Cannot create Cluster – the computer X is joined to a cluster

Recently attempting to install a new three node cluster I ran into a new issue. Once I was able to run a successful “Cluster Validation Check” and chose the option to install a new cluster I received a message “The computer xxx is joined to a cluster”.

select_servers

 

 

My first thought then was to remove clustering and try a fresh install of the feature.  That didn’t go to well either, I was informed that the node was an active node of a cluster that it in fact was NOT.

remove_clustering

I did a bit of research and found that I could clear this with using PowerShell. To do so I had to open PowerShell as an administrator and load the failoverclusters module. Then I could run the command clear-clusternode to forcefully clean up the cluster node.

PoSH

Once the node was cleaned up I was able to proceed with the cluster build.

 

Share
This entry was posted in PowerShell, SQLServerPedia Syndication, Tibits. Bookmark the permalink.

10 Responses to Cannot create Cluster – the computer X is joined to a cluster

  1. wbbeasley says:

    So do you know what triggered the original error. Were you going from a 2 node cluster to a 3 node cluster or something?

    • Tim Radney says:

      I haven’t been able to pinpoint the issue but I am leaning towards a GPO. Even after doing the fix, I didn’t create the cluster until the next day and the issue had come back. I had to run the PowerShell command again, built the cluster and so far so good. It has been a week.

  2. Don Schaefer says:

    Thank you! I was looking for the solution to this and your blog is the only thing that worked for me. Thanks again, Don

  3. Sudhir Giri says:

    Powershell worked well with me.

  4. Paul says:

    Thanks for this. Lots of other sites only give the remove-cluster command where you need to know the cluster name. I am sure there is a simple way round that however this cut to the chase and gave the solution

  5. Greg Smith says:

    Thank you, I was looking for a solution to this problem for many hours. Your solution took 5 seconds, much appreciated.
    -Greg

  6. Davi says:

    Very good

  7. Everton Araujo says:

    Thanks man… it´s simple.

  8. Gorakshnath says:

    Nice solution

  9. Sri says:

    Easy Solution.

Leave a Reply

Your email address will not be published. Required fields are marked *