Microsoft KB Archive/324142

= SMS: Software Inventory Agent Generates Exception If Damaged History File Is Processed =

Article ID: 324142

Article Last Modified on 10/25/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-



This article was previously published under Q324142



SYMPTOMS
When the Systems Management Server (SMS) Software Inventory Agent (Sinv32.exe) scans a history file (Sinv.his) that is damaged, it may generate an exception error. When this symptom occurs, the Software Inventory agent generates a 669 status message. The following log entries may be added to the Sinv32.log file on the client:

Preloading history file ...... <<<<<<<<<<<<< EXCEPTION EXCEPTION EXCEPTION >>>>>>>>>>>>> <> (Logged to all threads) An exception was raised in the application 'Software Inventory Agent', thread 0x128 (Main Thread) <> A fatal exception occurred in THIS THREAD.



CAUSE
The cause of this problem occurs in two stages:
 * 1) The Software Inventory Agent performs a complete inventory, and finds the first file in a folder without a valid Product Name field. When this occurs, it places the file information in the history file (Sinv.his) without any preceding product information.
 * 2) The next time software inventory is taken, the history file is parsed by the Software Inventory agent. The file record that is not preceded by the product information causes the agent to generate an exception error.



Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Systems Management Server 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

288239 How to Obtain the Latest Systems Management Server 2.0 Service Pack

Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server service pack that contains this hotfix.

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 about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The SMS 2.0 post-Service Pack 3 (SP3) English version of this fix should have the following file attributes or later:   Date         Time   Version        Size     File name        Platform -  01-Mar-2001  22:10  2.0.92.9       511,801  Insinv32.exe     Alpha 01-Mar-2001 22:10  2.0.1493.3274  151,824  Sinv32.exe       Alpha 01-Mar-2001 22:10                      67  Compversinv.ini 01-Mar-2001 22:10  2.0.92.9       280,581  Insinv32.exe     Intel 01-Mar-2001 22:10  2.0.1493.3274  104,816  Sinv32.exe       Intel NOTE: Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.



WORKAROUND
To work around this problem, re-install the program that is inventoried without the product information so it is inventoried in a different order.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Systems Management Server 2.0 Service Pack 5.



Installing the Hotfix
Apply this fix to all sites in the SMS hierarchy in which the Software Inventory Agent must be updated because of this problem.

Using the Hotfix Installer
NOTE: Only use this method on Intel-based computers.
 * 1) Copy or extract the hotfix to the SMS site server, making sure to maintain the folder structure, with the I386 and Alpha folders &quot;below&quot; the folder that contains the Q324142.exe hotfix installation program.
 * 2) Run Q324142.exe, and then follow the installation instructions. Note that running the Q324142.exe /s command causes the installation program to run silently.
 * 3) After installation, verify that the SMS services are started.

Clients will upgrade their software inventory components in the 23-hour maintenance cycle.

Manual Installation

 * 1) Stop the SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER services on the site server.
 * 2) Copy the updated Insinv32.exe files to the appropriate  \Inboxes\Clicomp.src\Sinv\  folders.
 * 3) Copy the Sinv32.exe files to the appropriate  \Bin\  folders.
 * 4) Copy the Compversinv.ini file to the  \Inboxes\Clicomp.src\Sinv folder and rename it to Compver.ini.
 * 5) Start the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services. You can update the clients after the Client Access Points (CAPs) have been updated.

NOTE: The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Because of this, 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, or you can click Update Configuration on the Sites tab in the client's Systems Management tool in Control Panel.

Additional query words: prodsms av

Keywords: kbhotfixserver kbqfe kbsms200presp5fix kbhardware kbbug kbenv kberrmsg kbfix kbinventory KB324142

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.