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 |
ischana
Starting Member
1 Post |
Posted - 2008-10-16 : 06:24:22
|
Dear allMy sql server 2000 was running successfully in the evenning but on next morning sql serverwas not running..i checked from all sources..but no solution tried from service manager/EM and then from control-panel->services also changing log on option also but sql service didn't started .. sql service started and then stopped immediately ...In past also i had faced the same probleme Can Anyone suggest the sound solution..regardsIS |
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2008-10-16 : 08:16:28
|
Check the Event Viewer of the serverCheck the SQL Errorlog |
 |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-10-16 : 09:13:33
|
quote: Originally posted by YellowBug Check the Event Viewer of the serverCheck the SQL Errorlog
How can you check Error Log when SQL service is not starting? What error do you get while connecting? |
 |
|
SimpleSQL
Yak Posting Veteran
85 Posts |
Posted - 2008-10-16 : 22:21:39
|
How can you check Error Log when SQL service is not starting? What error do you get while connecting?Gien the OP's problem descriptionsql service started and then stopped immediately ...I think SQL might be starting, but maybe not all system databases are able to recover and hence failing, we would have SQL errorlog.ischana, please check following location fro SQL ErrorlogC:\program files\Microsoft sql server\mssql\log In this folder you should have by default 7 errorlogs, from errorlog, errolog.1 - errorlog.6Check the latest one, which is errorlog (with no extension).This should give you clue as to why SQL is not startingIf no errolog is getting created, then check Application event log, this should typically have erorr listed (maybe permission issue etc..)But given your SQL was runnign fine and it stopped all of a sudden, I would think it is system DB issue rather than permission.Hope this helps. |
 |
|
tosscrosby
Aged Yak Warrior
676 Posts |
Posted - 2008-10-17 : 10:59:17
|
You can usually open the log file with notepad or wordpad at the server level. Look in \MSSQL\LOG in the install folder. Pick the appropriately dated file.Terry |
 |
|
|
|
|