none
Failover Clustering Fails to Start

    Question

  • Good day all,

    Hopefully someone can assist. Ive been running around in circles. 

    We had a 2 Node cluster configured, then the cluster was destroyed (not the correct way) the 2 servers were shutdown and formatted.  Now Im tyring to re-configure a 2 node Cluster again and am running into numerous issues. 

    Both servers have been rebuilt with Server 2008 Enterprise SP2. - Identical Servers as well as connected to a SAN for Disk Quorum.

    Clustering Services were installed successfully on both Nodes and Validation comes back 100% on both Nodes. however when tyring to start the cluster Service it fails with Event ID: 7024 and 1090.

    Event ID 7024: Service Specific Error 2
    Event ID: 1090: Cluster Service cannot be started on this node because a registry operation failed with error '2'

    The user account has admin rights on the computer and network domain.
    Ive tried uninstalling the Failover Clustering services.
    Even when setting the service to Automatic then trying to create the cluster - it says the computer is already part of a cluster.
    Wednesday, February 03, 2010 4:40 PM

Answers

  • Thanks for the replies everyone but I managed resolve the issue.  There's a Kbase article for the resolution

    http://support.microsoft.com/kb/973838

    So if anyone runs into removing a Cluster from your network without the method of using the Destroy command from DOS. Just ensure that you remove all pointers in your Active Directory and DNS records that were pointing to that cluster. 

    Also, the Clustering Services in Server 2008 require 3 dependencies in order to startup correctly: 

    Cluster Virtual Miniport Driver - Which was failing in my case
    RPC server 
    and 
    SRV

     
    Wednesday, February 03, 2010 10:20 PM

All replies

  • Not sure this is the answer, but did you delete the computer objects from the domain before rebuilding the cluster?  I have always been sure delete the physical and virtual computer names from AD when rebuilding clusters with the same name, because i know some SPNs are stored in these objects that the cluster will/should recreate.
    Wednesday, February 03, 2010 5:11 PM
  • Hey Gunner999

           Thanks for the reply,

       I went into AD and DNS and just deleted any instances of the old Virtual server names and physical nodes computer names (basically any records pointing to the old cluster).  Also another item I tried which seemed to get me closer was I renamed the Cluster name as well as the physical node names, it allows me to go through the creation but then times out at the step Forming the cluster.. and there no error message in the event viewer or anything.  
    Wednesday, February 03, 2010 8:00 PM
  • Thanks for the replies everyone but I managed resolve the issue.  There's a Kbase article for the resolution

    http://support.microsoft.com/kb/973838

    So if anyone runs into removing a Cluster from your network without the method of using the Destroy command from DOS. Just ensure that you remove all pointers in your Active Directory and DNS records that were pointing to that cluster. 

    Also, the Clustering Services in Server 2008 require 3 dependencies in order to startup correctly: 

    Cluster Virtual Miniport Driver - Which was failing in my case
    RPC server 
    and 
    SRV

     
    Wednesday, February 03, 2010 10:20 PM