This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 52%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hi,
I am in a weird situation with our Windows 2012 R2 three-node failover cluster. We have a current setup of a three-node failover cluster with file witness share. Two physical nodes died, and I had to evict both nodes from the cluster, but now when I am trying to add a new node back with Windows 2016 in the cluster, I am getting the below error.
Cluster failed to start. The latest copy of cluster configuration data was not available within the set of nodes attempting to start the cluster. Changes to the cluster occurred while the set of nodes were not in membership and as a result were not able to receive configuration data updates. .
Votes required to start cluster: 2
Votes available: 1
Nodes with votes: <new server> <old server>
Guidance:
Attempt to start the cluster service on all nodes in the cluster so that nodes with the latest copy of the cluster configuration data can first form the cluster. The cluster will be able to start and the nodes will automatically obtain the updated cluster configuration data. If there are no nodes available with the latest copy of the cluster configuration data, run the 'Start-ClusterNode -FQ' Windows PowerShell cmdlet. Using the ForceQuorum (FQ) parameter will start the cluster service and mark this node's copy of the cluster configuration data to be authoritative. Forcing quorum on a node with an outdated copy of the cluster database may result in cluster configuration changes that occurred while the node was not participating in the cluster to be lost.
I am not sure what to do here since the cluster is up and running with one remaining node and I do not want to risk it going down as it is running critical applications. Should I disable quorum witness altogether then join the new node and then enable it again? Will doing this affect the cluster in any way? Any help would be greatly appreciated!
Thanks in advance!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Hello
Thank you for your question and reaching out.
Reference:
--If the reply is helpful, please Upvote and Accept as answer--
Hi,
Thanks for your reply. I have checked all the configurations from the validation test, and nothing stands out of any networking issues. The new node trying to join the cluster can ping the cluster, the other node, DNS is ok. Not sure what the issue is. The issue in my circumstance is that I cannot join the node back to the cluster after the upgrade. Quick question, What if I disable the quorum to remove voting and then add it? Will that affect anything on the currently running node? Thank you.
Suppose anyone is looking for the answer to being unable to add a node to a cluster. Do this.
Instead of going around and trying to ask for help from everyone and trying different methods. Use the below command to generate the cluster log and check why it is causing the error. In my case, I tried everything and later found out that the cluster was terminating the connection from a disabled cluster network; upon enabling the network for cluster communication, everything worked flawlessly.
Get-ClusterLog -Destination C:\ –UseLocalTime
Here are the instructions from the article I found online:
Error when adding a node to a Hyper-V cluster: Waiting for notification that node is a fully functional member of the cluster - The error code is 0x5b4 - Unable to successfully cleanup
31.10.2014Author:[Alexey Maksimov](https://blog.it-kb.ru/author/blogroot/"Перейти на сайт Алексей Максимов")12 359 view4 Comments
A Windows Server 2012 R2-based Hyper-V cluster has been created with a single node and a disk witness. After that, we try to add a new node to the cluster. As a result, an error appears:
If you look at the View Report, you can see that the node is undergoing initial validation, and then the operation fails with a message about some kind of waiting timeout:
Adding KOM-AD01-VM07.holding.com to the cluster.
Validating cluster state on node KOM-AD01-VM07.
Getting current node membership of cluster KOM-AD01-VMFC01.
Adding node KOM-AD01-VM07 to Cluster configuration data.
Validating installation of the Network FT Driver on node KOM-AD01-VM07.
Validating installation of the Cluster Disk Driver on node KOM-AD01-VM07.
Configuring Cluster Service on node KOM-AD01-VM07.
Waiting for notification that Cluster service on node KOM-AD01-VM07.holding.com has started.
Waiting for notification that node KOM-AD01-VM07 is a fully functional member of the cluster.
Cluster service on node KOM-AD01-VM07 did not reach the running state. The error code is 0x5b4. For more information check the cluster log and the system event log from node KOM-AD01-VM07. This operation returned because the timeout period expired.
Unable to successfully cleanup.
The server 'KOM-AD01-VM07.holding.com' could not be added to the cluster.
An error occurred while adding node 'KOM-AD01-VM07.holding.com' to cluster 'KOM-AD01-VMFC01'.
This operation returned because the timeout period expired
To understand the root of the problem, additional debugging information is required, which will help you get the recommendations in the article Failover Clustering and Network Load Balancing Team Blog - How to Troubleshoot Create Cluster failures in Windows Server 2012. In particular, to get the log, the clustering components will be executed on both servers (on the current cluster node and the server being added to the cluster) Powershell cmdlet that uploads this log to a text file:
Get-ClusterLog
As a result, a log file with the name of the form KOM-AD01-VM04_cluster.log will appear along the specified path
In our particular example, the examination of the log on the server being added to the cluster did not bring clarity, however, in the log of the server owning the cluster, multiple warnings of the form were noticed:
00000ad8.00001dd4::2014/10/29-20:14:55.154 WARN mscs::ListenerWorker::operator (): (5060)' because of '[FTI][Initiator] Discarding connection from 10.160.35.58:~3343~ to 10.160.35.57:~3343~ (node KOM-AD01-VM07) because it uses a disabled network.'
As a result, it turned out that the subnet related to Live Migration that was turned off in the cluster was the cause of the problem.
After enabling the appropriate cluster network, the new node was successfully added to the cluster.
Error when adding a node to a Hyper-V cluster : Waiting for notification that node is a fully functional member of the cluster - The error code is 0x5b4 - Unable to successfully cleanup
31.10.2014Author:[Alexey Maksimov](https://blog.it-kb.ru/author/blogroot/"Перейти на сайт Алексей Максимов")12 359 view4 Comments
A Windows Server 2012 R2-based Hyper-V cluster has been created with a single node and a disk witness. After that, we try to add a new node to the cluster. As a result, an error appears:
If you look at the View Report, you can see that the node is undergoing initial validation, and then the operation fails with a message about some kind of waiting timeout:
Adding KOM-AD01-VM07.holding.com to the cluster.
Validating cluster state on node KOM-AD01-VM07.
Getting current node membership of cluster KOM-AD01-VMFC01.
Adding node KOM-AD01-VM07 to Cluster configuration data.
Validating installation of the Network FT Driver on node KOM-AD01-VM07.
Validating installation of the Cluster Disk Driver on node KOM-AD01-VM07.
Configuring Cluster Service on node KOM-AD01-VM07.
Waiting for notification that Cluster service on node KOM-AD01-VM07.holding.com has started.
Waiting for notification that node KOM-AD01-VM07 is a fully functional member of the cluster.
Cluster service on node KOM-AD01-VM07 did not reach the running state. The error code is 0x5b4. For more information check the cluster log and the system event log from node KOM-AD01-VM07. This operation returned because the timeout period expired.
Unable to successfully cleanup.
The server 'KOM-AD01-VM07.holding.com' could not be added to the cluster.
An error occurred while adding node 'KOM-AD01-VM07.holding.com' to cluster 'KOM-AD01-VMFC01'.
This operation returned because the timeout period expired
To understand the root of the problem, additional debugging information is required, which will help you get the recommendations in the article Failover Clustering and Network Load Balancing Team Blog - How to Troubleshoot Create Cluster failures in Windows Server 2012. In particular, to get the log, the clustering components will be executed on both servers (on the current cluster node and the server being added to the cluster) Powershell cmdlet that uploads this log to a text file:
Get-ClusterLog
As a result, a log file with the name of the form KOM-AD01-VM04_cluster.log will appear along the specified path
In our particular example, the examination of the log on the server being added to the cluster did not bring clarity, however, in the log of the server owning the cluster, multiple warnings of the form were noticed:
00000ad8.00001dd4::2014/10/29-20:14:55.154 WARN mscs::ListenerWorker::operator (): (5060)' because of '[FTI][Initiator] Discarding connection from 10.160.35.58:~3343~ to 10.160.35.57:~3343~ (node KOM-AD01-VM07) because it uses a disabled network.'
As a result, it turned out that the subnet related to Live Migration that was turned off in the cluster was the cause of the problem.
After enabling the appropriate cluster network, the new node was successfully added to the cluster.