Thursday 10 January 2013

Update KB2750149 Breaks Hyper-V 2012 Failover Clusters

It seems that a recent update is wreaking havoc on Hyper-V 2012 Failover Clusters.

If updates have not been run as of yet then avoid this one.

If things are not working as expected after a round of updates and this one was included uninstall and hopefully things come up as they should.

Error quote from the Forums post:

A weak event was created and it lives on the wrong object, there is a high chance this will fail, please review and make changes on your code to prevent the issue.

Version=1
EventType=AppHangB1
EventTime=130022261829914481
ReportType=1
Consent=1
ReportIdentifier=26cc3e6a-5a82-11e2-93f7-782bcb53a584
IntegratorReportIdentifier=26cc3e6b-5a82-11e2-93f7-782bcb53a584
NsAppName=mmc.exe
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=mmc.exe
Sig[1].Name=Application Version
Sig[1].Value=6.2.9200.16384
Sig[2].Name=Application Timestamp
Sig[2].Value=50109efd
Sig[3].Name=Hang Signature
Sig[3].Value=5707
Sig[4].Name=Hang Type
Sig[4].Value=138496
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.2.9200.2.0.0.400.8
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=5707c224bfa37e5b267a1680ece79add
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=c8c0
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=c8c0bc8698a6964e5cded02ffc06ca16
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=5707
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=5707c224bfa37e5b267a1680ece79add
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=c8c0
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=c8c0bc8698a6964e5cded02ffc06ca16
UI[3]=Microsoft Management Console is not responding
UI[4]=Windows can check online for a solution. If you close the program, you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution and close the program
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Management Console
AppPath=C:\Windows\System32\mmc.exe
ReportDescription=A problem caused this program to stop interacting with Windows.
NsPartner=windows
NsGroup=windows8

We tend to wait on updates with our managed clients.

It seems that regression testing for updates has not been up to the same standard it has been in the past at Microsoft.

So, we test here in-house beforehand. It is a part of our service offering.

Hat Tip: SBS Diva

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer

No comments: