Windows – MMC crashes on Windows Server 2008 x64 – Exchange console, event viewer

netwindowswindows-server-2008

Help!

I don't know what happened; this server has been very reliable but suddenly began having problems with a particular .NET 2.0 web site simply hanging – it wouldn't load at all. However, another ASP.NET site was still fine. Reinstalling the site didn't fix it, nor did deleting and re-creating the application within IIS.

Trying the event viewer was met with a horrifying "Microsoft Management Console has stopped working".

Some Googling led me to believe the .NET framework was the problem. I found a tool called the .NET cleanup tool – http://blogs.msdn.com/astebner/pages/8904493.aspx – which cleaned out .NET entirely. I reinstalled .NET 1.1 and 3.5 (which installed 2.0 and 3.0 as well). Using the .NET verification tool – http://blogs.msdn.com/astebner/pages/8999004.aspx – I believe these have all installed ok.

However, my server is in worse shape now. The Exchange 2010 Management Console crashes with an MMC error and now my other (previously reliable) .NET web app now hangs on loading too.

I thought I should use Computer Management to remove and re-add the application and web server roles but sure enough, MMC crashes.

If anyone can help I will be extremely grateful.

Thank you !

Best Answer

Best call Beau Murray from Arion Systems :) nah seriously

http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/f12e749a-da9d-4ddc-b74f-fb12597b8324

Uninstall KB2449742

Related Solutions

Windows – Useful Command-line Commands on Windows

A little known one is

getmac

It shows the MAC address(es) of your network adapter(s).

Screenshot of running getmac from a Windows commandline window.

Error installing dotnet framework 3.5 SP1 on windows 2008

Normally you just need to make sure that you have .NET installed and then Windows Update will lead you through all of the update. However I've run into failures like yours on about 1 in 50 servers, so the trick is to figure out the best path to navigate for your situation.

You're on the right path. Here's what I suggest:

For the WS08 server, I would uninstall the .NET Framework completely and then build back up again. To do so, use Add/Remote programs to uninstall any of the service packs that you see there. Then from Server Manager go to -> Roles -> Web Server (IIS) -> Remove Role Services -> and remove "ASP.NET" and ".NET Extensibility" (and accept the prompt to remove dependencies). After that completes, perform a reboot if it asks for one.

Then, from Server Manager again, add a role service and add those back again. Then use Windows Update, but step through the service packs in order. Don't assume that the cumulative installs will work since you already know that you're a fringe case.

For the Vista computer, if you haven't already, I suggest the Windows Update path there too. If that dead-ends, then start here: http://www.microsoft.com/net/Download.aspx. Make sure that you do have .NET 2.0 installed. (just check c:\windows\microsoft.net\framework\v2.0.50727 and make sure it has the full set of files.).

Then install 3.5 (not SP1 yet): http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en

Finally 3.5 SP1: http://www.microsoft.com/downloads/details.aspx?FamilyId=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en

Hope that helps.

Related Topic