MSSQLSERVER stopped and does not start

  • Dear All,

    I am new in SQLServer and face a problem starting the MSSQLSERVER service. If i try to start it from services property I get an error and it stops immediately. Below is the log file generated from the service:

    ___________________________________________________________________________________________________

    "May 3 2005 23:18:38

    Copyright (c) 1988-2003 Microsoft Corporation

    Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)

    2011-11-28 23:38:04.54 server Copyright (C) 1988-2002 Microsoft Corporation.

    2011-11-28 23:38:04.54 server All rights reserved.

    2011-11-28 23:38:04.54 server Server Process ID is 3424.

    2011-11-28 23:38:04.54 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.

    2011-11-28 23:38:04.56 server SQL Server is starting at priority class 'normal'(2 CPUs detected).

    2011-11-28 23:38:04.57 server SQL Server configured for thread mode processing.

    2011-11-28 23:38:04.59 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.

    2011-11-28 23:38:04.60 spid4 Starting up database 'master'.

    2011-11-28 23:38:04.65 spid4 Error: 9003, Severity: 20, State: 1.

    2011-11-28 23:38:04.67 spid4 Cannot recover the master database. Exiting."

    ___________________________________________________________________________________

    Any kind of your help shall be much appreciated.

    Best regards

  • It can't find the master database, or it's corrupt. What was the last thing that happened on this server?

    Can you pull up the tail of the previous error log (you'll find it in the same directory as the path listed there) and post the last 100 entries or so? It should be ERRORLOG.1.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • I should have mentioned, right about now is when you want to make dang sure you know where a valid copy of your master db backups are, and the most recent as possible that it was functioning.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • And if you can't find a good backup of the master database, prepare your resume and punt! (select * from references where reference_business_name <> 'business name')

  • If the Master DB is corrupt, you will have to rebuild it - this is done with the installation media.

    Something like this

    start /wait <CD or DVD Drive>\setup.exe /qn

    INSTANCENAME=<InstanceName> REINSTALL=SQL_Engine

    REBUILDDATABASE=1 SAPWD=<NewStrongPassword>

    Then you need to restore the Master DB, if you have a backup.

  • This process is different in 2008 though.

  • derekr 43208 (11/28/2011)


    If the Master DB is corrupt, you will have to rebuild it - this is done with the installation media.

    Something like this

    start /wait <CD or DVD Drive>\setup.exe /qn

    INSTANCENAME=<InstanceName> REINSTALL=SQL_Engine

    REBUILDDATABASE=1 SAPWD=<NewStrongPassword>

    Then you need to restore the Master DB, if you have a backup.

    I would agree, but until we know more I wouldn't rebuild. It could be as simple as a permissions policy. The reason for the last shutdown and more information and feedback from the OP will help us find the correct course of action. Having the backup handy will also be a better option most of the time.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • Evil Kraig F (11/29/2011)


    derekr 43208 (11/28/2011)


    If the Master DB is corrupt, you will have to rebuild it - this is done with the installation media.

    Something like this

    start /wait <CD or DVD Drive>\setup.exe /qn

    INSTANCENAME=<InstanceName> REINSTALL=SQL_Engine

    REBUILDDATABASE=1 SAPWD=<NewStrongPassword>

    Then you need to restore the Master DB, if you have a backup.

    I would agree, but until we know more I wouldn't rebuild. It could be as simple as a permissions policy. The reason for the last shutdown and more information and feedback from the OP will help us find the correct course of action. Having the backup handy will also be a better option most of the time.

    Complete agree with you, that's why I started my response with

    If the Master DB is corrupt

  • I am curious to know if this is a new installation or an existing one. And if it is existing, has it been working before? To your knowledge, how long has it not been working?

    I know many environments where servers have bad installs and never work, but no one knows about it until someone new joins the team or takes over the responsibility.

    Can you still contact the people who installed? Or was this a dev install you put on a laptop or desktop/

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Dear Friends,

    Thanks in advance all of you engaged on my issue. As I mentioned on my firs message I have not much experience on SQL services, so I cannot tell you more details. Moreover I have difficulties because the base operation System when I try to start the MSSQL server is in Greek language and some of error messages I cannot understand well, so just I am telling you some other details to have you an idea of the problem. I am mentioned for a program installed in a PC runing on Windows XP home Greek edition SP2, with CPU Intel P4 2.8 MHz and 512 Mb RAM. The program is one for manage a kind of POS (Point of Sales) it have a database for, customers, receipts, payments, and so on. This program is in Greek language as well and MSSQL server 2000 has been installed by this program. The program has worked correct for a period of 4 years and the problem has been caused by un proper shutdown because of fail of electricity. This is all that I have for the problem. Something else; When I try to start the service from Services Computer Management I get an error similar to this: "Error starting the MSSQLSERVER, same services start and stops immediately if they have not to do something, please try to start it again later" One more time I would like to thank you all for your help and you are welcome If someone have any idea to help me to solve this problem.

    Best regards,

  • As Craig requested, please post the contents of C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG and ERRORLOG1. This will help us help you.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • f.panci (11/29/2011)


    The program has worked correct for a period of 4 years and the problem has been caused by un proper shutdown because of fail of electricity. This is all that I have for the problem.

    Call the company that provided you the software and explain to them you have a corrupt master database in the installation they provided. Said power failure most likely fragged up the disk cache and left the master db out of sync. To save you some time when you call them you're going to need to locate the backups of your databases.

    This is not something you want to handle in the wrong language and being unfamiliar with the problem when you have support available to you via the vendor. This is a significant enough issue that it can completely hose up your data.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • I have seen this type of problem before, where SQL Server cannot start on XP because of file corruption following a power failure.

    I completely agree with the advice to contact the vendor. They should have greater skills in dealing with this problem than you have.

    However, the bad news is that the problem with the master database may only be the first of many issues you will have. If master is damaged then your own databases may also be damaged and have to be restored from backups. Your vendor should be able to help but they may charge for this.

    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

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply