Closed jonathaneckman closed 6 years ago
Disregard. I figured this out but will leave the answer here for others.
My Cluster name was too long. The CNO of SqlFailoverCluster
was SQLFAILOVERCLUS
. This caused the error because SqlFailoverCluster was not found in the domain, but the machine was already joined to the SQLFAILOVERCLUS cluster.
@jonathaneckman Great that you solved it. It's NetBIOS limitation, for another reference see here https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/create-or-configure-an-availability-group-listener-sql-server?view=sql-server-2017#DNSnameReqs
Closing this as this was resolved by the contributor.
I am trying to create a new cluster on the first node. The node is an Azure VM. The first time the following is run, it works.
The second time, it fails with
I use a DSC pull server so this runs every 15 mins. Are my parameters incorrect?