September 26, 2009 at 5:48 am
I have a SQL2008 box, thank God its a minor development box, that won't start SQL Server 2008 Developer Edition.
It gives messages talking about a corrupt ldf file for the master database.
Great I'll start the service in minimal mode and restore the master database. Only I can't because without the master database the service won't start to the point where I can do a restore.
Next attempt is to rebuild the master
1. Navigate to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release
2. Run setup.exe /ACTION=REBUILDDATABASE /QUIET /INSTANCENAME=D_POOLE /SQLSYSADMINACCOUNTS=D_POOLE\David
After hanging around for a bit I get an error message which tells me to look at summary.txt file log. the message is recorded in summary.txt as follows
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643838
Exit facility code: 1203
Exit error code: 2
Exit message: The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for further details.
Start time: 2009-09-26 12:36:31
End time: 2009-09-26 12:37:13
Requested action: RebuildDatabase
Tried the repair option from the DVD. Generated an error message and didn't achieve anything. Not sure what to do now short of uninstalling SQL2008 and re-installing it. Thank God this isn't a production environment.
October 27, 2009 at 4:00 pm
Is your instance in mixed mode? If it is, you also have to supply the SA password for the repair.
October 28, 2009 at 5:13 am
What is in the install logs? These are normally found in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Logs
You get one folder in \Logs for every time you run SETUP, so look in the most recent folder. The files with Summary in the name are worth looking at first as they sometimes show the root cause at the top of the file. Otherwise you will have to look in the Detail files.
With a Detail file, start at the bottom and scroll up. You will need to scroll past all the error messages, then scroll down to see how the error develops. Sometimes the error given nearest the end of the file is not the root cause, but the error second nearest the end often is.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 29, 2009 at 4:09 pm
It has been mentioned before but, as a quick hack, if you restore the good master backup to a temporary database on another server that has exactly the same build then replace the corrupt master files with those new database files you should be able to start the server OK.
I just tried it with a test server here and it seems to work fine.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply