Lets start with a simple issue that I have struggled with a few times. I try to start SQL Server Configuration Manager and is met with this puzzling message:
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid class [0x80041010]
The Internet list many culprits and most agree that WMI is not to blame this time. Exactly what causes the error seems to be somewhat random. Someone blames 32 vs. 64-bit mixed installations. I have experienced it after patching or installing multiple different instances on the same server, or even just patching an instance. Lets all agree it is caused by change of some kind.
Usually this issue is rather easy to resolve. Open CMD as administrator and type (copy) the following (take care to replace 000 with your SQL Server version code.
mofcomp "%programfiles(x86)%\Microsoft SQL Server\000\Shared\sqlmgmproviderxpsp2up.mof"
If you have the simple problem, then this will resolve your issue, and it might look something like the screenshot below. Your luck might vary. If the the easy to remember file name sqlmgmproviderxpsp2up.mof is not in the catalog, you might need to search a bit on your server to see if you have it lying around somewhere else.
SQL Server list of versions
- 2000 = 80
- 2005 = 90
- 2008 = 100
- 2008 R2 = 105
- 2012 = 110
- 2014 = 120
- 2016 = 130
- 2017 = 140
- Error message when you open SQL Server Configuration Manager (Microsoft.com)
- Unable to access SQL Server Configuration Manager (Stackoverflow.com)
- SQL Server Configuration Manager cannot connect […] (Mssqlservertips.com)
- SQL Server File names vs versions (Stackoverflow.com)
- Photo by Nathan Dumlao on Unsplash