When upgrading SQL Server to a newer version, it is not uncommon to encounter unexpected issues. One such issue is the failure of the “Windows Management Instrumentation (WMI) Service” rule during the upgrade process. In this blog post, we will discuss how to fix this error and successfully complete the upgrade.
The Error
During the upgrade from SQL Server 2008 R2 to SQL Server 2014 on a two-node cluster, two rules failed:
- Rule “Windows Management Instrumentation (WMI) service” failed. The WMI service is not running on the cluster node.
- Rule “Not clustered or the cluster service is up and online.” failed. The machine is clustered, but the cluster is not online or cannot be accessed from one of its nodes.
Upon further investigation, the error message indicated an issue with the cluster WMI namespace on one of the nodes.
The Solution
After consulting the MSDN documentation, it was discovered that the cluster namespace was missing in the WMI. To resolve this issue, the following steps were taken:
- Open the “Windows Management Instrumentation Tester” by going to Start > Run > WBEMTest.
- Select “Connect” and enter the namespace “Root\MSCluster”.
- If additional options are available, it means that the connection to WMI is working.
- In this case, an error with the code 0x80041010, facility WMI, and description “Invalid Class” was encountered.
- To fix this, the .mof file for the cluster was compiled using the command “Mofcomp.exe ClusWMI.mof”.
After running the above command, the cluster namespace was successfully added back to the WMI, resolving the error and allowing the upgrade to proceed without any further issues.
Conclusion
Encountering errors during SQL Server upgrades is not uncommon, and it is important to troubleshoot and resolve them promptly. In this case, the failure of the “Windows Management Instrumentation (WMI) Service” rule was fixed by compiling the .mof file for the cluster. If you have encountered a similar error during an upgrade, we hope this solution helps you resolve it as well.
Have you encountered the same error during a SQL Server upgrade and found a different solution? Please share it with our readers in the comments below.