Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

Bob Jones — Mon, 16 May 2011 09:21:35 GMT

Why is the broken version of this hotfix still being distributed by Microsoft? I sync'd my WSUS server 2 weeks after the fixed version was released and still got the broken version.

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

Girts — Tue, 10 May 2011 12:52:51 GMT

"I've followed the instructions in KB2540222 to determine that we have the 'broken' hotfix, but I can't install the 'fxed' hotfix as it says we have no affected products installed. "

Same problem.

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

Nigel Freeman — Fri, 06 May 2011 09:13:05 GMT

I've followed the instructions in KB2540222 to determine that we have the 'broken' hotfix, but I can't install the 'fxed' hotfix as it says we have no affected products installed. For now I have just removed the current patch but that still leaves us with the broken hotfix in place and I'm concerned this will hit us again unless I can fix the root cause. Any suggestions?

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

Frank T — Wed, 20 Apr 2011 14:15:45 GMT

So if we never installed it, we need to install the -v2 patch from those project/development sites and then install the original MS11-28 patch? I'm confused.

Will the -v2 eventually be put out for auto updates?

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

Nino Bilic [MSFT] — Tue, 19 Apr 2011 23:13:51 GMT

Folks, I just made an update to the blog post with links to fixes that will resolve this situation for you.

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

fucifino — Tue, 19 Apr 2011 19:37:28 GMT

On XCH 2010 SP1/WIN 2K8 SP2 besides the symptoms outlined above, KB 2449742 breaks Outlook 2011 (fanboys beware) connectivity.

Outlook 2011 will not connect until KB 2449742 is removed (and server restarted). We did not have any problems with Outlook 2010.

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

Joe — Mon, 18 Apr 2011 22:54:20 GMT

I've run into this on my 2008 SP2 box running Exchange 2010 SP1.

Looking forward to a fix to the fix :-)

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

Peter O. — Mon, 18 Apr 2011 20:38:48 GMT

I can confirm that this hoses up Exchange 2007 Sp3 machines too. Has similar behavior to a bad .net patch installer from the last patching period. I was able to fix that by copying the machine.config from an unpatched system.

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

Jeff — Mon, 18 Apr 2011 02:48:10 GMT

It also leaves thes bombs in the System Log:

Source: Microsoft-Windows-WAS

Event ID: 5009

Description:

A process serving application pool 'MSExchangeAutodiscoverAppPool' terminated

unexpectedly. The process id was '8504'. The process exit code was '0x80131506'.

Source: Service Control Manager

Event ID: 7031

Description:

The Microsoft Exchange Mailbox Replication service terminated unexpectedly.

It has done this 1 time(s). The following corrective action will be taken in 5000

milliseconds: Restart the service.

Source: Microsoft-Windows-WAS

Event ID: 5011

Description:

A process serving application pool 'MSExchangeAutodiscoverAppPool' suffered a

fatal communication error with the Windows Process Activation Service. The process

id was '9032'. The data field contains the error number.

re: Exchange 2010 management tools do not start after the installation of .NET hotfix KB 2449742

April — Sat, 16 Apr 2011 06:09:47 GMT

This update killed OWA on my friend's Exchange 2007 installation. Attempts at access create event 64 in the log, and show the following to the user: "Outlook Web Access did not initialize. An event has been logged so that the system administrator can resolve the issue. Please contact technical support for your organization." The update ate his IIS config and created AD replication issues as well. IIS and AD weren't too difficult to fix, but OWA stubbornly refuses to come to life.

I'll be very interested in hearing more of your findings while I try to help him troubleshoot his issue. I am not sure in his case that removing the update would undo the damage. We'll probably try to remove and recreate the default owa site.