Event Viewer Error Mmc Could Not Create Snap-in
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 08:10:28 GMT by s_ac15 (squid/3.5.20)
Snap-in The Microsoft Management Console (MMC) is an application that provides a graphical-user interface (GUI) and a programming
Windows 7 Event Viewer Snap In Not Responding
framework in which consoles (collections of administrative tools) can be created, saved, mmc cannot initialize the snap in event viewer windows 7 and opened. MMC was originally released as part of the Windows 98 Resource Kit, and is included
Event Viewer Mmc Could Not Create The Snap-in Server 2008
on all later versions. It uses a Multiple Document Interface (MDI) in an environment similar to Microsoft's Windows Explorer. MMC is considered to be a container for the actual http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/event-viewer-mmc-could-not-create-the-snap-in/7c9aaea1-e0b7-42fd-adc0-f7d0b3f22c3d operations, and is known as a "tools host." It does not, itself, provide management, but rather a framework in which management tools can operate. Sometimes, there may be a possibility of scenario in which some snap-ins may not work properly. Especially, if the registry configuration of a snap-in is broken (note that Registry Editor is not a snap-in), the http://troubleshooter.xyz/fix-mmc-could-not-create-the-snap-in/ snap-in initialization would fail. In this case, you’re likely to get following error message (an specific message in case of Event Viewer): MMC could not create the snap-in. The snap-in might not have been installed correctly. Let's see how to fix MMC Could Not Create The Snap-in error via following method: Method 1: Turn on the Microsoft .net Framework Right click on the windows button and select control panel. Click on programs. Now select "Turn Windows features on or off" under Programs and Features. Now select “Microsoft .net Framework 3.5". You have to expand each component and check the ones you want to turn on. Restart the computer and check if the issue is fixed if not then go to the next step. You may run the system file checker tool once again. It might fix the issue. How to use system file checker tool. The above method might fix the MMC Could Not Create The Snap-in error but if it doesn't then follow the next method. Method 2: Registry fix Press windows + R key simultaneously
Creating your account only takes a few minutes. Join Now I did a fresh install of Windows 7 Enterprise (RTM) on my manager's PC (!), making https://community.spiceworks.com/topic/78696-mmc-could-not-create-the-snap-in-windows-7-can-t-load-event-viewer-and-more his old HD with XP a slave and installing a new master HD. As has been also my experience with Windows Server 2008, the initial install went so quickly and smoothly that http://serverfault.com/questions/325067/windows-firewall-mmc-could-not-create-the-snap-in you know it's too good to be true. (Pardon the cynicism. . . nearly 20 years of dealing with Microsoft products has left me with a certain expectation.) I believe this trouble event viewer stems from an installation of Peachtree Premium Accounting 2007 on this workstation, because it installed a version of .Net Framework 1.1. I can't guaranty it, but I have a sense that the trouble began there. In any case, this PC has SQL Server Enterprise 2008 installed, and at least one application that requires .NET FX 3.5 SP1. What I'm seeing is the following: 1. When trying not create the to open the event log: "MMC could not create the snap-in. The snap-in might not have been installed correctly. Name: Event Viewer CLSID: FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510}" 2. When I attempt to reinstall .NET 3.5 nothing happens. The installer application never does anything. 3. When I attempt to apply .NET 3.5 SP1, the files extract, then the application "disappears". 4. When I attempt to install our product (we're a software company - ironically a Microsoft partner) I get far enough to enter the SQL server credentials and test the connection, which succeeds, but then when the files are being extracted for installation it gets to a certain point and then rolls back the installation. 5. Windows activation fails with the following error: Windows Activation A problem occurred when Windows tried to activate. Error Code 0x8007232B. Code: 0x8007232B Description: DNS name does not exist. (Note that the above "DNS error" is not likely a problem with our DNS. All settings and messages relating to the domain DNS look as expected, and I'm seeing nothing that would be consistent with a do
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Windows Firewall: MMC could not create the snap-in up vote 0 down vote favorite On Windows Server 2008 when trying to open either Event Viewer or Windows Firewall settings, I'm getting the following error: MMC could not create the snap-in. The snap-in might not have been installed correctly. Name: Windows Firewall with Advanced Security CLSID: FX: {b05566ac-fe9c-4368-be02-7a4cbb7cbe11} windows-server-2008 windows share|improve this question edited Sep 7 '13 at 22:06 Uwe Keim 92031534 asked Oct 26 '11 at 19:20 Kyberias 10111 add a comment| 3 Answers 3 active oldest votes up vote 0 down vote Had this same error, had to ring Microsoft support to get it worked out. Had to install kb2688730 to resolve the issue. The KB article for kb2688730 doesn't address the error message but it does resolve the issue (have done this on 20+ 2008R2 boxes now). The cause was as follows: As far as we can tell, either the patch installation on the affected servers was interrupted in some way, or did not complete properly, causing .Net corruption on the servers. share|improve this answer answered Dec 6 '12 at 0:36 Mark 436 add a comment| up vote -1 down vote Seems that there are some snapins/dll corrupted ... Have you tried to run a scandisk ? (sfc /scannow) if the scandisk doesn't resolve the problem try registering the snapins dll : Open a command prompt with administrative privileges Copy and paste the following commands into the elevated command prompt, or you can save the commands into a batch file, and then execute the batch script: regsvr32 /s adprop.dll regsvr32 /s azroles.dll regsvr32 /s azroleui.dll regsvr32 /s ccfg95.dll regsvr32 /s certadm.dll regsvr32 /s certmmc.dll regsvr32 /s certpdef.dll regsvr32 /s certtmpl.dll regsvr32 /s certxds.dll regsvr32 /s cladmwiz.dll regsvr32 /s clcf