SQL SERVER – Configuration Manager Error: The Server Threw an Exception [0x80010105]

In my previous blog, I showed one of the errors caused due to disabled WMI service.  In this blog, we would learn how to fix error “The server threw an Exception [0x80010105]” while using SQL Server Configuration Manager.

After reading my previous blog, one of my blog readers contacted me to fix another error. If you search on the internet mostly you would see KB 2849344 but the client was using Windows Server 2008 and article is applicable to Windows 2012.

Here is how it was seen in the configuration manager:

SQL SERVER - Configuration Manager Error: The Server Threw an Exception [0x80010105] sscm-excep-01


In a few situations found on the internet, WMI service restart helped to fix the issue. We already tried restarting WMI Service, but it didn’t help in this situation.

Here are the steps which helped us in fixing the error. These are available on the internet on various blogs. I wanted you to save all possible steps to fix the error.

  1. Try restarting WMI Service.
  2. Compile all the MOF file related to windows. You can do that by using a script in my earlier blog SQL SERVER – WMI Error 0x80041017 – Invalid Query Using WBEMTest
  3. Compile MOF file related to SQL Server configuration manager.
    1. Open a command prompt as administrator
    2. Navigate to your SQL version’s shared directory (cd ):
      SQL 2005: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\
      SQL 2008 R2: C:\Program Files (x86)\Microsoft SQL Server\100\Shared\
      SQL 2012: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
      SQL 2014: C:\Program Files (x86)\Microsoft SQL Server\120\Shared\
      SQL 2016: C:\Program Files (x86)\Microsoft SQL Server\130\Shared\
    3. Then run the following command:
      mofcomp sqlmgmproviderxpsp2up.mofHere is the sample outputMicrosoft (R) MOF Compiler Version 6.2.9200.16384
      Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
      Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\130\Shared\sqlmgmproviderxpsp2up.mof
      MOF file has been successfully parsed
      Storing data in the repository…
  4. Recompile winwin32
    Mofcomp.exe %windir%\system32\wbem\cimwin32.mof
    And restart WMI Service.

I truly hope that the above steps should fix the issue for others also. If you find some other solution, please share via comments.

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

SQL Error Messages, SQL Server, SQL Server Configuration, WMI
Previous Post
SQL Server – Formatted Date and Alias Name in ORDER BY Clause
Next Post
SQL SERVER – New Way to Use DBCC Page in SQL Server 2019

Related Posts

2 Comments. Leave new

  • I also had the same problem. I was able to solve it easily by changing the path of the shortcut.
    The console being called referred to file
    “C:\Windows\SysWOW64\mmc.exe /32 C:\Windows\SysWOW64\SQLServerManager10.msc ”
    and I changed this into file
    “C:\Windows\SysWOW64\mmc.exe /32 C:\Windows\SysWOW64\SQLServerManager11.msc”.
    Problem solved.
    You’re welcome :)

  • SnakesOnAPlane
    July 24, 2020 9:52 pm

    Much easier and simpler fix: Open a command prompt window (Run as Administrator) and change the directory (cd) to %windir%\System32\wbem, then enter the following command (copy/paste):

    FOR /f %s in (‘dir /b /s *.dll’) do regsvr32 /s %s
    Net stop /y winmgmt
    FOR /f %s in (‘dir /b *.mof *.mfl’) do mofcomp %s
    Net start winmgmt


Leave a Reply