How to resolve the SQL error “cannot connect to WMI provider”

When you try to open SQL Configuration Manager Option and if you get an error like

“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 [0x8004100] then what will be cause? And what is the resolution?

 

image

Cause.
This problem occurs because the WMI provider is removed when you uninstall an instance of SQL Server. The 32-bit instance and the 64-bit instance of SQL Server share the same WMI configuration file. This file is located in the %programfiles(x86)% folder.

It seems the sqlmgmproviderxpsp2up.mof was damaged during the issues with the SAN.

So what is the Solution for this?

In my case I am using SQL 2012 SP1. So where can I find the sqlmgmproviderxpsp2up.mof file?

The location as follows :

C:\Program Files <x86>\Microsoft SQL Server\110\Shared folder.

 

image

The work around for this problem, you have to open a command prompt, type the following command, and then press ENTER:

mofcomp sqlmgmproviderxpsp2up.mof

image

Note For this command to succeed, the Sqlmgmproviderxpsp2up.mof file must be present in the %programfiles(x86)%\Microsoft SQL Server\number\Shared folder.
The value of number depends on the version of SQL Server:nnn

Microsoft SQL Server 2012

110

Microsoft SQL Server 2008 R2

100

Microsoft SQL Server 2008

100

Microsoft SQL Server 2005

90

After you run the Mofcomp tool, make sure to restart the WMI service for the changes to take effect.

Once this is done you will be able to open the SQL Configuration Manager Console.

Thanks

Smile

Advertisements

24 thoughts on “How to resolve the SQL error “cannot connect to WMI provider”

  1. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #49 - TechCenter - Blog - TechCenter - Dell Community

  2. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #49 - Dell TechCenter - TechCenter - Dell Community

  3. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #49 - Flo's Datacenter Report

  4. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #51 - Flo's Datacenter Report

  5. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #56 - Flo's Datacenter Report

  6. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #61 - Flo's Datacenter Report

  7. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #62 - Flo's Datacenter Report

  8. Thank you for this, really helped me out.

    …It seems the sqlmgmproviderxpsp2up.mof was damaged during the issues with the SAN….

    You know what kind of night it is…

  9. Pingback: Got “Cannot connect to WMI provider” when tried to open SQL Server Configuration Management | LouieBao.Net

  10. I tried the workaround and got:
    Storing data in the repository…
    An error occurred while processing item 1 defined on lines 4 – 7 in file
    C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof:

    Error Number: 0x80041003, Facility: WMI
    Description: Access denied

    Compiler returned error 0x80041003

  11. Pingback: How To Fix 0x80041003 Facility Wmi Registry Errors - Windows Vista, Windows 7 & 8

  12. Pingback: Fix Sql Cannot Connect Error 18456 Windows XP, Vista, 7, 8 [Solved]

  13. Thank you sooooo much for this! after weeks of wrangling with our application support team and getting no where, I decided to take matters in my own hands (Im local IT with no SQL experience) and this fixed our issue. You, sir or madam, are awesome.

  14. I applied this fix on a SQL 2016 Enterprise server built on Window2012 OS and although mofcomp sqlmgmproviderxpsp2up.mof ran successfully , it did not resolve the error. I ran procmon which didn’t suggest an error and also provided additional permissions to the registry keys. Unfortunately nothing allowed me to connect to WMI – any additional suggestions would be appreciated – Thanks

  15. I don’t even understand how I finished up here, but I believed this
    publish was good. I don’t realize who you’re but certainly you are going to a well-known blogger should
    you are not already. Cheers!

  16. I am running SQL 2016 on a Windows 10 OS. I ran the prompt as described and it was able to parse as advertised. However, when I go to open up the configuration manager I am still getting the same error code. If anyone has developed a work around for this please post. This is driving me crazy!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s