Urgent Help. SQL Server Service stops unexpectdly
-
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 ?
Regards
Fahad
-
http://msdn2.microsoft.com/en-us/library/ms189117.aspx
May be this helps.......
-
Hi Shir.
Take a look at this documentation.
http://www.sql-server-performance.com/sqlserver2000_clustering_install_main.asp
Regards.
-
Does the SQL Server errorlog show a normal shutdown request or not ?
Have you examined the "cluster.log" file ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
-
SQL Server Error Log doesnot record a shutdown request. I have scanned all the sql logs ,since the time error occured , but no clues.
The cluster.log file does report that sql service is offline , but there are no errors /warnings prior to the sql service shutdown event.
The system Log records the event
"SQL server service was terminated unexpectedly"
The immediate event is reported by "ClusSvc" which says
"Cluster resource 'SQL Server' in Resource Group " , which i understand is immediate consequence of what happened earlier.
What could be my possible next step ?
-
If the event logs have nothing and the SQL Server errorlog does not have a "sghutdown" line and the cluster.log file looks OK (be wary the cluster.log file is only valid for a few hours .. it constantly rolls). I'sd then look for a SQL Server "dump" file. Try looking for *.dmp first in the MSSQL\LOG directory then scan the entire drive where SQL Server is installed.
Oh, just thought to ask ... are you running SP1 on your WIn 2K3 cluster ? What SP are you on for SQL Server as well ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
-
Both nodes have WIN2K3 SP1 , there is a difference wrt SQL SP , one node have SP3 while other is running on SP1(the node where error occured). But this setup ran fine for almost 2 months without errors.
I am not quite finished looking through cluster.log file yet , but havent found any hint till now.
What i should be looking for in dump file ?
Regards
Fahad
-
What appeared to run fine was probably just a case of luck.
Apply SP3 immediately !
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
-
Hi Shir.
The strange thing is that you have two different service pack level in SQL server in your cluster environment. How did you execute the setup?
The service pack setup used to update all the nodes joined in the cluster.
Regards.
Diego
-
That was my perception as well , but i found out that both nodes are running at different SP level.
I started with a single node cluster and joined the second node aftwer wards, the newly added node lags the updated SQL SP.
What arethe recommended steps to install SP in cluster environment ?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply