While playing with my virtual machine, I encountered an interesting error. In this blog we would learn how to fix error cannot connect to WMI provider [0x80070422] while launching SQL Server Configuration Manager.
As I have been writing in my earlier blogs, I always use my virtual machine as my playground to break things and fix it. If I can fix it, I write a blog and if I can’t fix it then I restore the VM to last known good image. After making some changes, when I tried launching SQL Server configuration manager, I was welcomed by below error message.
![SQL SERVER - Unable to Launch SQL Server Configuration Manager. Error: Cannot Connect to WMI Provider. [0x80070422] sscm-err-01](https://blog.sqlauthority.com/i/d/sscm-err-01.jpg "SQL SERVER - Unable to Launch SQL Server Configuration Manager. Error: Cannot Connect to WMI Provider. [0x80070422] sscm-err-01")
Here is the text of error 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.
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. [0x80070422]
The first part of the error message is quite generic. The second part is the one which explains the real cause. It talks about some service which is needed. Based on my experience I knew that it is all about WMI Service. If you get same hex code 0x80070422 then you should check services on that machine. You might find the Windows Management Instrumentation (WMI) Service is set as “Disabled”
![SQL SERVER - Unable to Launch SQL Server Configuration Manager. Error: Cannot Connect to WMI Provider. [0x80070422] sscm-err-02](https://blog.sqlauthority.com/i/d/sscm-err-02.jpg "SQL SERVER - Unable to Launch SQL Server Configuration Manager. Error: Cannot Connect to WMI Provider. [0x80070422] sscm-err-02")
WORKAROUND/SOLUTION
As you might have guessed that we need to enable Windows Management Instrumentation (WMI) service to get it working. This service should be healthy for SQL Server Configuration Manager to work properly. Here are the steps to enable the service.
- Click on Start and go to Run
- Type “Services.msc” and hit enter.
- Scroll down to locate “Windows Management Instrumentation”
- Right-click on that service and go to properties.
- From the drop-down, choose “Automatic”.
- Hit OK to save the settings.
After following the above, you should be able to launch the SQL Server Configuration Manager without any error. Have you found any other cause of such error caused by WMI?
Reference: Pinal Dave (https://blog.SQLAuthority.com)
1 Comment. Leave new
Hi, Dave,
unfortunately I have a similar case to this but the hex number differs. The description of the error is Invalid class 0x80041010.
Do you know what this is all about?
This is SQL 2017 and I find this is a solution, but when I run this as run as admin, I get the following message:
C:\>mofcomp.exe “C:\Program Files (x86)\Microsoft SQL Server\140
\Shared\sqlmgmproviderxpsp2up.mof”
MOF file has been successfully parsed
Storing data in the repository …
An error occurred while processing item 10 defined on lines 73-79 in C: \ Program Files (x86) \ Microsoft SQL Server \ 140 \ Shared \ sqlmgmproviderxpsp2up.mof file:
Error Number: 0x80070005, Facility: Win32
Description: Access is denied.
Compiler returned error 0x80070005
My user is also a local administrator and sysadmin on the SQL Server
Best regards.
Slaviša Radisavljević, Serbia