Unable to create new Failover Cluster

Question

I'm trying to create a new 3 node Windows Failover Cluster on Server 2022 Datacenter and I'm having trouble getting it to actually create. When running the cluster creation wizard, all steps go through fine and validation passes without error. Once it starts processing, it gets to the part about binding to a domain controller and then spits out the following error:

Check whether the computer object <object> for node <node> exists in the domain. Domain controller <domain-controller>. More data is available.

Some troubleshooting steps I've taken to test this:

• Verified the account I'm using to create the cluster is an administrator on all nodes as well as a domain/enterprise admin in AD
• Verified the computer objects do indeed exist in AD
• Tried different OUs in AD to rule out OU perms
• Tried both Windows Server 2019 and 2022 with the same results
• Tried pre-configuring the AD objects for the cluster, same results
• Tried both single-node and multi-node configurations, both fail
• Verified the cluster nodes have proper connectivity to the domain controllers and proper ports are open on the DCs
• Verified DNS records exist and global catalogs are reachable
• Tried creating via PowerShell with the same error
• Verified I can do an nslookup for the CNO on all nodes successfully
• Dcdiag completes successfully on all domain controllers
• All nodes are joined to the domain

One thing I tried is to create a DNS-only cluster and while that does work, it still doesn't solve the issue as I need to have an AD-integrated cluster for this. Only other relevant error I'm seeing in the FailoverClustering-Manager>Diagnostic event log (event ID 4614) is below.

Creating the cluster failed - System.ApplicationException: An error occurred creating cluster '<cluster>'. ---> System.ComponentModel.Win32Exception: More data is available
--- End of inner exception stack trace ---
at MS.Internal.ServerClusters.Cluster.Create(String clusterName, StringCollection nodeNames, ICollection1 ipAddresses, ClusterActionCallback callback, AdminAccessPoint managementAccessPoint, AdminAccessPointResType CNOResType)
at MS.Internal.ServerClusters.Configuration.CreateClusterConfigurationNoCno.PerformCreateCluster(ActionArgs actionArgs, ActionUpdateHelper updateHelper)
at MS.Internal.ServerClusters.Configuration.CreateClusterConfigurationNoCno.PerformAction(ActionArgs actionArgs)
at MS.Internal.ServerClusters.Configuration.CreateClusterConfigurationNoCno.InternalPerformAction(ActionArgs actionArgs)

I don't really know what else to try and I'm at a loss. We have other clusters that are operational that were likely created prior to 2012 R2. My domain controllers are on Server 2016 with a 2016 functional level. I've searched up articles and while some mentioned similar issues, none actually resolved it. Any help is appreciated.

Answer 1

Hi Jason,

Hope you're doing well.

The following documents may help you:

How to Troubleshoot Create Cluster Failures - Microsoft Community Hub

If you have any other questions, please let me know.

Best Regards