SQL SERVER – Fix: Configuration Manager- Cannot Connect to WMI Provider. You Do Not Have Permission or The Server is Unreachable

The reason, I like SQL Server as a product is that there are multiple solutions to one problem and one can use the method they find most convenient. Almost three years ago, I wrote a blog post about how to solve the error: Configuration Manager – Cannot Connect to WMI Provider. You Do Not Have Permission or The Server is Unreachable. The other day, I faced the same error again and this time I solved it with a different method. Let us learn how I did that.

When I was working with my client Comprehensive Database Performance Health Check, I suddenly received the following error:

SQL Server Configuration Manager
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.


Here is what we did to fix the problem. The first opened a command prompt in the location machine and ran the following command according to the SQL Server version which was installed on the machine.

SQL Server 2005

mofcomp “%programfiles(x86)%\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof”

SQL Server 2008 / R2

mofcomp “%programfiles(x86)%\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”

SQL Server 2012

mofcomp “%programfiles(x86)%\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof”

SQL Server 2014

mofcomp “%programfiles(x86)%\Microsoft SQL Server\120\Shared\sqlmgmproviderxpsp2up.mof”

SQL Server 2016

mofcomp “%programfiles(x86)%\Microsoft SQL Server\130\Shared\sqlmgmproviderxpsp2up.mof”

SQL Server 2017

mofcomp “%programfiles(x86)%\Microsoft SQL Server\140\Shared\sqlmgmproviderxpsp2up.mof”

SQL Server 2019

mofcomp “%programfiles(x86)%\Microsoft SQL Server\150\Shared\sqlmgmproviderxpsp2up.mof”

When you run the above statement, it will give you success output.

However, if due to any reason, you do not get Success, you will have to follow the suggestion provided in my earlier blog post over here.

I hope you will be able to solve your problem easily and quickly and get started with SQL Server Configuration Manager. If you are familiar with any such other tip or trick, do let me know and I will be happy to post about them on this blog post with due credit to you.

Reference: Pinal Dave (http://blog.SQLAuthority.com)

Exit mobile version