0

I have a Windows failover cluster up and running, with two nodes.

I'm now trying to add a third node:

Add-ClusterNode -Name node3

this unfortunately fails with the following error:

The clustered role was not successfully created. Add-ClusterNode : An error occured while performing the operation. This operation returned because the timeout period expired.

The server node3 is joined to the domain like the other two instances, and all instances can talk to each other.

What could be causing this? I'm working with Windows server 2019 on EC2 (AWS)

I'm also seeing this error message when adding the node via cluster manager:

* Cluster service on node node3 did not reach the running state. The error code is 0x5ba

Improve this question
4
  • I'm sure there's a log somewhere that might have helpful information.
    – mustaccio
    Aug 16, 2022 at 17:42
  • @mustaccio which one? I've not seen any helpful message in the cluster logs
    – Foo
    Aug 16, 2022 at 17:51
  • Windows Event Log and SQL Server Log are places you can check. Also, did you verify it's not a firewall issue?...can you ping the third node?
    – J.D.
    Aug 17, 2022 at 2:17
  • @J.D. yes, like I said all servers can talk to each other
    – Foo
    Aug 17, 2022 at 8:06

1 Answer 1

Reset to default
0

This was due to a DNS issue on the node.

I had to run this for it to work:

Set-DnsClientGlobalSetting -SuffixSearchList @("")
Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.