Symptoms
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 inhotfix 941214. This hotfix provides an updated Client.msi for Systems Management Server 2003.
This hotfix rollup packages resolves the following problems.
Problem 1The 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?(http://support.microsoft.com/kb/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 2When 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?(http://support.microsoft.com/kb/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 3The 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: 80004005Log message 3
Unknown error encountered processing an instance of class SMS_MIFGroup: 80041013Note 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.
Resolution
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 “Computers with specific software registered in Add Remove Programs” 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?(http://support.microsoft.com/kb/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 7Inventory 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 8When 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 9The SMS_InstalledSoftware class incorrectly generates a software code for Windows operating systems by inserting some extra characters.
