Page 1 of 2 12 LastLast
Results 1 to 15 of 16
  1. #1
    Join Date
    Nov 2008
    Posts
    4

    Unanswered: MS SQL server won't start

    Hi everyone,

    I'm having an issue with MS SQL server, basically the server won't start. From the task bar I open the SQL Server Service Manager and click on the start button, it thinks about it for a few seconds then stops. I have managed to get a copy of the SQL server log and believe I have found the error but I'm unfamiliar on how to correct it, can anyone give me some easy to follow steps or direct me to a website that can help.

    Here is the ErrorLog

    2008-11-22 10:15:39.87 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
    Dec 17 2002 14:22:05
    Copyright (c) 1988-2003 Microsoft Corporation
    Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)

    2008-11-22 10:15:39.87 server Copyright (C) 1988-2002 Microsoft Corporation.
    2008-11-22 10:15:39.87 server All rights reserved.
    2008-11-22 10:15:39.87 server Server Process ID is 1576.
    2008-11-22 10:15:39.87 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SAGETAXATION\LOG\ERRORLOG'.
    2008-11-22 10:15:39.89 server SQL Server is starting at priority class 'normal'(1 CPU detected).
    2008-11-22 10:15:39.92 server SQL Server configured for thread mode processing.
    2008-11-22 10:15:39.92 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
    2008-11-22 10:15:39.95 spid3 Starting up database 'master'.
    2008-11-22 10:15:40.14 server Using 'SSNETLIB.DLL' version '8.0.766'.
    2008-11-22 10:15:40.15 spid5 Starting up database 'model'.
    2008-11-22 10:15:40.17 server SQL server listening on 192.168.1.64: 1433.
    2008-11-22 10:15:40.17 server SQL server listening on 127.0.0.1: 1433.
    2008-11-22 10:15:40.17 server SQL server listening on TCP, Shared Memory, Named Pipes.
    2008-11-22 10:15:40.17 server SQL Server is ready for client connections
    2008-11-22 10:15:40.17 spid3 Server name is 'SMITHFIE-07HQKN\SAGETAXATION'.
    2008-11-22 10:15:40.17 spid3 Skipping startup of clean database id 5
    2008-11-22 10:15:40.17 spid3 Skipping startup of clean database id 6
    2008-11-22 10:15:40.20 spid8 Starting up database 'msdb'.
    2008-11-22 10:15:40.20 spid9 Starting up database 'TaxSecurities_1994'.
    2008-11-22 10:15:40.20 spid10 Starting up database 'TaxSecurities_1995'.
    2008-11-22 10:15:40.20 spid11 Starting up database 'TaxSecurities_1996'.
    2008-11-22 10:15:40.56 spid5 Error: 9003, Severity: 20, State: 1
    2008-11-22 10:15:40.56 spid5 The LSN (12:299:1) passed to log scan in database 'model' is invalid..
    2008-11-22 10:15:40.75 spid11 Starting up database 'TaxSecurities_1997'.
    2008-11-22 10:15:40.76 spid8 Starting up database 'TaxSecurities_1998'.
    2008-11-22 10:15:40.76 spid10 Starting up database 'TaxSecurities_1999'.
    2008-11-22 10:15:40.79 spid9 Starting up database 'TaxSecurities_2000'.
    2008-11-22 10:15:41.45 spid10 Starting up database 'TaxSecurities_2001'.
    2008-11-22 10:15:41.46 spid11 Starting up database 'TaxSecurities_2002'.
    2008-11-22 10:15:41.46 spid8 Starting up database 'TaxSecurities_2003'.

    Any help much appreciated.

    Regards

    Marc

  2. #2
    Join Date
    Nov 2004
    Location
    on the wrong server
    Posts
    8,835
    Provided Answers: 6
    That's a strange error. I have not googled it, but it is saying the Log Sequence Number of the transaction log being applied to the database during recovery (which happens during startup) is invalid for your model database.

    That being said, the most common cause of a sql instance no starting up is that the security credential used by the account that runs the SQL Server service is not valid anymore or that account is locked out or it's password has changed.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  3. #3
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    If model is corrupt, you can't create a new copy of tempdb. This would prevent SQL Server from starting.

    First and foremost, make a good backup of the MDF and LDF files. Your server is in a fragile state, and even a mnior boo-boo could leave the datbase files corrupt. To make a backup when you can't start SQL Server properly:

    1) Use the Windows Control Panel to set the SQL Server service to manual.
    2) Reboot Windows
    3) Copy all of the MDF and LDF files to either another machine or removable media (like a DVD).

    Do not do anything else until you have good backups.

    The fix is usually easy, but trying it right now would put all of your data at risk.

    -PatP

  4. #4
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Ok, that one died pretty abruptly. Either they found another fix, or for some reason they just don't care.

    -PatP

  5. #5
    Join Date
    Nov 2008
    Posts
    4
    Sorry guys, only managed to check the forum this morning. I'm sort of stuck as I won't get on the PC until tommorrow so I can't try anything but I will do the backup first as Pat has suggested. Thanks for the help.

    Marc

  6. #6
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Ah, I thought that you'd wandered off on us... That happens a lot.

    Once you have the backup made, you have three choices for fixing the problem.

    The best answer is if you have a backup of your own model database. You'll have to use another copy of SQL Server with the same version / patch level (like SQL 2005, Service Pack 1) to restore your model using the MODEL.MDF and MODEL.LDF filenames but a different database name such as "ONo" or anything else that makes sense to you. This means that you'll have to put the files into a different directory. This is messy, but not hard. Once you've got your model backup restored, detach it from the new server and copy the files to replace the ones on your crippled server.

    If you don't have a backup, I'd recommend that you install a new copy of SQL Server and when that installation is complete stop the service and copy the MODEL.* files to replace the ones on your crippled server.

    A last ditch effort that may or may not work would be to rename the MODEL.LDF file to something like MODEL.BAD. Some times this will work and will allow you to keep any customizations you've made to the model database. This is not supported by Microsoft, and it is strictly a "last ditch" effort.

    -PatP

  7. #7
    Join Date
    Nov 2008
    Posts
    4
    Thanks Pat, I'll give it a try and let you know how it turns out.

    Marc

  8. #8
    Join Date
    Nov 2008
    Posts
    4
    Hi all,

    Right first problem is I'm a newbie at SQL, sorry but I have created a backup copy of the SQL folder with the database in and I have noticed a 'Backup' folder full of files with the extension *.bkp is it possible to use these files to restore the 'MODEL' files and if so how? not sure what software to use to restore on another pc and then copy back to the old PC (If that is the procedure you mentioned above) Again any help much appreciated.

    Marc

  9. #9
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    I'd expect the files to be named *.BAK, but I'll work under the assumption that they are named *.BKP for some reason on your system. The first thing I'd suggest is to verify the file date and time... Model doesn't change often, but the other files probably do need to be quite current. If there is a file named MODEL.BKP, then you've got a chance.

    -PatP

  10. #10
    Join Date
    Jan 2009
    Posts
    2

    Solved the same problem

    I had the same problem and thank you for helping me to solve it:

    I did the same thing:
    a just copied 'healthy' model.mdf and modellog.ldf
    from another server over the 'ill' ones on my server and
    when a tried to start SQL server again it was OK.

    There were some events in the Application log
    about 'recovery completion'.

    Of course, don't forget to make backup of your valuable
    mdfs and ldfs first !

    thank you all

  11. #11
    Join Date
    Jan 2009
    Posts
    2
    I had the same problem and thank you for helping me to solve it:

    I did the same thing:
    a just copied 'healthy' model.mdf and modellog.ldf
    from another server over the 'ill' ones on my server and
    when a tried to start SQL server again it was OK.

    There were some events in the Application log
    about 'recovery completion'.

    Of course, don't forget to make backup of your valuable
    mdfs and ldfs first !

    thank you all

  12. #12
    Join Date
    Jul 2009
    Posts
    1
    Thanks Pat! The same solution worked for me with a similar error. I thought I would post here to say thanks and hopefully seed google with some error message text to help others in the future.

    My SQL 2000 server wouldn't start. The server was turned off for a weekend and then Poof! on Tuesday, no SQL.

    Event Log Error ( Source MSSQLSERVER, EVENTID 17052 )

    Error: 823, Severity: 24, State: 2
    I/O error (torn page) detected during read at offset 0x00000000012000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf'.

    Based on docs, I think it was hard drive corruption caused by shutting down a 24/7 server all of a sudden like that.

    Solution was to stop SQL on another server, copy model.mdf and modellog.ldf to broken server, reboot.
    Last edited by Terillius; 07-21-09 at 20:44.

  13. #13
    Join Date
    Feb 2011
    Posts
    3

    Success!

    Thanks PAT! You're the man! The same happened to our server, which logged the error: EXCEPTION 0XC00000FD EXCEPTION_STACK_OVERFLOW AT 0X00404FFB0.

    Instead of just the MODEL files, we copied all the SQL built-in .MDL and .LDF files from a "healthy" server to the corrupted one, and it started successfully! *SIGH* Good thing I saw this forum. Thanks a lot!

  14. #14
    Join Date
    Apr 2008
    Location
    Iasi, Romania
    Posts
    561
    Provided Answers: 2
    Quote Originally Posted by andyxis View Post
    we copied all the SQL built-in .MDL and .LDF files from a "healthy" server
    All including master database? Hmm.
    Florin Aparaschivei
    DB2 9.7, 10.5 on Windows
    Iasi, Romania

  15. #15
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Quote Originally Posted by andyxis View Post
    Instead of just the MODEL files, we copied all the SQL built-in .MDL and .LDF files from a "healthy" server to the corrupted one, and it started successfully! *SIGH* Good thing I saw this forum. Thanks a lot!
    Yikes!!! Copying msdb is rarely a good idea (sometimes useful for recovering from a disaster, but only under CAREFULLY controlled circumstances and very short periods of time). Copying master seems like a reciepe for disaster to me!

    I'm glad that this worked for you, but I'm not very comfortable with it.

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •