June 22, 2006 at 4:45 am
Hi
The MSsql sevrer service is not starting.The system was shutdown abruptly and then when it got restarted it is giving error and not starting the service.The error message it is dispaying is
"Could Not start MSSQLServer service on Local Computer.
The service did not return an error.This could be an internal windows error or an internal service error.If the problem persists,contact your system admisnistrator."
How do I go about solving it.
June 22, 2006 at 8:30 am
Check the account by which your service was running OR try starting it from different account.
------------
Prakash Sawant
http://psawant.blogspot.com
June 22, 2006 at 9:47 am
Check the Windows System log as well. It should contain more info.
June 22, 2006 at 10:16 am
Windos system log has this info "unable to do recovery for master database.Exiting"
June 26, 2006 at 11:27 am
It sounds like it is now time to recover the amster database from your last full backup. Once you perform this you should be able to start up the instance. If not it will lead you to the next set of issues. I'd be prepared to restore model and msdb as well.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
June 26, 2006 at 11:50 pm
Check recent SQL Error Logs and see exact reason for not able to recover master. As suggested by Rudy you may need to restore last full backup of master,.
June 27, 2006 at 4:20 am
If you can't start SQL Server and you want to restore the master database, you will need to rebuild the master database first using the rebuildm utility. This isn't a lot of fun (although it's good experience), so I would suggest, as Balmukund mentions, checking the error log first. If you can't find the error log, the chances are that the reason for your problem is that you've specified an invalid path to it in your -e startup parameter. You can use sqlservr -c (I think that's the right syntax) to start SQL Server from the command line and have the "error" messages displayed on screen. You may need to specify paths to the master data and log files and the error log if they're not in default locations, and there are a whole host of other parameters you can use, such as minimal configuration and trace options. Check out the full syntax in Books Online.
John
June 27, 2006 at 5:15 am
Thanks for correcting me John. I agree with action plan given by John. to Add:
First step will be rebuild master database and then you need to restore from the backup (i am assuming that you have good backup)
June 27, 2006 at 6:13 am
You should only rebuild/restore master as a last resort, and after ascertaining (or attempting to ascertain) the cause of the failure. I can't think of any reason to rebuild/restore other than corruption or deletion of data file(s) (apart from to change the server collation, but that's another topic). If SQL Server is not starting because a drive letter that the data files depend on has changed, for example, it will be much easier and safer to fix that condition than to go through an unnecessary procedure.
So find that error log and see what it says. If it doesn't exist, run sqlservr -eX:\MyPath\errorlog where X:\MyPath is the drive letter and path to where you want the error log to be.
Good luck
John
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply