none
Creating a new Cluster failed with "An error occurred while creating the cluster and the nodes will be cleaned up" RRS feed

  • Question

  • Hi,

    We have 2 Windows server 2012 Datacenter edition with 4 NIC, I am trying to configure windows cluster and validation test passed successfully.

    the 2 servers are connected to storage with fiber. during the creation of cluster i got the following error:

    Unable to successfully 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 'HyperV3Cluster'.

    The parameter is incorrect

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

    • Changed type cloudex14 Tuesday, October 1, 2013 12:05 PM
    Tuesday, May 21, 2013 10:22 AM

Answers

  • Hi,

    This is a priviledge issue with windows server 2012 which preventing from creating a cluster. to solve the problem do the following:

    1. Manually create CNO (Cluster Name Object) in Active Directory.

    http://technet.microsoft.com/en-us/library/cc731002%28d=printer,v=ws.10%29.aspx

    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.  

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. My blog:http://msibrahim.wordpress.com/

    • Marked as answer by cloudex14 Wednesday, October 2, 2013 7:19 AM
    Tuesday, October 1, 2013 12:00 PM

All replies

  • Hi,

    Have you tried the Clear-ClusterNode command to manually clean up the cluster, maybe there is some installation error and system try to clean up the installation, but can’t finish clean up.

    And if possible, reinstall the OS and then re-try to create the cluster.

    For more information please refer to following MS articles:

    Clear-ClusterNode
    http://technet.microsoft.com/en-us/library/ee460996.aspx
    How to clean up the cluster resource group and the databases on a shared disk after a failed failover Cluster Complete operation in SQL Server 2008
    http://support.microsoft.com/kb/953505


    Lawrence

    TechNet Community Support

    Wednesday, May 22, 2013 6:35 AM
    Moderator
  • I did clear for both nodes but still same error, that was a fresh installation. do i have to reinstall OS ? is there any other option ?
    Wednesday, May 22, 2013 9:54 AM
  • Hi,

    Still the same problem after reinstall the OS.

    Sunday, May 26, 2013 1:22 PM
  • You included everything, but the important parts...   the log statements you have above are the attempts to clean-up, after the failure.  But they don't include the logging of the failure... that's what we really need.  So scroll up a few lines and focus on the failure.

    See this blog for troubleshooting steps:
    http://blogs.msdn.com/b/clustering/archive/2012/05/07/10301709.aspx

    Thanks!
    Elden

    Sunday, May 26, 2013 3:30 PM
    Owner
  • Hi,

    I found the following errors:

    ConnectCluster (999): Failed to open remote cluster status 'node name' == 1753.

    ConnectRemoteCluster (856): Couldn't resolve RPC binding to cluster 'node name', Status = 1753

    OpenClusterImpl (1119): Could not connect to cluster.  sc = 1753

    Monday, May 27, 2013 8:48 AM
  • Was there ever a solution to this??
    Monday, August 26, 2013 3:32 PM
  • I have the same Issue . Did you resolve it ?

    Daoud Ghannam

    Wednesday, August 28, 2013 10:58 AM
  • Having the same Error, did you resolve it ?

    Daoud Ghannam

    Wednesday, August 28, 2013 10:58 AM
  • I ll just stick with VMware

    Wednesday, September 25, 2013 8:16 PM
  • any one knw how to solve it ?
    Tuesday, October 1, 2013 8:54 AM
  • Hi,

    This is a priviledge issue with windows server 2012 which preventing from creating a cluster. to solve the problem do the following:

    1. Manually create CNO (Cluster Name Object) in Active Directory.

    http://technet.microsoft.com/en-us/library/cc731002%28d=printer,v=ws.10%29.aspx

    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.  

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. My blog:http://msibrahim.wordpress.com/

    • Marked as answer by cloudex14 Wednesday, October 2, 2013 7:19 AM
    Tuesday, October 1, 2013 12:00 PM
  • amazing, the problem is solved. Thanks mohamed for ur help.
    Wednesday, October 2, 2013 7:20 AM
  • Communication between nodes and DC may be blocked. Check port TCP & UDP port 464 (Kerberos Change/Set password) is open. This may be one of the root cause for this issue.


    Syed

    Thursday, January 15, 2015 9:20 AM
  • Re-install the OS?  That's a pretty drastic suggestion for a error at the final phases of the install. That's like saying if you have a flat tire on your car, get a new car.
    Tuesday, April 5, 2016 5:29 PM
  • Another useless suggestion; I have experienced this same error and the original post includes all of the information the wizard provides.
    Tuesday, April 5, 2016 5:30 PM
  • If the business requirement is MSCS for MS SQL, how are you doing that with only VMware LOL. You still need the OS.
    Tuesday, April 5, 2016 5:38 PM
  • In addition to the suggestions regarding required ports between MSCS and the AD Domain, and the suggestion regarding manual creation also keep in mind that MSCS is very sensitive to correct time. The time on the nodes needs to match the AD time on the DC, or it will fail with this exact error as well.

    Jonathan

    Tuesday, April 5, 2016 8:27 PM
  • Hes saying that he is going to stick to VMware for failover and replication. I would too, because its much easier to configure, but I have a stubborn software that wont run in a virtualized environment.
    Friday, August 19, 2016 1:38 PM
  • Check the dns 'A' record created or not in DNS Server of cluster name.  Also make sure which users you are using those have domain admin rights or not?

    Saturday, May 27, 2017 4:25 AM