An application or service frequently uses the Windows Management Instrumentation (WMI) interface to query a Windows Server 2008 R2 failover cluster for hosted virtual machine information by using one of the following commands:
Select * from MSCluster_Resource where Type = 'Virtual Machine' and PrivateProperties.VmID = 'id'
Select * from MSCluster_Resource where Type = ‘type1 ‘ [OR type = ‘typeN’ ]*
Select * from MSCluster_Resource where Type = ‘Generic Service’ and PrivateProperties.ServiceName = ‘ServiceName’
Select * from MSCluster_Resource where Type = ‘Virtual Machine Configuration’ and PrivateProperties.VmId = ‘id’
Hotfix package 974930 is installed on the queried cluster node.
In this scenario, the memory usage of one Wmiprvse.exe process keeps increasing every time WMI queries are conducted. With time, the Wmiprvse.exe process terminates. Because of this issue, the application or service experiences low performance or function failure.
The issue occurs because the Cluster WMI provider (Cluswmi.dll) incorrectly leaks about 4,100 bytes of heap space every time that an enumeration of cluster resources is conducted.
To resolve the issue, install the following hotfix on the affected Windows Server 2008 R2-based cluster node.
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.
To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).
Additionally, you must have the Failover Clustering feature installed.
For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
To use the hotfix, you do not have to change the registry.
You do not have to restart the computer if you stop the Cluster service before you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Windows Server 2008 R2
Windows Server 2008 R2
The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. 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 x64-based versions of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
To work around the issue, run the following script on the affected Windows Server 2008 R2-based cluster node:
select * from mscluster_Resource where PrivateProperties.VmID = 'id'
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
974930 An application or service that queries information about a failover cluster by using the WMI provider may experience low performance or a time-out exception
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2