Microsoft KB Archive/941395

= A hotfix rollup package that provides an updated Client.msp is available for Systems Management Server 2003 =

Article ID: 941395

Article Last Modified on 11/14/2007

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-



INTRODUCTION
This article describes a hotfix rollup package that is available for the Microsoft Systems Management Server (SMS) 2003 Service Pack 3 (SP3) client. This update is in the form of an MSP package and can only be used to update existing SMS 2003 SP3 clients. The same update is also available as a Client.msi package in hotfix 941214. This hotfix provides an updated Client.msi for Systems Management Server 2003.

This hotfix rollup packages resolves the following problems.

Problem 1
The Wmiprvse.exe process on client computers in the organization may generate high CPU usage while SMS 2003 SP3 Asset Advisor is performing hardware-inventory operations. Sometimes, the CPU usage may reach 100 percent. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937882 After you install SMS 2003 Service Pack 3, the Wmiprvse.exe process may generate high CPU usage on client computers during hardware-inventory operations

Problem 2
When you schedule advertisements in Microsoft Systems Management Server 2003, you experience the following symptoms:
 * Advertisements that have a recurring daily schedule that you create in British Summer Time (BST) run one hour too early after the time changes to Coordinated Universal Time (UTC).
 * Advertisements that have a recurring daily schedule that you create in Coordinated Universal Time run one hour too late after the time changes to BST.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

933870 Advertisements that have a recurring schedule are off by one hour in SMS 2003 when the time changes between British Summer Time (BST) and Coordinated Universal Time

Problem 3
The hardware inventory process may fail for SMS clients that are running on Windows Vista-based computers. Additionally, Task Manager may display that a Wmiprvse.exe process has more than 500 megabytes (MB) of private working set. This behavior usually occurs on a computer that has more than 100,000 events in the Security log.

The symptoms of hardware failure may vary. Typically, no inventory data is sent to the management point when this problem occurs. Additionally, one of the following messages is logged in the InventoryAgent.log file.

Log message 1

Inventory: Starting reporting task.

Reporting: (80041013) Reading of reports failed

Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of CLIMSG_HINV_ERROR_REPORTFAILURE

{

...

};

CReportTask::CreateReportHeader: GetSingleWMIObject - Failed to read the client version & type.

CReportTask::CreateReport: CreateReportHeaderFile failed.

CReportTask::CreateReport failed.

Reporting: Cycle failed: 80041013

Inventory: Reporting Task completed in 0.062 seconds

Inventory: Reporting task failed to completed successfully. No report will be sent.

Log message 2

Unknown error encountered processing an instance of class CCM_System: 80041013

Collection: Failed to process mandatory data item for class: CCM_System. Cycle abandoned !!

Failed to process instances of CCM_System: 80004005

Collection: Cycle failed: 80004005

Log message 3

Unknown error encountered processing an instance of class SMS_MIFGroup: 80041013

Note This information is logged when some noncritical classes are not listed in the inventory data. The class that is listed in the log information may vary between clients or between instances of hardware inventory that are executed. The 80041013 error code represents a WMI Provider Load Failure (WBEM_E_PROVIDER_LOAD_FAILURE) error.



Problem 4
Some processes have an access violation problem because the AssetAdvisor.dll module allocates insufficient memory. For example, the Wmiprvse.exe process may have this access violation problem.

Problem 5
After you upgrade to Microsoft SMS 2003 Service Pack 3, you run a report that is based on the v_Add_Remove_Programs view. However, the report stops responding, and the process uses 100 percent of the CPU resources. For example, reports such as the &quot;Computers with specific software registered in Add Remove Programs&quot; report stop responding, and the process uses 100 percent of the CPU resources. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

939872 Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 Service Pack 3

Problem 6
SMS 2003 should use data that is combined with the ProductID registry entry and the DigitalProductID registry entry to determine sale channel code. Earlier products do not support the DigitalProductID registry entry.

Problem 7
Inventory counts are inaccurate in the License 1A report and in the License 1B report. Multiple components that have the same Microsoft product code (MPC) appear as a single product instead of as individual products.

Problem 8
When Microsoft SQL Enterprise Manager and Books online are installed on the computer, they are incorrectly reported as SQL Server installations in the License Ledger report.

Problem 9
The SMS_InstalledSoftware class incorrectly generates a software code for Windows operating systems by inserting some extra characters.



Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Applying the hotfix rollup package
Notes
 * The installation of this hotfix requires a site reset to complete the installation.
 * The installation process prompts you to create a package and a program so that you can distribute the Client.msp package to the existing Advanced Clients. Creating the default package and program is optional. If you accept this prompt, the package will be named &quot;KB941395 - Advanced Client Hotfix W2K&quot; and the program will be named &quot;KB941395 - Advanced Client Patch Install.&quot;
 * Apply this hotfix on the primary site servers and on the secondary site servers, and then use SMS software distribution to update the existing SMS 2003 SP3 Advanced Clients.

You must apply this hotfix on the primary site servers and on the secondary site servers. Then, use one of the following methods to distribute the updated Advanced Client.

Method 1
Use SMS software distribution to update the existing Advanced Client.

Method 2
Use Client Push Installation to update the existing Advanced Client. To do this, follow these steps:
 * 1) Open the SMS Administrator Console.
 * 2) In the console tree, expand Systems Management Server, expand the node that corresponds to the site database, and then expand Collections.
 * 3) Under the Collections node, right-click the collection to which you want to apply the new Advanced Client, point to All Tasks, and then click Install Client.
 * 4) Complete the steps in the Client Push Installation Wizard.

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix replaces the hotfixes that are described in the following Microsoft Knowledge Base articles.

937882 After you install SMS 2003 Service Pack 3, the Wmiprvse.exe process may generate high CPU usage on client computers during hardware-inventory operations

933870 Advertisements that have a recurring schedule are off by one hour in SMS 2003 when the time changes between British Summer Time (BST) and Coordinated Universal Time

939872 Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 Service Pack 3

File information
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

