October 13, 2008 at 10:46 am
OS: Server 2003 x64
MEM: 32GB
SQL: 2005, SP2
MSCS, failover cluster
During the installation of SQL Server on a failover cluster, the second node did not install the database engine/services for some reason. Now, if the cluster was to failover, SQL Server will not start because the Cluster Resource Group will not failover to that node. After investigation, the SQL Server Resource within the cluster does not see the second node as a possible owner. When I attempt to add it as a possible owner, it does not see it. Further, when I look at the services on the second node, SQL Server (MSSQLSERVER) is not a listed service. Analysis Services, Reporting Services, Integration Services are all there; just not SQL Services.
What would be the best approach to correcting this failed install on this node? :w00t:
October 13, 2008 at 12:23 pm
- Check the installation log files for the reasons why it did no install on the second node !
Only then you can fix it.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data and code to get the best help
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Who am I ? Sometimes this is me but most of the time this is me
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply