Error in Failover Cluster Manager after install of KB2750149

  • Artigo

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
https://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
https://support.microsoft.com/kb/2803748

 

John Marlin
Senior Support Escalation Engineer
Microsoft Enterprise Platforms Support

Comments

  • Anonymous
    January 23, 2013
    Fix has already been released, please update this post :support.microsoft.com/.../2803748
  • Anonymous
    July 28, 2013
    Yes, it works thanks for the post
  • Anonymous
    October 22, 2013
    Thanks it works.
  • Anonymous
    October 26, 2013
    This worked awesome! Thanks.
  • Anonymous
    December 02, 2013
    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?
  • Anonymous
    January 10, 2014
    If you are running, or going to run in the future, SQL Server inside Azure Virtual Machines, your favorite
  • Anonymous
    September 07, 2014
    This fix is for windows 2012 not for windows 2012 R2
  • Anonymous
    January 12, 2015
    Thank you
  • Anonymous
    December 09, 2015
    Why win2012R2 doesn't have this issue?
  • Anonymous
    December 09, 2015
    Why win2012R2 doesn't have this issue?