When you use a WMI script to query the Win32_PerfFormattedData_NTDS_NTDS class on a Windows Server 2003-based domain controller, the script returns a 0x80041010 error

On a Windows Server 2003-based domain controller, you experience one of the following symptoms.

Symptom 1

When you use a Windows Management Instrumentation (WMI) script to query the Win32_PerfFormattedData_NTDS_NTDS class, the script fails. A 0x80041010 ("Invalid class") error is returned.

Symptom 2

When you use System Monitor to collect performance data, the following performance counters under the NTDS performance object always return 0:

• DS % Reads from NTDSAPI
• DS % Searches from NTDSAPI
• DS % Writes from NTDSAPI

This problem occurs because the Directory Service incorrectly handles the three performance counters that are described under Symptom 2 in the "Symptoms" section.

To resolve this problem, apply the following hotfix, and then run the following command at a command prompt:

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003 with Service Pack 1, x64-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

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

Steps to reproduce the problem

1. On a Windows Server 2003-based domain controller, click Start, click Run, type wbemtest, and then click OK.
2. Click Connect.
3. In the Namespace box, type root\cimv2, and then click Connect.
4. Click Query.
5. In the Enter Query box, type SELECT * FROM Win32_PerfFormattedData_NTDS_NTDS, and then click Apply.

You experience one of the symptoms that are described in the "Symptoms" section.

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