I’ve been running Windows Server 2012 Failover Cluster for about a year and it’s been stable up until now. Recently, I encountered an issue where Live migration of VMs failed across all hosts in the cluster. In addition, the Failover Cluster Manager started displaying the following error:
Cluster network name resource ‘Cluster Name’ failed registration of one or more associated DNS name(s) for the following reason:
The handle is invalid. Select your cluster name on the top left pane of the Failover Cluster Manager.
The error was obviously related to DNS in some way. I still couldn’t figure out the cause though. After digging around for a while, I came up with the following steps that have so far helped me resolve the problem.
Open the Failover Cluster Manager Console.
In the center panel, go down to “Cluster Core Resources”.
Right-click your Cluster name and select the “More actions” drop down option.
I selected the “Simulate Failure” option.
After the Cluster Object goes offline, right-click the Cluster Name again, “More actions” and select “Repair”.
Still the DNS status was still “Invalid” .
For a second time, I went ahead and did a right-click on the Cluster name object again.
This time I selected the “Take Offline” option.
After the Cluster Object went offline, I did a right-click on the Cluster Name, “More actions” and selected the “Repair” option.
This time, the DNS status changed to “OK” after the Cluster name “Repair” action.
So far, these steps seem to resolve the error without disrupting any Virtual Machine operations. I plan to upgrade to WS 2012 R2 and hopefully will not have to deal with this. Hopefully, these steps help spare someone a lot of headache :).
you rock.
thank you very much
excellent, above steps helped me to fix the issue
I’m glad the post was of some help to you. Thank you for the comment.
Awesome, quick and easy fix. Thanks.
Found this that may explain it better:
https://blogs.msdn.microsoft.com/clustering/2013/12/13/understanding-the-repair-active-directory-object-recovery-action/
I had similar issue with SCALE out File Server , the issues was that when i added the network share name \\ , the cluster object did not have the permission to create computer object,
I just briefly added the cluster name to domain admin group allowed the object to be created and everythign was all Good