locked
KB2750149 breaks Windows 2012 Failover Cluster Manager RRS feed

  • Question

  • After installing KB2750149 on one of our cluster nodes the UI would no longer function properly in the following way:

    The Failover Cluster Manager will start, I can select Nodes and it will list the nodes, once I select a Node I get an very long exception message stating that "a weak event was created and it lives on the wrong object.....".  From there a dialog pops up that never goes away and I have to end the task.

    I uninstalled KB2750149 and the UI works fine as before.

    I have no idea if the update is revealing a problem in the Failover Cluster Manager or if the update is buggy, either way please fix this.  

    Thanks!


    • Edited by Ginno2k9 Wednesday, January 9, 2013 8:55 PM
    Wednesday, January 9, 2013 8:05 PM

Answers

  • Thank you for the post, we are aware that the hotfix KB2750149 http://support.microsoft.com/kb/2750149 which was just released yesterday 1/8/2013 is negatively impacting the Failover Cluster Manager snap-in.

    We are actively investigating, and we will post more information as it becomes available.  The only known workaround at this time is to uninstall the hotfix.  We are recommending you do not deploy hotfix KB2750149 on Windows Server 2012 Failover Clusters until a solution is available.

    We apologize for the inconvenience, more information to come.

    Thanks!!
    Elden Christensen
    Principal Program Manager Lead
    Windows Server Clustering Group

    Thursday, January 10, 2013 12:01 AM
  • Just saw that KB2803748 showed up on my Server 2012 cluster nodes for installation

    Installed the update (no restart needed) and Cluster Manager no longer fails.

    Update for Windows Server 2012 (KB2803748)
    Installation date: ‎1/‎22/‎2013 1:31 PM
    Installation status: Succeeded
    Update type: Important
    Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.
    More information: 

    http://support.microsoft.com/kb/2803748

    Tuesday, January 22, 2013 6:39 PM
  • I can confirm KB2803748 has appeared on WSUS and fixes the issue. No reboot needed which is a bonus.

    Tim

    • Marked as answer by Yan Li_ Friday, February 1, 2013 1:44 AM
    Thursday, January 24, 2013 9:49 AM
  • I can confirm KB2803748 has appeared on WSUS and fixes the issue. No reboot needed which is a bonus

    Can confirm too. But no reboot is needed only if no users logged-on with Failover Clustering snap-in loaded.
    • Marked as answer by Yan Li_ Friday, February 1, 2013 1:44 AM
    Thursday, January 24, 2013 10:00 AM

All replies

  • I experienced the same issue today as well.
    Wednesday, January 9, 2013 8:52 PM
  • Same exact issue here.  Wasn't sure what broke it until I found this post.
    Wednesday, January 9, 2013 8:53 PM
  • exact same issue here

    Freundliche Grüsse Tobias Schiessl

    Wednesday, January 9, 2013 9:15 PM
  • Same issue here as well.
    Wednesday, January 9, 2013 9:23 PM
  • same issue
    Wednesday, January 9, 2013 9:31 PM
  • this article was very helpful, was just about to start tinkering with powershell cluster commands to figure out what was going on...just saved my sharepoint database
    Wednesday, January 9, 2013 11:58 PM
  • Thank you for the post, we are aware that the hotfix KB2750149 http://support.microsoft.com/kb/2750149 which was just released yesterday 1/8/2013 is negatively impacting the Failover Cluster Manager snap-in.

    We are actively investigating, and we will post more information as it becomes available.  The only known workaround at this time is to uninstall the hotfix.  We are recommending you do not deploy hotfix KB2750149 on Windows Server 2012 Failover Clusters until a solution is available.

    We apologize for the inconvenience, more information to come.

    Thanks!!
    Elden Christensen
    Principal Program Manager Lead
    Windows Server Clustering Group

    Thursday, January 10, 2013 12:01 AM
  • Thanks, waiting for your update. 
    Thursday, January 10, 2013 9:59 AM
  • Same issue after Cluster Aware Updating ran on my cluster.
    However issue appears when clicking roles.

    Have uninstalled KB2750149 waiting for new update.


    Friday, January 11, 2013 3:34 AM
  • exact same issue here. please fix it asap
    Friday, January 11, 2013 9:26 AM
  • same issue

    Thanks!

    Saturday, January 12, 2013 7:22 PM
  • thank you very much - helped us right at the moment, configuring our new cluster!
    Monday, January 14, 2013 9:19 PM
  • Same issue. Just built a new cluster, the nodes already had this patch installed before being clustered. Failover Cluster Manager crashing as described. Removed patch from both node and it’s stable. RDP is still working.

    Wednesday, January 16, 2013 8:43 AM
  • same issue with me!! still waiting..

    Thanks for the update 


    Saqib Ahmed

    Wednesday, January 16, 2013 9:50 AM
  • Just saw that KB2803748 showed up on my Server 2012 cluster nodes for installation

    Installed the update (no restart needed) and Cluster Manager no longer fails.

    Update for Windows Server 2012 (KB2803748)
    Installation date: ‎1/‎22/‎2013 1:31 PM
    Installation status: Succeeded
    Update type: Important
    Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.
    More information: 

    http://support.microsoft.com/kb/2803748

    Tuesday, January 22, 2013 6:39 PM
  • I can confirm KB2803748 has appeared on WSUS and fixes the issue. No reboot needed which is a bonus.

    Tim

    • Marked as answer by Yan Li_ Friday, February 1, 2013 1:44 AM
    Thursday, January 24, 2013 9:49 AM
  • I can confirm KB2803748 has appeared on WSUS and fixes the issue. No reboot needed which is a bonus

    Can confirm too. But no reboot is needed only if no users logged-on with Failover Clustering snap-in loaded.
    • Marked as answer by Yan Li_ Friday, February 1, 2013 1:44 AM
    Thursday, January 24, 2013 10:00 AM
  • Just built a new cluster and i'm back to the same issue. Why is this patch even still available? Good job I knew the fix this time
    Friday, August 30, 2013 8:28 AM
  • Just built a new cluster and i'm back to the same issue. Why is this patch even still available? Good job I knew the fix this time

    just scan for newer updates, one of newer updates (don't remember the exact kb) fix this issue.

    Friday, August 30, 2013 10:07 AM
  • Thanks Elden

    I was facing the same problem on my both cluster node. infact whenever I select any cluster disk, I was getting same error message.

    I install this http://www.microsoft.com/en-us/download/details.aspx?id=36468 hotfix and fix the issue on both nodes.

    Thanks

    MAKHAN

    Friday, October 4, 2013 1:16 PM
  • Hi All,

    Reason: Installed Win2012 Updates on Cluster nodes with mentioned KB.

    KB2750149

    http://blogs.technet.com/b/askcore/archive/2013/01/14/error-in-failover-cluster-manager-after-install-of-kb2750149.aspx

    Workaround:Now, we have to Install mentioned one more update on Win 2012 cluster nodes

    KB2803748

    http://www.microsoft.com/en-us/download/details.aspx?id=36468


    Kirpal Singh


    Friday, January 3, 2014 7:47 AM