Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2005 Cluster - Removing / Rebuilding / Adding Node Expand / Collapse
Author
Message
Posted Sunday, November 18, 2012 6:49 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 5:26 PM
Points: 219, Visits: 1,156
We have a two node SQL Server 2005 SP2 cluster, Running Windows Server 2003 SP1. My company implemented a new EMC SAN which required for all the servers running 2003 server SP1 being upgraded to SP2. Today, while upgrade ONE of our clusters to SP2, the boot-up got stuck on the Windows splash screeen. The server folks attempted to uninstall, but the server remained unhappy. To make a long story short the server was rebuilt. It was rebuilt using the hostname as before and successfully upgraded to SP2, while the primary node is up and owning all the clustered resources. When the server was handed over to me, I RDP'd into the primary and attempted to add SQL Instances onto new node. All was going well until I bumped into an issue when it attempts to validate the Service accounts "A domain group is missing for one or more services. To Install SQL Server 2005 as a Failover Cluster, domain groups must be specified for all the clustered services being installed. To proceed, enter the missing domain group information. The domain group cannot be validated for the server SQL Server." The account I am using is a domain admin account and is a member of multiple groups. Further, this account is used on ALL of our Production clusters. Could the problem be an issue with the SID? Something embedded in the registry of the primary node because we are using the same hostname? When the built the node they installed SP2, while the primary is still on SP1? Any help is much appreciated. I am at a loss.
Post #1386123
Posted Sunday, November 18, 2012 8:25 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, August 17, 2014 7:48 PM
Points: 102, Visits: 741
A couple of quick questions.

1. Is the account you are logged in as a local admin on both of the cluster nodes?
2. It has been a while since I have dealt with the death of a cluster node. I would go through the SQL Server install and remove, presuming it is still there, the node that died from the Cluster Node Configuration. Then reinstall. Directions for removing the node can be found here. http://msdn.microsoft.com/en-us/library/ms191545(v=sql.90).aspx

Hope this helps.
Post #1386136
Posted Monday, November 19, 2012 5:15 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 5:26 PM
Points: 219, Visits: 1,156
Those were the exact steps I followed. Hopefully today is a better day....txtPost_CommentEmoticon('');
Post #1386310
Posted Monday, November 19, 2012 5:48 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 5:26 PM
Points: 219, Visits: 1,156
This was fixed today. It was due to a missing Security Group in Active Directory.
Post #1386646
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse