Share via


Unable to add cluster nodes - Cluster service did not reach teh running state. The Error code is 0x5b4.

Question

Thursday, December 4, 2014 10:50 AM

Hi , i am trying to add last node into existing cluster.  The validation passed with minor warning.

But i get error "Cluster service on node xxx did not reach the running state.  The error code is 0x5b4.  This operation returned because the timeout period expired.

Server windows 2012 R2.   I tried google online but can't find any workaround for this.

Please share your opinion.  tq

All replies (5)

Monday, December 8, 2014 9:25 PM ✅Answered

It appears to me that this is a network related issue. Can the cluster nodes resolve the new nodes FQDN? Also can the new cluster node resolve the cluster name and other nodes? When it does resolve does it appear to be communicating on the right IP address?

Maybe in the network settings of the new node press the ALT key and move the management network adapter to the top of the list and press Ok. Then retry adding it to the cluster.


Tuesday, December 9, 2014 6:36 AM ✅Answered

Hi RaymondHS,

Please refer the following related KB to confirm your network settings meet the cluster requirement,

Cluster Networking Best Practices

http://technet.microsoft.com/pt-pt/library/cc779429(v=ws.10).aspx

I’m glad to be of help to you!

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.


Friday, December 5, 2014 4:48 PM

Do you have a domain controller and is it running, prior to 2012 you need to have a accessible domain controller running to start the cluster service. So if all your DCs are in the cluster it will not actually start. this is not the case anymore but was in 2008 r2.

If you have to you can create a new VM with the DC's vhd and start it outside the cluster.


Friday, December 5, 2014 4:57 PM

If you look at the system logs do you get any more granular detail for the error? To me it sounds like the network possibly is timing out when its trying to join the cluster. Are your network adapters setup similar to the other nodes in the existing cluster? It also sounds like the actual failover cluster service on the cluster doesn't want to start. That is why I would verify the windows system event log.

You could also go into Event Viewer > Custom Views> Administrative Events and look for all errors and see if you see anything that can give you more detail.


Monday, December 8, 2014 8:04 AM

well, the host is same configuration as all existing nodes.   

The system event just generic error event 1172 - Cluster Agent:  The cluster service on xxx has failed.