KB2750149 breaks Windows 2012 Failover Cluster Manager
-
Wednesday, January 09, 2013 8:05 PM
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 09, 2013 8:55 PM
All Replies
-
Wednesday, January 09, 2013 8:52 PMI experienced the same issue today as well.
-
Wednesday, January 09, 2013 8:53 PMSame exact issue here. Wasn't sure what broke it until I found this post.
-
Wednesday, January 09, 2013 9:15 PMexact same issue here
Freundliche Grüsse Tobias Schiessl
-
Wednesday, January 09, 2013 9:23 PMSame issue here as well.
-
Wednesday, January 09, 2013 9:31 PMsame issue
-
Wednesday, January 09, 2013 11:58 PMthis 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
-
Thursday, January 10, 2013 12:01 AM
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- Proposed As Answer by Subhasish Bhattacharya Thursday, January 10, 2013 12:12 AM
- Unproposed As Answer by Ginno2k9 Thursday, January 10, 2013 3:46 PM
- Marked As Answer by Shaon ShanMicrosoft Contingent Staff, Moderator Friday, February 01, 2013 5:17 AM
-
Thursday, January 10, 2013 9:59 AMThanks, waiting for your update.
-
Friday, January 11, 2013 3:34 AM
Same issue after Cluster Aware Updating ran on my cluster.
However issue appears when clicking roles.Have uninstalled KB2750149 waiting for new update.
- Edited by Robert Williames Friday, January 11, 2013 3:35 AM
-
Friday, January 11, 2013 9:26 AMexact same issue here. please fix it asap
-
Saturday, January 12, 2013 7:22 PM
same issue
Thanks!
-
Monday, January 14, 2013 9:19 PMthank you very much - helped us right at the moment, configuring our new cluster!
-
Wednesday, January 16, 2013 8:43 AM
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 9:50 AM
same issue with me!! still waiting..
Thanks for the update
Saqib Ahmed
-
Tuesday, January 22, 2013 6:39 PM
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
- Proposed As Answer by TimBoothby Thursday, January 24, 2013 9:48 AM
- Marked As Answer by Shaon ShanMicrosoft Contingent Staff, Moderator Friday, February 01, 2013 5:17 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.
Tim
- Marked As Answer by Yan Li_Microsoft Contingent Staff, Moderator Friday, February 01, 2013 1:44 AM
-
Thursday, January 24, 2013 10:00 AM
Can confirm too. But no reboot is needed only if no users logged-on with Failover Clustering snap-in loaded.I can confirm KB2803748 has appeared on WSUS and fixes the issue. No reboot needed which is a bonus
- Marked As Answer by Yan Li_Microsoft Contingent Staff, Moderator Friday, February 01, 2013 1:44 AM

