SQL Server Fails to Start When Moved to Different Node
Failover Clustering, Failover Clustering nodes, SQL Server, SQL Server 2008, SQL Server 2008 R2, SQL Server clustering, Windows Server 2008 R2
Sql 2008 R2 on Windows 2008 R2 cluster. When I move instance from node 1 to node 2 everything is fine: all resources come online as they should. When I move the instance from node 2 to node 1, all resources except sql server and agent come online. If I delete errorlog and start the sql server service, sql server and agent startup without problems. Also, I can offline the server on node 2, move it to node 1, and try and start it but it fails unless I delete the errorlog first. I checked startup parameters and servers are identical. I also have a second instance on the same cluster and it moves back and forth between nodes without incident.
Software/Hardware used:
Software/Hardware used:
ASKED:
April 7, 2011 5:24 PM
UPDATED:
April 11, 2011 7:47 PM
RELATED QUESTIONS
- cluster install node failure when adding
- Windows Server Cluster 2003 or 2008
- Can I add a local SQL 2005 instance to a clustered node
- SSIS 2008 R2 performance and Windows Server 2008 R2 with a clustered SQL instance is slower than when connecting to a non-clustered instance?
- Hyper-V Host Not Responding in SCVMM R2
Answer Wiki:
Please provide us the cluster logs to investigate.
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
