Help: SQL Server

Sharing my knowlege about SQL Server Troubleshooting Skills

Solution : SQL Server Configuration Manager – Cannot connect to WMI provider – Provider load failure [0x80041013]

Posted by blakhani on February 3, 2015


One of my friend had something wrong with SQL Server installation. He did multiple things like repair, registry cleanup etc. I helped him in cleaning up stuff and reinstalling SQL Server. Things were looking good but there was one pending issue.

As soon as he was trying to launch SQL Server Configuration Manager, he was seeing below 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.
Provider load failure [0x80041013]
—————————
OK  
—————————

 

Another variation of same error is The specified module could not be found. [0x8007007e] – This clearly indicates that some dll is not registered.

He found this KB http://support.microsoft.com/kb/980142 but he was on SQL 2008 SP3 so this was not applicable. Since there was many things done by him, I was almost sure that this is due to either missing DLL or some WMI provider related files. Below were the steps performed to fix the issue.

  • We need to make sure that we have sqlmgmproviderxpsp2up.mof file present and complied. Refer my earlier blog for using mofcomp to compile the mof files.
  • Make sure we have sqlmgmprovider.dll file in “shared” folder. The location of folder would be dependent on SQL version. On my machine it is located under “C:\Program Files\Microsoft SQL Server\100\Shared” The folder 100 is for SQL 2008. Refer below table for version and name mapping.  

Microsoft SQL Server 2014

120

Microsoft SQL Server 2012

110

Microsoft SQL Server 2008 R2

100

Microsoft SQL Server 2008

100

Microsoft SQL Server 2005

90

  • If file is present in the folder, please register the DLL using command (regsvr32.exe "C:\Program Files\Microsoft SQL Server\110\Shared\sqlmgmprovider.dll")
  • Make sure we have file “svrenumapi.dll” in the same folder. If file exists, register it using regsrv32.exe as pointed earlier. In SQL 2014 the file is called as svrenumapi12.dll
  • Make sure that file framedyn.dll exists in “C:\WINDOWS\system32” folder. If not, pick it from C:\WINDOWS\system32\wbem folder and keep it to system32.
  • Check your environment variables. the PATH variable has C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

If none of the above is working then you should download Process Monitor and capture data while launching SQL Server Configuration Manager. Look for “Name not found” and that might give you some hint. Comment below if you found any other solution

Advertisements

2 Responses to “Solution : SQL Server Configuration Manager – Cannot connect to WMI provider – Provider load failure [0x80041013]”

  1. Sunder Singh kapkoti said

    Hi ,

    I am submitting one of my query related to performance of SP, the issue is

    when I execute the SQL statements written inside SP, without SP it is running fine and completed with in 1 minnute but when i run it through SP it is died out and not completing even in 72 hrs.

    If you can suggest me the possible causes for this behaviour on SQL statements with SP and with out SP.

    Thanks in advance.

    Regards
    Sunder Singh Kapkoti

  2. Rawden Hoff said

    Hi had to grant registry permissions to HKEY_CLASSES_ROOT\CLSID\{540967d8-8743-4778-b346-a3459896ef94} to get this to work. I have just upgraded to Windows 10 x64 and am running SQL 2008 x84 and 2012 x64 side by side.

    Regards,

    Rawden.

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

 
%d bloggers like this: