Article ID: 323911
Article Last Modified on 10/25/2006
APPLIES TO
- Microsoft Systems Management Server 2.0 Standard Edition
This article was previously published under Q323911
SYMPTOMS
When a primary Systems Management Server (SMS) site is attached to a parent site, Software Inventory Processor (SMS_SOFTWARE_INVENTORY_PROCESSOR) is flagged to resynchronize all clients. This is flagged by placing a "{sitecode}.sha" file in the SMS\Inboxes\Sinv.box folder. When this occurs, you see the following entry in the Sinvproc.log file:
New parent site detected. Resync all clients.
On a site with many clients, Software Inventory Processor typically processes the first group of resynchronization requests very quickly, but then slows down and processes only one resynchronization request every several minutes.
Software Inventory Processor does not process any incoming software inventory files while it is processing the resynchronization requests. Therefore, additional files may back up in the Sinv.box folder on the site server.
CAUSE
Resynchronization requests are processed slowly only when a client's GUID or SMSID is not in the current SMS\Inboxes\Clidata.src\Client.lkp file. When Software Inventory Processor inserts a new client in the Client.lkp file to signal that the client must be resynchronized, it writes all the existing records in a temporary file. This operation may be slow if the Client.lkp file contains a lot of clients.
RESOLUTION
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:
288239How to Obtain the Latest Systems Management Server 2.0 Service Pack
Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends 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:
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 English version of this fix for SMS 2.0 Service Pack 4 (SP4) sites has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name Platform
-------------------------------------------------------------------
01-May-2002 14:05 2.0.1493.4129 1,514,768 Baseobj.dll Alpha
01-May-2002 14:05 2.0.1493.4129 965,728 Baseobj.dll X86
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.
WORKAROUND
To work around this problem, remove the "{sitecode}.sha" file so that Software Inventory Processor does not resynchronize all clients at the same time. Software Inventory Processor then resynchronized the clients one at a time as clients report their software inventory data on their configured schedule.
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.
MORE INFORMATION
How to Install the Hotfix
Apply this fix on all the sites in the SMS hierarchy. To install the fix, use one of the following methods.
How to Use the Hotfix Installer
NOTE: You can use this method only on Intel-based computers.
- Copy the hotfix folder structure to a local folder on your site server or to a share on your network. The I386 and Alpha subfolders are required; you must also download them from the Microsoft FTP site. It is important to keep the folder structure intact. The Q323911.exe file is a Microsoft Windows Installer file that updates specific files on your site server.
- Log on to your site server by using an account with administrator permissions.
- On the site server, quit the SMS Administrator console.
- Run the Q323911.exe file and then follow the instructions in the wizard. The SMS services are stopped and restarted as part of the installation process.
How to Manually Install the Hotfix
- Copy the update program file (Q323911.exe) and platform folders to a new folder. The folder structure must be such that the program file is located one folder "above" the platform folders.
- Quit the SMS Administrator console and stop all SMS services in Control Panel. If the SMS_SITE_BACKUP service is running, stop it.
- Replace the Baseobj.dll file that is located in the SMS\Bin\
Platformfolder with the version that is located in the hotfixPlatformfolder. - Restart the SMS site services.
Additional query words: prodsms sinv resync backlog
Keywords: kbhotfixserver kbqfe kbsms200presp5fix kbhardware kbbug kbfix KB323911
