Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2039
  • Last Modified:

Sql Server won't start

I had a (hopefully) unrelated hardware problem and restarted my server, but on restart, Sql isn't starting.  When I try and start it manually in Services, I get the following message: "The MSSQLSERVER service on Local Computer started and then stopped.  Some services stop automatically etc...."  The Event Log has this message in it:
17113 :
initconfig: Error 2(The system cannot find the file specified.) opening 'master.mdf' for configuration information.

I am not very experienced with SQL so i'm not sure how to change the configuration settings or what settings may have been altered.  I've made several changes to the configuration since the last reboot.  Where do I start?
0
rdotson102
Asked:
rdotson102
  • 4
  • 4
  • 2
1 Solution
 
ptjcbCommented:
It seems that you have lost your Master database (which has all of the configuration information). This article might help:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q273572
0
 
rdotson102Author Commented:
The master database is fine.  I've tried restoring an older copy of it, with no change.  Besides, the error seems to indicate that it's reading the master db because it can't find some other file.
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
rdotson102Author Commented:
What if there's a problem with the registry?  How could I rebuild the registry without having to do a complete reinstall?
0
 
ptjcbCommented:
From
http://www.microsoft.com/resources/documentation/msa/idc/all/solution/en-us/oag/oagc20.mspx

Failure to recover system or user databases

Another major startup task performed during SQL Server startup is to recover each system and user database. If SQL Server fails to recover any of the system databases (master, msdb, tempdb, model are the system databases in SQL Server 2000), you may not be able to start Sql Server 2000 service. The reason for the failure will be logged in detail in the error log file as discussed previously.

If SQL Server fails to recover the master database, this failure may be due to something as simple as not being able to locate the files. You may see a similar message to one of the following:
•      

Initconfig: Error 2(The system cannot find the file specified.) opening 'C:\Program Files\Microsoft SQL Server\MSSQL\data\master.mdf' for configuration information.
•      

Udopen: Operating system error 3(The system cannot find the path specified.) during the creation/opening of physical device C:\Program Files\Microsoft SQL Server\MSSQL1\data\mastlog.ldf.
•      

FCB::Open failed: Could not open device C:\Program Files\Microsoft SQL Server\MSSQL1\data\mastlog.ldf for virtual device number (VDN) 2.

As the messages clearly indicate, SQL Server cannot find or open the file at the original location. To fix the problem you need to make sure that the files are in the specified location and that the SQL Server account has read/write access to them.

0
 
rdotson102Author Commented:
I'm running Sql Server 2000 and that solution doesn't apply to me.  Like I said, the master db is where it's supposed to be and perfectly fine.  There has to be some other solution to this one.
0
 
Anthony PerkinsCommented:
>>Like I said, the master db is where it's supposed to be and perfectly fine.<<
How do you know?  Is it even attached to the server?
0
 
Anthony PerkinsCommented:
>>I've tried restoring an older copy of it, with no change. <<
How did you do this?  Please don't say you used Windows Explorer to copy.
0
 
rdotson102Author Commented:
ptjcb, the link you posted is the closest thing to the correct solution on this one.  For some reason, when I clicked on it, I thought it was a different solution.  I'm sorry.  After I posted the original question, I found that link which led me to rebuild the registry by choosing that option in the sql server 2000 setup.  After the registry rebuild, it worked fine.  I got it working before anyone responded, but I don't need the points and can't stand asking for a refund, so I was trying to get someone to provide the solution for me.  I was trying to lead you to the right thing with the question about the registry rebuild, which is why I was also so emphatic about the master db being in the right place.  Sorry about the trouble.  Anyway, you get the points.  Thanks a lot.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 4
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now