After you install the Simplified Chinese version of Systems Management Server (SMS) 2003 Inventory Tool for Microsoft Updates Version 3 (ITMUv3), the following reports generate incorrect information:

• All computers with a specific software update distribution status
• Software update distribution status by software update ID
• All computers with a specific update advertisement status
• Software update advertisement status by software update ID
• Distribution status summary of software updates
• Summary of software updates that failed to deploy

Additionally, some new reports do not appear in the Reports list.

This problem does not occur if the English version of SMS 2003 and the English version of ITMUv3 are installed.

This problem occurs because the Swupdate_reports_chs.mof file is corrupted.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Hotfix installation instructions

To apply this hotfix, follow these steps:

1. Run the ITMUv3-KB941039-X86-CHS.exe file.
2. In the Choose Directory for Extracted Files box, specify a location to save the Swupdate_reports_chs.mof file, and then click OK.
3. Open the SMS Administrator console.
4. In the console tree, expand Site Database, expand Reporting, right-click Reports, point to All Tasks, and then click Import Objects.
5. On the Welcome page, click Next.
6. In the MOF path and file name box, type the path and the file name of the Swupdate_reports_chs.mof file that you specified in step 2, and then click Next.
7. Follow the instructions in the Import Object wizard to finish the steps.

After you follow these steps, the reports generate correct information. Additionally, new reports that have the following identifiers appear:

• 0000000183
• 0000000184
• 0000000185
• 0000000186
• 0000000187

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 does not replace any other hotfixes.

File information

The Simplified Chinese 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.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

To determine whether you are experiencing this problem, follow these steps:

1. Open the SMS Administrator console.
2. In the console tree, expand Site Database, expand Reporting, and then click Reports.
3. Right-click the Distribution status summary of software updates report, and then click Properties.
4. On the General tab, click Edit SQL Statement.
5. Examine the information in the SQL statement box. The following is an example of an SQL statement that has this problem:

   from v_GS_PatchStatus ps
   join v_FullCollectionMembership fcm on ps.ResourceID=fcm.ResourceID
   join v_ApplicableUpdatesSummary inf on 
     ps.ID=inf.ID and 
     ps.QNumbers=inf.QNumbers and 
     ps.LocaleID=inf.LocaleID and 
     ps.Title=inf.Title and 
     ps.Product=inf.Product
   where fcm.CollectionID=@CollID
   

   The following is an example of an SQL statement that does not have this problem:

   from v_GS_PatchStatusEx ps
   join v_FullCollectionMembership fcm on ps.ResourceID=fcm.ResourceID
   join v_ApplicableUpdatesSummaryEx inf on 
     ps.UpdateID=inf.UpdateID 
   where fcm.CollectionID=@CollID and
              inf.Type = @Type
   

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