MMC Snap-in will not load most processes and throws an error on Windows 2008R2 x64. It gives the error:

mmc could not create the snap-in. CLSID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb} when opening server manager.

It also gives similar errors opening the event viewer, etc. I think that the .NET Framework is messed up but I can't narrow down the exact cause. Has anyone else seen this issue? I have a dmp file of mmc.exe but haven't been able to get anything meaningful out of it.

7 Answers

I know this is an old post, but I ran into the same issue and tried everything I could find on the internet regarding this. After working with Microsoft for 3 days we found the fix. Please see below for all the steps that were completed, and finally what solved the issue. This was for a Server 2008R2 machine:

Symptoms

MMC could not create the snap-in. The snap-in might not have been installed correctly.

Name: Server Manager

CLSID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb}

Name: Event Viewer

clsid: fx: {b05566ad-fe9c-4363-be05-7a4cbb7cb510} Event Viewer

Name: Task Scheduler

clsid: fx: {c7b8fb06-bfe1-4c2e-9217-7a69a95bbac4} Task Scheduler

Name: Windows Firewall with Advanced Security

clsid: fx: {b05566ac-fe9c-4368-be02-7a4cbb7cbe11} Windows Firewall with Advanced Security

Server Information

Microsoft Server 2008R2 SP1

HP ProLiant DL380G6

Resolution

• Replaced C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config with known working file

• Replaced entire C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\ folder with known working folder

• Ran System Update Readiness Tool for Server 2008 – all reports came back with no error

• Ran c:\Windows\Microsoft.NET\Framework\v3.5\WFServicesReg.exe /r /b

• sfc /scannow was ran, came back clean

• Ran .NET Verifier on all version of .NET, all came back verified successfully

• Reinstalled .NET 3.5 via CLI:

  DISM /online /disable-feature /FeatureName:NetFx3
  DISM /online /enable-feature /FeatureName:NetFx3

• Removed registry keys:

  HKLM\Software\Microsft\OLE\MachineAccessRestriction HKLM\Software\Microsft\OLE\MachineLaunchRestriction

• Restarted “Start DCOM Server Process Launcher” service

• Replaced files dsadmin.dll and dssite.msc located at C:\Windows\winsxs\x86_microsoft-windows-d..mc-sitesandservices_31bf3856ad364e35_6.1.7601.17514_none_a143f244c78549c1 with a good know version

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMCSnapIns\FX{b05566ad-fe9c-4363-be05-7a4cbb7cb510}\RuntimeVersion, changing value from v2.0.40607 to v2.0.50727

Final resolution from Microsoft:

• The Servicing stack of the Operating System was clean as reported by the Sfc output
• Uninstalling/Reinstlaling Visual C++ 2005/2008/2010 with a reboot took out of the picture Visual C++ library components
• The .Net Policy had the correct value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\v2.0 - 50727=50727-50727
• Uninstalling McAfee didn’t help even after a reboot.

• The Components and Schema hive unloaded after a few reboots

• The IDNA trace that we gathered indicated that we fail due to a bad function pointer most probably returned by a .net component. After applying the Update and a reboot the issue went away which indicates we have a broken/damaged .net component on the server.

Check out this thread. It sounds like a corrupted update.

3

I was having same issue, but it worked just fine, when i removed .Net 3.5 from my system, and just by that removal everything got back to normal .. this looked to be a problem with .net itself, i have not tried to install 3.5 again when i will do that will update the thread

1

Look for the corrupted snapin and remove the key after backup

Example for Task scheduler

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{c7b8fb06-bfe1-4c2e-9217-7a69a95bbac4}] and [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{c7b8fb07-bfe1-4c2e-9217-7a69a95bbac4}]

Per Akira Umehara's answer on this thread, another solution is:

1. Navigate to the following directory on the corrupt machine: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG
2. Copy the machine.config file to desktop just in case before you go to 3rd step.
3. Rename machine.config to machine.config.old (in the original directory: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG).
4. Reboot (not always required, but ensures a clean start).

NB: The above applies to x64 operating systems. For x86, do the same only using the directory: C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\.

I get the impression this only works for OSes not yet upgraded to .net framework 4 was released; though have found nothing explicitly to confirm this.

Noticing Issue and Initial Findings

I had the same issue on Windows Server 2008 R2; I believe caused by a failed Windows Update attempt; failing due to a full C drive.

• Freed up space on C drive
• Tried all techniques mentioned on here and in this blog, with no joy (mentioning as these may have partially resolved the issue).
• Noticed that the .Net Verification Tool crashed when run on .net versions =v4.
• Noticed that c:\windows\assembly was displaying sub-folders instead of the standard GAC view (potentially due to a missing desktop.ini, though I did not realise at the time)
• Noticed that some apps were reporting a missing dll (Microsoft.VisualStudio.OLE.Interop).

Steps to fix

• Ran Windows Explorer as Admin
• Copied the GAC (c:\windows\assembly) from a the VM from which this server had originally been cloned, ensuring missing files were created in the GAC, but existing content was left unimpacted (I generally wouldn't recommend this; but the server was not vital, and all other routes had been exhausted). NB: The source VM included the missing Microsoft.VisualStudio.OLE.Interop DLL.
• Rebooted

This resolved several issues:

• The GAC now displayed as expected
• The missing DLL issue was resolved (i.e. the DLL was there; and we no longer saw exceptions related to this DLL)
• The .Net Verifier ran for all versions of .net; and reported all as healthy.

However, the original issue (per question) remained.

• Reran the below commands to again remove and re-add the .net 3.5 feature:

  DISM /online /disable-feature /FeatureName:NetFx3
  DISM /online /enable-feature /FeatureName:NetFx3

• The disable command failed; but enable completed successfully

• The issue was resolved; presumably the enable-feature command somehow kicked something missed by the GAC copy into place...

I had the same error a few minutes ago on one of five identically installed, and I just updated Windows Server 2008 R2 Terminal Servers and now it works again.

All I did was go to File > Options and then I deleted the about 460 KB of files stored in the user profile, confirmed the dialog, closed the MMC. After reopening, everything is working fine again.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy