An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...

Ronald Medina 11 Reputation points
2021-05-20T21:20:43.67+00:00

Hi,

I'm trying to deploy a Cluster with two nodes (WServer 2019 both / Domain Joined / Fresh Install) but it fails. Attach the creation's report:


Beginning to configure the cluster CLUSTERNAME.

Initializing Cluster CLUSTERNAME.

Validating cluster state on node NODE01.TEST.AR.

Searching the domain for computer object 'CLUSTERNAME'.

Find a suitable domain controller for node NODE01.TEST.AR. The specified server cannot perform the requested operation.

Operation failed, attempting cleanup.

An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...

An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...

There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes.

There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes.

An error occurred while creating the cluster.
An error occurred creating cluster 'CLUSTERNAME'.

The specified server cannot perform the requested operation

To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.


I tried the prestage process but it fails as well.
I'm carrying out this deployment using Administrator account which is Domain Admin.

Could anyone please help?

Kind regards.

Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
941 questions
{count} votes

7 answers

Sort by: Most helpful
  1. Marc Lefebvre 6 Reputation points
    2022-10-24T12:15:20.883+00:00

    I ran into this exact issue, and could find no documentation about it - it turned out to be the servers being added to the cluster couldn't reach the global catalog. This must be a change in later versions of Windows. Opening up ports 3268,3269 fixed the issue. Hope this helps someone in the future!

    1 person found this answer helpful.

  2. Yuhan Deng 3,756 Reputation points Microsoft Vendor
    2021-05-21T02:29:20.957+00:00

    Hi,
    This is a priviledge issue with windows server which prevents you from creating a cluster. to solve the problem, try the following steps:

    1. Manually create CNO (Cluster Name Object) in Active Directory;
      For your reference:
      https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731002(v=ws.10)?redirectedfrom=MSDN
    2. Ensure that CNO$ account has Full Control on the CNO and The computers container;
    3. Add CNO$ account (CNO computer object) in Local Admins group;
    4. Finally, add CNO$ in Domain Admins group.

    If the problems remains after these, please check the event logs and see if there’s any specific log relevant to this issue.

    Thanks for your time.
    Best regards,
    Danny

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. Ronald Medina 11 Reputation points
    2021-05-21T20:43:14.203+00:00

    Hi Yuhan,
    Thank you for your quick response.

    I tried to carry out the process that you indicated but it's still failing.

    Attach details about the errors into Event Viewer:

    Log Name: System
    Source: Failover-Clustering-Client
    Event ID: 81
    Level: Error


    LogExtendedErrorInformation (974): Extended RPC error information:
    ProcessID is 7076
    System time is: 8683/471/16294 0:0:46624:8611
    Generating component is 2
    Status is 1753
    Detection location is 501
    Flags is 0
    NumberOfParameters is 4
    Unicode string: ncacn_ip_tcp
    Unicode string: NODE01.TEST.AR
    Long val: -1182943054
    Long val: 382312662


    There's another identical error, but the only thing that changes is the 'Unicode string' parameter: NODE02.TEST.AR

    Thanks in advance.

    0 comments No comments

  4. Yuhan Deng 3,756 Reputation points Microsoft Vendor
    2021-05-24T01:49:54.663+00:00

    Hi,
    I don’t see any problem according to the logs.
    Would you run a validation report again and see if there’s anything missing?
    For your reference:
    https://learn.microsoft.com/en-us/windows-server/failover-clustering/create-failover-cluster

    Thanks for your time.
    Best regards,
    Danny

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  5. Ronald Medina 11 Reputation points
    2021-05-27T20:47:40.767+00:00

    Hi Danny,

    I've run the validation again and only the following warnings show up:

    Node NODE02.TEST.AR is reachable from Node NODE01.TEST.AR by only one pair of network interfaces. It is possible that this network path is a single point of failure for communication within the cluster. Please verify that this single path is highly available, or consider adding additional networks to the cluster.
    Node NODE01.TEST.AR is reachable from Node NODE02.TEST.AR by only one pair of network interfaces. It is possible that this network path is a single point of failure for communication within the cluster. Please verify that this single path is highly available, or consider adding additional networks to the cluster.

    The cluster validation test has detected that all nodes do not have the same software updates. We recommend that all nodes run the same version of the operating system, and install the same software updates. If you have verified that all nodes are consistent, you can ignore this warning.

    Even though they're only warnings, can this affect?

    Regards.