Check that WMI is Running on the Node
WMI Service
First check that the ‘Windows Management Instrumentation’ Service has started on each node by opening the Services console on that node. Also check that its Startup Type is set to Automatic.
WBEMTest or directly on the server
· Launch CMD
· CMD > WBEMTest
· The Windows Management Instrumentation Tester will launch
· Select Connect
· Namespace: Root\MSCluster
· Select Connect
o If you see more options available, it means you are connected and WMI is working
§ Feel free to try a query to confirm, such as selecting ‘Query’ and enter: SELECT * from MSCluster_Resource
o If you see an error, there is a WMI issue
PowerShell or remotely from another node within the same cluster (2008 R2 or higher only)
· Launch Elevated PowerShell
· PS > get-wmiobject mscluster_resourcegroup -computer MyNode -namespace “ROOT\MSCluster“
o If you see a lot of information displayed, WMI is running
o If you see an error, there is a WMI or firewall issue
Rebuild a Corrupt WMI Repository
If you continue to see errors after checking that WMI is running, the firewall is properly configured and rebooting, it is possible that your WMI repository has become corrupt so the cluster can no longer read from it. The following steps will enable you to rebuild your repository so that the other nodes can read from it again. Rebuilding the repository should be your last troubleshooting step, not your first.
· In the Services console, manually stop the WMI service to ensure that dependent services are stopped
· Start WMI service again
· Launch and elevated CMD or PowerShell
· CMD/PS > winmgmt /ResetRepository
Ensure that WMI is installed. Verify that the %Windir%\System32\WBEM directory exists and that it contains WinMgmt.exe.
Review WMI security by using WMI Control (or Wbemperm.exe for earlier versions of WMI). Ensure that the accounts that are used by your management application are able to access WMI and the namespaces that are used by that application.
Review the logs that are available in the %Windir%\System32\wbem\logs directory.
Use WMI Control to enable verbose logging. Reproduce the problem and review the logs again.
If the problem might be provider-specific, enable provider logging. In addition to default WMI logging, you can enable provider logging by changing the Logging or Level values in the following registry tree:
HKLM\Software\Microsoft\WBEM\Providers\Logging
If you think that the CIM Repository might be corrupted, verify that it has a normal complement of namespaces, providers, and classes. For more information, see the “Verifying the State of the CIM Repository” section later in this appendix. If this confirms that the CIM Repository is corrupted, see the “Backing Up WMI Data” section earlier in this appendix.
Table B.4 WMI Logs
| Log | Content |
|---|---|
| Wbemcore.log | Core |
| WinMgmt.log | The WMI service |
| Framework.log | The WMI framework, including the Win32 Provider |
| Wbemess.log | The event subsystem |
| Setup.log | Setup and upgrade |
| Mofcomp.log | MOF Compiler messages |
| Wbemprox.log | The connection proxy, which is relevant during the connection to WMI, especially for DCOM-related issues |
| WMIAdap.log | The high-speed performance counter adapter |
| WMIProv.log | Providers-related issues, but not necessarily provider-specific issues |
| WMIC.log | The WMI Command-line tool |
| Dsprovider.log | The Active Directory provider |
| NTEvt.log | The Windows NT event log provider |
| WbemSnmp.log | The SNMP Provider |
If your WMI-based management application or script is running successfully but very slowly, consider whether WMI is using an excessive amount of computer resources (such as memory or CPU time). In the worst cases, WMI resource consumption issues can cause the computer to respond slowly.
The Processes tab of Windows Task Manager (TaskMgr.exe) is an effective tool to confirm whether WMI is consuming excessive resources. In the Image Name column, review WinMgmt.exe to see if it is using a large percentage of CPU or a large amount of CPU Time. The Mem Usage column is also useful, but you should add the VM Size column to add virtual memory consumption to the display (by clicking Select Columns on the View menu). WMI usually uses 8 to 10 MB of memory or virtual memory.