Error in Failover Cluster Manager after install of KB2750149

Error in Failover Cluster Manager after install of KB2750149

  • Comments 7
  • Likes

On Tuesday, Jaunary 8, the below recommended fix was released and available on Windows Update for Windows .NET Framework 4.5.

2750149
An update is available for the .NET Framework 4.5 in Windows 8, Windows RT and Windows Server 2012
http://support.microsoft.com/kb/2750149/EN-US

When installing this update to a Windows 2012 Cluster Server, you will receive the below error when you select Roles or Nodes from within Failover Cluster Manager.

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

You can still manage your Cluster from a node that does not have this fix or through Powershell.  The recommendation at this time is to remove and not install this fix. 

Microsoft is aware of the issue.  Once the cause has been identified and a resolution available, this blog will be updated to reflect the resolution.

 

==========
UPDATE - January 23, 2013
==========

This issue has been resolved.  After installing the KB2750149 patch for .NET Framework, please also install the below patch.

KB2803748
Failover Cluster Management snap-in crashes after you install update 2750149 on a Windows Server 2012-based failover cluster
http://support.microsoft.com/kb/2803748

 

John Marlin
Senior Support Escalation Engineer
Microsoft Enterprise Platforms Support

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Fix has already been released, please update this post :

    support.microsoft.com/.../2803748

  • Yes, it works thanks for the post

  • Thanks it works.

  • This worked awesome! Thanks.

  • I had the same problem and installed the update KB2803748, now everything works fine. But KB2750149 isn't installed. Is it possible, that there is another source causing this problem?

  • This fix is for windows 2012 not for windows 2012 R2