MMC fails to load event viewer in RTM
- when I try to invoke the event viewer I get the following error:
MMC could not create the snap-in.
Name: Event Viewer
CLSID: FX:{b05566ad-fe9c-7a4cbb7cb510}
This is a new installation of Windows Vista Ultimate from MSDN (RTM).
Any ideas how to fix this? how to re-register the snap-in?
thanksdavid
Answers
After typing this I found a mmc.exe.config file that was forcing the version of .net. Renaming the file fixed my problem.
You rock! I spent a long time trying to figure this one out. An application (Peachtree accounting) installed the .net 1.1 framework and hosed many of my MMC snap in's including event viewer, task scheduler and IIS 7 admin.
I looked in my system32 folder and sure enough there was an mmc.exe.config file that had the supported runtime section set to "v1.1.4322". I couldn't seem to edit the file to comment out that section, vista wouldn't let me save it, but it did let me rename it to mmc.exe.config.BAK and sure enough everything started working again. I'm guessing these problems with mmc and snap in's in Vista are all related to apps that install the .net 1.1 framework and windows vista's inability to protect that mmc.exe.config file.
Cheers to you!
All Replies
- do you have problem with others plug-in?
- No, all other admin snap-ins work ok
How about using this command to open event viewer?
eventvwr.exe
or
mmc.exe X:\WINDOWS\system32\eventvwr.msc
It's not a dll. So, if it really fail, you may need to copy that file from the source disc or another company to see whether it can work.
I have tried different ways, but it doesn't work.
from cimputer management, from Event Viewer sortcut in Admins tolls, from command line lik you say, from an empty MMC and triying to add Event View snap-in.
Allways a get the same result.
thanks
Hi, do you have office 07 installed to your system?
And, do you have another VIsta installation which got no problem on the event viewer? If so, you can try to copy the event viewer exe form there.
Besides, you can also try to move the event log file to other location first. If event viewer find the event log file disappear, it will re-create a new set of file. See whether it can help to fix the problem.
One more thing to try is run event viewer in this way:
use "runas administrator" to run "Command Prompt", then execute eventvwr.exe in there.And, did you try to run event viewer in Safe Mode? Does it got problem also?Also, please check your user account too, make sure your acocunt is not in the Guests local group.- Have you found a solution? I am having the same problem. I do have Office 2007, but no other vista installs. This is on Vista Business downloaded from our MVL
- Another point of note.
If I start mmc by itself, then add/remove snap-ins, and add the Event Viewer Snapin I get the following message:
MMC Cannot initialize the snap-in because the snap-in requires version v2.0.50727 of the .Net framework and version v1.1.4322 is already loaded. - After typing this I found a mmc.exe.config file that was forcing the version of .net. Renaming the file fixed my problem.
Your error message is difference with him.
By the way, where you find that file? I don't find this file on my system.
Yes, I have office 2007 rtm
Yes, my partners are running Vista without this issue. I have copy eventvwr.exe from him computer, but still doesn't woks.
Their computers can open my log files...
with runas and cmd... same result
with safe mode... same result
My account is in administrators group only.
I am sure that this is not for a permissions problem. All others admin snap.ins work fine.
I think that I need some wayto re register the snap-in...
thanks
After searching on the net, I find a simular problem about event viewer, which was about atl.dll
Please reference here:
http://support.microsoft.com/kb/912651/en-us
See whether it can help.
I also find a KB which was about MMC:
http://support.microsoft.com/kb/271135/en-us
Hope it can help you too.
By the way, is it a clean install? no other third party software and driver?
I had created it for another snapin
c:\windows\system32\mmc.exe.config
ic. but seem can't solve the problem of the others.
- Did you guys solve it? I'm having the same problem here. Office 2007 installed too.
- No, sorry, I still have the problem
- How about calling the support service of MS?
I also have this same issue when I try to invoke the event viewer I get the following error:
MMC could not create the snap-in.
Name: Event Viewer
CLSID: FX:{b05566ad-fe9c-7a4cbb7cb510}Could it be related to msde 2000?
Could it be related to .net installations?Has anybody found a resolution?
- I think no solution yet. Please report the problem to MS support service.
After typing this I found a mmc.exe.config file that was forcing the version of .net. Renaming the file fixed my problem.
You rock! I spent a long time trying to figure this one out. An application (Peachtree accounting) installed the .net 1.1 framework and hosed many of my MMC snap in's including event viewer, task scheduler and IIS 7 admin.
I looked in my system32 folder and sure enough there was an mmc.exe.config file that had the supported runtime section set to "v1.1.4322". I couldn't seem to edit the file to comment out that section, vista wouldn't let me save it, but it did let me rename it to mmc.exe.config.BAK and sure enough everything started working again. I'm guessing these problems with mmc and snap in's in Vista are all related to apps that install the .net 1.1 framework and windows vista's inability to protect that mmc.exe.config file.
Cheers to you!
johnc999 wrote: After typing this I found a mmc.exe.config file that was forcing the version of .net. Renaming the file fixed my problem.
You rock! I spent a long time trying to figure this one out. An application (Peachtree accounting) installed the .net 1.1 framework and hosed many of my MMC snap in's including event viewer, task scheduler and IIS 7 admin.
I looked in my system32 folder and sure enough there was an mmc.exe.config file that had the supported runtime section set to "v1.1.4322". I couldn't seem to edit the file to comment out that section, vista wouldn't let me save it, but it did let me rename it to mmc.exe.config.BAK and sure enough everything started working again. I'm guessing these problems with mmc and snap in's in Vista are all related to apps that install the .net 1.1 framework and windows vista's inability to protect that mmc.exe.config file.
Cheers to you!
Thx for you testing! Now, we can have a solution for this problem.
- Worked for me too, I also have Peachtree installed.
- The renaming of mmc.exe.config worked for me! I was getting the exact same error, renamed the file, all now working. The config file was forceing version v1.1.4322. Cheers. Adrian
- I my case it wasn't mmc.exe.config, but machine.config itself. I solved the issue (and many other things that were not working) by reverting maching.config to machine.config.default.
- John,
I've been working on this problem for days when I was directed to this site. I also have this issue with the Event Viewer and Task Scheduler. I was thrilled to see that many of you were able to resolve this by renaming the file but I can NOT rename the MCC.exe file. Would anyone here know why I can't rename that file.
I am running Vista Home Premium. This has become a very frustrating ordeal and wonder why Microsoft doesn't deal with it on their site. Would you know? Hi
I had this problem, but now fixed. I found it was working after dealing with "permissions" issues on windows registry keys on matters concerning un-install failure problems with Adobe8 and I-tunes. I re-set permissions on keys that windows advised were preventing the un-install until the problem went away. Hope this helps. Good luck.
- I share the anteprevious poster's problem and your advice didn't make the least sense to me. Does anyone know how to revert the machine.config file to the default configuration on Vista? When I try to rename this file I get a series of popups ending with one that says "You need permission to perform this action".
I was never able to solve it. ended up reinstalling vista.Theres one and only one solution:
You will have to recreate the environment variable PATH.
In Windows Vista go to Computer Properties and on the left pane click on Advanced System Settings. Click on Environment Variables.
Under System variables, scroll down and look for the variable named "Path". Select the entry and delete it and click on OK. Click on OK again to the system properties window.
Now return back to the same place and click on "New" under System variables and set the values:
Variable name: Path
Variable value: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
Then everything should work fine.
Its a weird solution for the problem!
I have the same problem. However I changed the path variable and it doesn't work.
I didn´t find any mm.exe.config under c:\windows or any of its sub folders
Additionally, I have found 3 machine.config.default files, under .net framework 2.0 directories (v2.0.50727 and v2.0.50215) and x86_netfx_config_ocm..... folder. Wich I have to restore?
dc366 wrote: Theres one and only one solution:
You will have to recreate the environment variable PATH.
Recreating the path worked for me. Thanks!
- I am having the same issue after performing a repair installation of .NET Framework 3.5 on Windows Vista x64 after another issue. Since this I am having a lot of issues with Visual Studio 2008 as well where packages no longer load or where .NET applications crash or no longer start ...
- Thank you man, you save my life !
Gabriel Lozano-Moran wrote: I am having the same issue after performing a repair installation of .NET Framework 3.5 on Windows Vista x64 after another issue. Since this I am having a lot of issues with Visual Studio 2008 as well where packages no longer load or where .NET applications crash or no longer start ...
I'm also having this problem where .NET applications crash or don't start (and the problem in the thread title as well, of course). I looked for a mmc.exe.config file but don't have one, and there's not a machine file in the main system32 folder.
I also recreated the path to no avail.- I have this problem and do not have a mmc.exe.config file anywhere. However I do have some dll files created by Microsoft Visual Studio.NET in C:\Program Files\Microsoft.Net\ Primary Interlop Assemblies and they are dated from 2002. Could this be a problem? I have no corresponding files anywhere. They are msdatascr.dll, stdole.dll and adodb.dll. There are several services that willnot start like secure socket,
- mmc.exe.config and EventViewer.dll does not exist
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510}]
"Type"="Microsoft.EventViewer.SnapIn.EventViewerSnapIn, EventViewer, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
"ApplicationBase"="C:\\Windows\\system32\\"
"NameString"="Event Viewer"
"Description"="Displays monitoring and troubleshooting messages from windows and other programs."
"ModuleName"="EventViewer.dll"
"AssemblyName"="EventViewer"
"RuntimeVersion"="v2.0.40607"
"FxVersion"="2.0.0.2"
"HelpTopic"="C:\\Windows\\Help\\eventviewer.chm"
"LinkedHelpTopics"="C:\\Windows\\Help\\eventviewer.chm"
"About"="{00000000-0000-0000-0000-000000000000}"
"NameStringIndirect"=hex(2):40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
00,77,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
6d,00,69,00,67,00,75,00,69,00,72,00,65,00,73,00,6f,00,75,00,72,00,63,00,65,\
00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,00,30,00,31,00,00,00
"DescriptionStringIndirect"=hex(2):40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
00,5c,00,6d,00,69,00,67,00,75,00,69,00,72,00,65,00,73,00,6f,00,75,00,72,00,\
63,00,65,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,00,30,00,32,00,00,00
"ProviderStringIndirect"=hex(2):40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,\
00,6f,00,77,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\
5c,00,6d,00,69,00,67,00,75,00,69,00,72,00,65,00,73,00,6f,00,75,00,72,00,63,\
00,65,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,00,30,00,33,00,00,00
"VersionStringIndirect"=hex(2):40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,\
6f,00,77,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,69,00,67,00,75,00,69,00,72,00,65,00,73,00,6f,00,75,00,72,00,63,00,\
65,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,00,30,00,34,00,00,00
"IconIndirect"=hex(2):40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,\
00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
69,00,67,00,75,00,69,00,72,00,65,00,73,00,6f,00,75,00,72,00,63,00,65,00,2e,\
00,64,00,6c,00,6c,00,2c,00,2d,00,35,00,30,00,30,00,00,00
"FolderBitmapsColorMask"=dword:00ff00ff
"LargeFolderBitmapIndirect"=hex(2):40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
00,5c,00,6d,00,69,00,67,00,75,00,69,00,72,00,65,00,73,00,6f,00,75,00,72,00,\
63,00,65,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,35,00,30,00,31,00,00,00
"SmallFolderBitmapIndirect"=hex(2):40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
00,5c,00,6d,00,69,00,67,00,75,00,69,00,72,00,65,00,73,00,6f,00,75,00,72,00,\
63,00,65,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,35,00,30,00,32,00,00,00
"SmallSelectedFolderBitmapIndirect"=hex(2):40,00,43,00,3a,00,5c,00,57,00,69,00,\
6e,00,64,00,6f,00,77,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,\
00,32,00,5c,00,6d,00,69,00,67,00,75,00,69,00,72,00,65,00,73,00,6f,00,75,00,\
72,00,63,00,65,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,35,00,30,00,33,00,00,\
00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510}\NodeTypes]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510}\NodeTypes\{33F2C345-BF11-41b6-90DA-4FB4963EA4E2}]
@="Classic Viewer Root Node"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510}\Standalone]
