Microsoft KB Archive/941214

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

Article ID: 941214

Article Last Modified on 11/14/2007

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-



SYMPTOMS
This article describes a hotfix rollup package that is available for the Microsoft Systems Management Server (SMS) 2003 client. This update is in the form of an MSI package. It can be used to deploy the new, updated client or to update existing ones by forcing a reinstallation of the client by using a push installation. The same update is also available as a Client.msp package in hotfix 941395. This is a hotfix rollup package that provides an updated Client.msp for SMS 2003.

The hotfix rollup package resolves the same issues as hotfix 941395 that is described in the following Microsoft Knowledge Base article:

941395 A hotfix rollup package is available for the Microsoft Systems Management Server 2003 client

Hotfix 941395 updates the existing installation of SMS 2003 SP3 client software. However, the current hotfix rollup package (hotfix 941214) also provides an updated Client.msi package. Therefore, you can deploy the Client.msi package to computers that do not have SMS 2003 SP3 client software installed.

This hotfix rollup package resolves the following problems.

Problem 1
The Wmiprvse.exe process on client computers in the organization may generate high CPU usage while the SMS 2003 SP3 Asset Advisor is performing hardware-inventory operations. 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 SMS 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 UTC 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 the access violation problem.

Problem 5
After you upgrade to SMS 2003 SP3, you run a report that is based on the v_Add_Remove_Programs view. However, the report stops responding. Additionally, 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. Additionally, 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, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

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

How to apply the hotfix rollup package
You must apply this hotfix on the primary site servers and on the secondary site servers. This hotfix automatically replaces the Client.msi file on the site servers. Then, SMS 2003 servers use the new Client.msi file to deploy SMS 2003 client software. When you use the MSI package to update existing clients, use either of the following methods:
 * Use SMS software distribution to update the existing Advanced Clients with the Client.msi file.
 * Use Client Push Installation to update the existing Advanced Clients with the Client.msi file. To do this, follow these steps:
 * Start the Client Push Installation Wizard.
 * On the Client Installation Options page, select the Always install (repair or upgrade existing client) option.
 * Follow the steps to complete the wizard.

Note When you use the Client Push Installation method, the Advanced Client automatically receives the latest version of the Client.msi file. You do not have to move or copy the Client.msi file.

Notes The installation of this hotfix requires a site reset.

Prerequisites
There are no prerequisites for installing this hotfix.

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 articles in the Microsoft Knowledge Base:

937882 After you install SMS 2003 SP3, 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 SP3

941395 A hotfix rollup package is available for the Microsoft Systems Management Server 2003 client

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.

