Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
fssherwani
Starting Member
2 Posts |
 Posted - 2006-03-07 : 09:35:01
|
| Hi Gurus:We are running SQL Failover clustering on 2 node windows 2003 cluster environment. I have one default and one named SQL instance.The SQL Service for default instance have failed couple of times. There is no solid clue in the eventlog why the service fails , there is enough disk space ,RAM is good and so is CPU.Desperately need help , what should be my troubleshooting steps ?RegardsFahad |
|
|
propanecan
Yak Posting Veteran
60 Posts |
Posted - 2006-03-08 : 09:28:21
|
| Are you runing this in active/passive or active/active mode? Does the default instance fail on both nodes or just one of the nodes? |
 |
|
|
fssherwani
Starting Member
2 Posts |
Posted - 2006-03-08 : 09:34:38
|
| Thanks for your reply , this is active/passive cluster.Both instances can failover to either node.There is a difference in SQL patch , first node is patched with SQL SP3 and the second node (where the failure occured) have SQL SP1. This might potential cause , but the environment ran without error for couple of months and suddenly it failed.Is there any document which talks about troubleshooting "SQLServer.exe" related issues. |
|
|
|
propanecan
Yak Posting Veteran
60 Posts |
Posted - 2006-03-08 : 09:45:20
|
I believe it's possible that your instance could run without error until the service is restarted or fails over. As a rule always run both nodes at the exact patch level. Especially given the vulnerabilities of earlier patch levels I would suggest patching to at least sp3a on both nodes.As far as troubleshooting...it sounds like you were on the right track by reviewing the event viewer, etc. As a rule with clustered environments I would always start by comparing the applications/configurations of each node.  |
|
|
|
|
|
|
Urgent Help , SQL Service stops unexpectedly