A "WBEM_E_INCOMPLETE_CLASS" WMI error occurs or Wmiprvse.exe crashes when concurrent WMI queries are sent to the cluster resources in Windows Server 2008

Consider the following scenario:

• You install the Failover Clustering feature on a multiprocessor computer that is running Windows Server 2008.
• On this computer, the MSCluster_ResourceGroup Windows Management Instrumentation (WMI) provider receives concurrent queries.

In this scenario, you may experience one or more of the following issues on the computer:

• You receive the following WMI error message:
  WBEM_E_INCOMPLETE_CLASS
• The WMI provider (Wmiprvse.exe) host process crashes.
• A program that manages the cluster resources does not work or works incorrectly.
• No errors are reported on the computer. However, the computer sends incorrect status data to the client computers.

This issue occurs because of a race condition in the WMI provider for the failover cluster. When the race condition occurs, a thread of a WMI query tries to access a variable that was freed by another thread. Therefore, an access violation occurs, and the Wmiprvse.exe host process crashes.

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 the problem described in this article. 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 be running Windows Server 2008 Service Pack 2 (SP2).

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix. To avoid restarting the computer, stop the Cluster service, and then install the hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 file information notes

• The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

  Version	Product	SR_Level	Service branch
  6.0.600 2 . 22xxx	Windows Server 2008	SP2	LDR

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

For all supported x64-based versions of Windows Server 2008

For all supported IA-64-based versions of Windows Server 2008

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

For more information about the MSCluster_ResourceGroup class, visit the following Microsoft website:For more information about the WMI error constants, visit the following Microsoft website: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Additional files for all supported IA-64-based versions of Windows Server 2008