Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL Server will not start after reboot

Status
Not open for further replies.

1DMF

Programmer
Jan 18, 2005
8,795
GB
Hi,

I was having problems with our test DB where MS Access wouldn't let me alter anything (we use it as the front end).

I had refreshed the tables again and again, deleted user accounts, added back in and gave it dbo_owner role.

Still I could not get the test DB to work, I even restored the live DB as the test DB seings as the Access front end works on the live DB no problem, but still the test would not work.

So I thought maybe SQL needs a reboot to clear something as no matter what i did the test db would not allow MS access to alter anything, add records, delete etc.. which seemed like privilage problems.

However on re-boot SQL won't even start with the following error
17113 : initconfig Error 2(error not found) opening 'master.mdf' for configuration

I rebooted again, still same problem, I've done a google and checked that the path in the regkeys for HKLM was not corrupt but this is pointing to the correct place where the data is, also the 'master.mdf' file does exist.

Any ideas what is happening, why and how to correct it.

Thanks.

P.S. i've checked norton and made sure that the SQL folders are excluded in the realtime scan, so it's not an access issue regarding Anti-Virus.

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you.
 
You say the Master.mdf doesn't exist. That's the problem there. Did you or someone else move it or delete it?

You will need to reinstall SQL Server. Save the .mdf files from your user databases and when you reinstall SQL Server, attach those databases.

-SQLBill

Posting advice: FAQ481-4875
 
Bill,

thanks for the reply but you have miss read the post
also the 'master.mdf' file does exist.

I wish it was that simple, i would have done a restore hours ago :)

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you.
 
Any idea what is going on, why it is saying files are missing that aren't and what might have caused this?

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you.
 
Yep, I misread that. But apparently something has 'damaged' the master file. You say you restored the Live DB to the test server. Did you restore ALL the databases (including Master)? If not, try that. If that works....something corrupted your Master file. If that doesn't work, you might have a disk problem.

-SQLBill

Posting advice: FAQ481-4875
 
NO I restored the LIVE DB to the TEST DB, that's all, same sever we only have one it's SBS 2003.

Hope not we have 3 x 72 gig SCSI runing Raid Level 5 striping, so even if a disk goes down it's suppose to still run on 2 isn't it?

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you.
 
I ended up having to re-install SQL, then had the nightmare that the backup wouldn't restore as our support guys had applied SP4 and the backup was created with SP3.

The master DB has been restored and it's finally starting to look up. Only been down for 5 days including the weekend, what fun we have!

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top