SQL SERVER – Configuration Manager – MMC could not create the snap-in. The snap-in might not have been installed correctly

I have always felt the social media has a bigger impact on the current generation. It can easily spoil their time on one side or it can be awesomely productive if utilized the right way. As there are two sides to the coin, social media also have a similar effect on people. I have personally wanted to see the bright side because it gets access to people easier now. The space for being private has decreased and we can easily be web searchable. Whenever I get time, I try to help on public forums and even on my Facebook page of SQLAuthority. Recently, one of the friendliest contacted me with below error while opening configuration manager over Facebook. He was using SQL Server 2016 so I got excited and wanted to see what was the problem. We got into a Skype call and I was guiding him through the troubleshooting process:

Here is an important informational error:

MMC could not create the snap-in CLSID: {EE7F2DDB-1319-4227-8FD4-4EB51615D34A}

Note: this trick should work with all MMCs failures. GUID depends on MMC. In this case it’s for SQL Server 2016.

MMC stands for Microsoft Management Console and can be opened via mmc.exe. One MMC is opened, we can load the snap-in.

If you are not having “SQL Server Configuration Manager” in start menu, then you can add below shortcut.

C:\Windows\SysWOW64\mmc.exe /32 C:\Windows\SysWOW64\SQLServerManager13.msc

“SQLServerManager13.msc” in the above command is the Snap-in for SQL Server 2016. Below table shows the file name for previous versions.

For this client, I have tried below: (again 130 is for SQL Server 2016)

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

Some site on internet asked to reset .net security. I have tried that also but it didn’t help.

C:\Windows\Microsoft.NET\Framework64\v2.0.50727> caspol.exe -all -reset

Finally, I have used Process Monitor and found that snap-in uses below registry key.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MMC\SnapIns\{EE7F2DDB-1319-4227-8FD4-4EB51615D34A}

We found that DLL was missing from that location. We found two solutions:

1. Pick SQLManager.dll from another machine having the same version of SQL Server.
2. Repair Shared components of SQL Server.

Since it was a test server, we went with option 1 and then we were able to open SQL Server Configuration manager. This is one more incident where tools like Process Monitor has helped me get to the bottom of the problem. Have you used Process Monitor to troubleshoot some issue? I am sure you will get innovative methods to use them.

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

The post SQL SERVER – Configuration Manager – MMC could not create the snap-in. The snap-in might not have been installed correctly appeared first on Journey to SQL Authority with Pinal Dave.