Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


database 'master' is not valid 9003 error Help!!!


database 'master' is not valid 9003 error Help!!!

Author
Message
fasih
fasih
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 3
hello guys,

I am having the same problem and sql server 2005 is not starting , every solution on the web requires sql server service to be running , or require to connect to SSMS , but to connect to sql server management studio sql server service must be running, i am in terrible condition, please if you guys have any solution.. I have already treid rebuilding master database but even after that nothing is working........... please help.

This is the log file

009-07-13 17:05:43.43 Server Detected 2 CPUs. This is an informational message; no user action is required.
2009-07-13 17:05:43.56 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-07-13 17:05:43.57 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-07-13 17:05:44.59 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-07-13 17:05:44.59 Server Database Mirroring Transport is disabled in the endpoint configuration.
2009-07-13 17:05:44.59 spid4s Warning ******************
2009-07-13 17:05:44.60 spid4s SQL Server started in single-user mode. This an informational message only. No user action is required.
2009-07-13 17:05:44.60 spid4s Starting up database 'master'.
2009-07-13 17:05:44.70 spid4s Error: 9003, Severity: 20, State: 1.
2009-07-13 17:05:44.70 spid4s The log scan number (239:200:1) passed to log scan in database 'master' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
2009-07-13 17:05:44.70 spid4s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47198 Visits: 44367
Do you have a backup of master?
How did you rebuild the master database and how did you verify that it really did get rebuilt?


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


fasih
fasih
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 3
I rebuild the master database using the command

start /wait \server\setup.exe /qn MSSQLSERVER reinstall=sql_engine rebuilddatabase=1 sapwd=mypassword

I checked the log file and it say completed succesfully .

I am desperate....
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47198 Visits: 44367
Maybe give Microsoft's customer support a shout. I've heard of a case where the rebuild says it succeeded but didn't, not sure why that could happen. Calling CSS will be a lot faster than getting free assistance here.

It isn't maybe a case where master is somewhere other than the default location and the rebuild put the new files in the default location?


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


mpmpolat
mpmpolat
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 3
if you haven't a backup file you must recreate log file. i tried it. it's sucsess.
harish_8080
harish_8080
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 0
Here's my side of story on solving this problem.
I'm using SQL Server 2008 Express Edition on Windows 7

Started SQL Server (SQLEXPRESS) and got error code 3414
After checking on error log, it was showing

The log scan number (19:136:1) passed to log scan in database 'model' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.


But i do not has backup of model or any database present in the "DATA" folder. There's a really simple solution for this.

Go to "Binn" directory of you MS SQL SERVER.
For me its "C:\Program Files\Microsoft SQL. Server\MSSQL10.SQLEXPRESS\MSSQL\Binn".
In Binn directory, go to the "Templates" folder.
And there is the model, master and msdbdata database mdf and ldf files which was installed with the MS SQL SERVER.
Replace the database file with the corrupted one.


This works for me.
Hope it works for you because it gets 2 hours for me to solve this problemCrazy
ayanmukherjee
ayanmukherjee
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 1
Hello harish

Thanks a ton it works perfectly

Thanks

Ayan
puneet_dwivedi
puneet_dwivedi
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 1
Hi What do you mean by >> Replace the database file with the corrupted one??
I am having similar issue I can locate the folder and see the files but how to replace them.
Please let me know:-)

Many Thanks
Regards
Puneet

harish_8080 (3/18/2011)
Here's my side of story on solving this problem.
I'm using SQL Server 2008 Express Edition on Windows 7

Started SQL Server (SQLEXPRESS) and got error code 3414
After checking on error log, it was showing

The log scan number (19:136:1) passed to log scan in database 'model' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.


But i do not has backup of model or any database present in the "DATA" folder. There's a really simple solution for this.

Go to "Binn" directory of you MS SQL SERVER.
For me its "C:\Program Files\Microsoft SQL. Server\MSSQL10.SQLEXPRESS\MSSQL\Binn".
In Binn directory, go to the "Templates" folder.
And there is the model, master and msdbdata database mdf and ldf files which was installed with the MS SQL SERVER.
Replace the database file with the corrupted one.


This works for me.
Hope it works for you because it gets 2 hours for me to solve this problemCrazy

Andreas AJV
Andreas AJV
Valued Member
Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)

Group: General Forum Members
Points: 54 Visits: 6
The expression "Replace the database file with the corrupted one." is wrong.
The correct one must be:
Replace the corrupted ones with the database files in Templates directory.

I have test it and it works.

Thnx

------------
When you 've got a hammer, everything starts to look like a nail...
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search