We help IT Professionals succeed at work.

Microsoft SQL Server 2005 Enterprise Cluster Failover Fails

I have created a Microsoft SQL Server 2005 Enterprise Cluster.  All Microsoft Cluster Service resources failover except resources used by SQL to include the server, disks, etc.  I need a resolution to this issue ASAP and I'd like to understand what could be causing this issue.

Thank you,

glbt
Comment
Watch Question

Paul MacDonaldDirector, Information Systems

Commented:
Looking at the property of the resources in question, are all nodes in the Possible Owners list?

Author

Commented:
Yes, both nodes are listed.

It seems that there is a broader issue.  Actually, when the team was attempting to add the second node to the SQL cluster, the install errored and failed. So, that could explain why the other cluster resources failover properly and not the SQL resources do not.

So, actually, I looking for how to add a second node to the SQL 2005 cluster. We have following the documented Microsoft steps without any success.
Paul MacDonaldDirector, Information Systems

Commented:
Okay.  There is a process specific to adding an additional node to an SQL cluster.  The SQL setup should offer that as a choice.

Author

Commented:
Thanks for working with me.  That is the problem.  The SQL setup is not offering, if you will, the expected choice for adding an additional node.
Commented:
The cause of this was related the security settings.  This is on a government network with stringent security requirements.  The fix was to ensure that user account used during setup was in the local security policy.  Unfornately, since it has been a long while now and I have been on several projects since that time, I do not recall which policy.

Author

Commented:
I am grading myself a B since I took so long to update this and could not recall the specific fix.