SMS: Software Inventory Creation Date Is Incorrect in SMS Database

ID: Q238762

The information in this article applies to:
  • Microsoft Systems Management Server version 2.0

SYMPTOMS

Systems Management Server (SMS) Resource Explorer may display a created date for an inventoried file that is different from the created date listed in the file's properties in Windows Explorer.


CAUSE

This problem occurs for two reasons:

  • The software inventory agent (sinv) did not use the file Creation Date as a key property. Therefore on a single client, files with the same name but with different created time stamps, were treated as the same and were not reported separately.


  • The stored procedure (sp_SoftwareInventory) that inserts software inventory information into the SMS database also did not use Creation Date as a key property. As a result, the time stamp that became associated with the file was simply the time stamp of the last reported instance across all clients.



RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English-language version of this fix should have the following file attributes or later: 

   Date      Time     Version          Size   File name    Platform
   ----------------------------------------------------------------
   12/30/99  12:34pm                   5,677  54831.sql    All
   11/5/99   3:59pm  2.0.91.3        277,953  Insinv32.exe I386
   11/5/99   3:56pm  2.0.1380.1070   100,208  Sinv32.exe   I386
   11/5/99   5:48pm                       67  Compver.ini  All
   11/5/99   3:59pm  2.0.91.3        507,636  Insinv32.exe Alpha
   11/5/99   3:56pm  2.0.1380.1070   144,144  Sinv32.exe   Alpha
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.



STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.


MORE INFORMATION

WARNING: Before you follow the steps below, you should generate SQL Server scripts for the following stored procedures:

  • sp_SoftwareInventory


  • sp_SMSGetNextID_Internal


These stored procedures are replaced by the hotfix SQL Server script. Generating and saving the scripts listed above lets you undo the changes made by the hotfix SQL Server script if necessary.

To install the hotfix, perform either of the following procedures at the Systems Management Server Site Server:

Using The Hotfix Installer:

i386 platforms only

  1. Copy the hotfix directory structure to a share on your network. Q238762.exe is a Microsoft Windows Installer file that updates specific files on your site server.


  2. Log on to your site server using an account with administrative privileges.


  3. On the site server, close the SMS Administrator console.


  4. Run the Q2238762.exe file, and follow the directions in the wizard. The file can be run in quiet mode using the /s switch.


  5. Stop the SMS Site Component Manager and SMS Executive services on the SMS Site server.


  6. Load the 54831.sql script using a SQL Server query tool, such as Query Analyzer or ISQL/W.


  7. Select the Systems Management Server database, and then run the script.


  8. Restart the SMS Site Component Manager and SMS Executive services.


Manual installation:

  1. Stop the SMS Site Component Manager and SMS Executive services on the SMS Site server.


  2. Replace the Compver.ini in the <Sms_root_directory>\Inboxes\Clicomp.src\Sinv folder with the version obtained from the hotfix.


  3. Replace the Insinv32.exe file in the <Sms_root_directory>\Inboxes\Clicomp.src\Sinv\<Platform> folder with the version obtained from the hotfix.


  4. Replace the Sinv32.exe file in the <Sms_root_directory>\Bin\<Platform> folder with the version obtained from the hotfix.


  5. Load the 54831.sql script using a SQL Server query tool, such as Query Analyzer or ISQL/W.


  6. Select the Systems Management Server database, and then run the script.


  7. Restart the SMS Site Component Manager and SMS Executive services.


NOTE: The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Therefore, it may take up to 23 hours for the hotfixed files to be propagated to the clients. To speed up this process, you can stop and restart the SMS Client Service on each client. You can also create a software distribution for one of the Resource Kit tools Setevnt.exe or Cliutils.exe along with the appropriate parameter(s) to start a CCIM work cycle. For information on the proper syntax to use with these tools, see the Resource Kit documentation.

Additional query words: prodsms sinv sinvproc

Keywords : kbSMS200 kbSMS200bug kbInventory
Version : winnt:2.0
Platform : winnt
Issue type : kbbug


Last Reviewed: January 7, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.