== The SQL Server service failed to start ==

I'm newbe with SQL Server , I'm looking for help with sql server express edition 2005. At the end of installation ocurrs an error:

The SQL Server service failed to start.
For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually.
Error Number : 29503 . (Summary file)
Rest of components has status : Successfully installed

I've go installed .Net Framework 2.0, I'm using XP with SP2 , no anty-virus software during instalatin is activated, the XP firewall is off during instalation.All system check requirements are passed successufully
(running on Athlon64)

No additional software bound with SQL is installed.(in add/remove programs there is nothing additional connected with sql)

I've re-installed it few times with some other options (network , local) ,different installation path ,but allways the same result - fail. I've tried to find help in few similar posts but that didn't help.Mayby i've miss somethin'

Could someone help



Answer this question

== The SQL Server service failed to start ==

  • Erin Devoy

    Hi ...
    1.
    about the question ... i'm not upgrading from Express RTM to Express Advanced
    there is only .Net framework 2.0 installed and this trouble with SQL Server2005EE,
    there is no VisualStudio package.

    2.
    here is my ERRORLOG:

    2006-05-02 00:01:11.59 Server
    Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25
    Copyright (c) 1988-2005 Microsoft Corporation
    Express Edition on Windows NT 5.1 (Build 2600: Dodatek Service Pack 2)

    2006-05-02 00:01:11.59 Server (c) 2005 Microsoft Corporation.
    2006-05-02 00:01:11.60 Server All rights reserved.
    2006-05-02 00:01:11.60 Server Server process ID is 3892.
    2006-05-02 00:01:11.60 Server Logging SQL Server messages in file 'd:\sqlee\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2006-05-02 00:01:11.60 Server This instance of SQL Server last reported using a process ID of 3012 at 2006-05-02 00:01:03 (local) 2006-05-01 22:01:03 (UTC). This is an informational message only; no user action is required.
    2006-05-02 00:01:11.60 Server Registry startup parameters:
    2006-05-02 00:01:11.60 Server -d d:\sqlee\MSSQL.1\MSSQL\DATA\master.mdf
    2006-05-02 00:01:11.60 Server -e d:\sqlee\MSSQL.1\MSSQL\LOG\ERRORLOG
    2006-05-02 00:01:11.60 Server -l d:\sqlee\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2006-05-02 00:01:11.60 Server Command Line Startup Parameters:
    2006-05-02 00:01:11.60 Server -d d:\sqlee\MSSQL.1\MSSQL\Template Data\master.mdf
    2006-05-02 00:01:11.60 Server -l d:\sqlee\MSSQL.1\MSSQL\Template Data\mastlog.ldf
    2006-05-02 00:01:11.60 Server -m SqlSetup
    2006-05-02 00:01:11.60 Server SqlSetup
    2006-05-02 00:01:11.60 Server -Q
    2006-05-02 00:01:11.60 Server -q Polish_CI_AS
    2006-05-02 00:01:11.60 Server -T 4022
    2006-05-02 00:01:11.60 Server -T 3659
    2006-05-02 00:01:11.60 Server -T 3610
    2006-05-02 00:01:11.60 Server -T 4010
    2006-05-02 00:01:11.62 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2006-05-02 00:01:11.62 Server Detected 1 CPUs. This is an informational message; no user action is required.
    2006-05-02 00:01:11.76 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.
    2006-05-02 00:01:11.76 Server Database Mirroring Transport is disabled in the endpoint configuration.
    2006-05-02 00:01:11.76 spid5s Warning ******************
    2006-05-02 00:01:11.76 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
    2006-05-02 00:01:11.76 spid5s Starting up database 'master'.
    2006-05-02 00:01:11.85 spid5s 16 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
    2006-05-02 00:01:11.90 spid5s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
    2006-05-02 00:01:11.90 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2006-05-02 00:01:11.90 spid5s SQL Trace ID 1 was started by login "sa".
    2006-05-02 00:01:11.93 spid5s Starting up database 'mssqlsystemresource'.
    2006-05-02 00:01:11.93 spid5s The resource database build version is 9.00.2047. This is an informational message only. No user action is required.
    2006-05-02 00:01:12.03 spid7s Starting up database 'model'.
    2006-05-02 00:01:12.17 Server A self-generated certificate was successfully loaded for encryption.
    2006-05-02 00:01:12.17 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
    2006-05-02 00:01:12.17 spid5s Server name is 'TESTUSER\SQLEXPRESS'. This is an informational message only. No user action is required.
    2006-05-02 00:01:12.17 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
    2006-05-02 00:01:12.17 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2006-05-02 00:01:12.17 spid5s Starting up database 'msdb'.
    2006-05-02 00:01:12.26 spid5s 3 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
    2006-05-02 00:01:12.28 spid5s 0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
    2006-05-02 00:01:12.28 spid5s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    2006-05-02 00:01:12.29 spid7s Clearing tempdb database.
    2006-05-02 00:01:12.43 spid7s Starting up database 'tempdb'.
    2006-05-02 00:01:12.50 spid5s Warning ******************
    2006-05-02 00:01:12.50 spid5s Attempting to change default collation to Polish_CI_AS.
    2006-05-02 00:01:12.60 spid5s Using 'dbghelp.dll' version '4.0.5'
    2006-05-02 00:01:12.60 spid5s **Dump thread - spid = 5, PSS = 0x037247B0, EC = 0x037247B8
    2006-05-02 00:01:12.60 spid5s ***Stack Dump being sent to d:\sqlee\MSSQL.1\MSSQL\LOG\SQLDump0002.txt
    2006-05-02 00:01:12.60 spid5s * *******************************************************************************
    2006-05-02 00:01:12.60 spid5s *
    2006-05-02 00:01:12.60 spid5s * BEGIN STACK DUMP:
    2006-05-02 00:01:12.60 spid5s * 05/02/06 00:01:12 spid 5
    2006-05-02 00:01:12.60 spid5s *
    2006-05-02 00:01:12.60 spid5s * Location: "xisort.cpp":432
    2006-05-02 00:01:12.60 spid5s * Expression: cpagesInSystem > 0
    2006-05-02 00:01:12.60 spid5s * SPID: 5
    2006-05-02 00:01:12.60 spid5s * Process ID: 3892
    2006-05-02 00:01:12.60 spid5s *
    2006-05-02 00:01:12.60 spid5s *
    // the rest I've removed
    *******************************************************************************
    External dump process returned no errors. 2006-05-02 00:01:12.85 spid5s Error: 17066, Severity: 16, State: 1.
    2006-05-02 00:01:12.85 spid5s SQL Server Assertion: File: <"xisort.cpp">, line=432 Failed Assertion = 'cpagesInSystem > 0'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
    2006-05-02 00:01:12.85 spid5s Error: 3624, Severity: 20, State: 1.
    2006-05-02 00:01:12.85 spid5s A system assertion check has failed. Check the SQL Server error log for details
    2006-05-02 00:01:12.87 spid5s Error: 3434, Severity: 20, State: 1.
    2006-05-02 00:01:12.87 spid5s Cannot change sort order or locale. An unexpected failure occurred while trying to reindex the server to a new collation. SQL Server is shutting down. Restart SQL Server to continue with the sort order unchanged. Diagnose and correct previous errors and then retry the operation.
    2006-05-02 00:01:12.87 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    Maybe it's something with the language version("collation to Polish_CI_AS",after that starts the dump process )

    please help ...


  • gurvinder_gill

    The most obvious question is: Are you purposly trying to set the collation to Polish Just want to make sure.

    - Mike



  • venkatakrishna

    I'm experiencing the same problem. The Visual Basic Express package properly installed everything except SQL Server. I've run it many times, with the same error that Tom had, that the server failed to start. I also downloaded the separate installation package for SQL Server Express and ran it several times, which also failed. It gets to a point where the services are installed, but when I try to manually start the SQL service it says that the service started and then stopped. The log for the VB package says that SQL Server 2005 Express Edition returned an unexpected value. The event viewer shows an application error for the MsInstaller with event 10005, which says that SQL Server setup failed to modify security permissions for registry key SOFTWARE\Microsoft\Microsoft SQL Server\90\Replication for user Administrator. I have only one user created on the machine, created during installing the machine which is an administrator level account. No disk encryption, file encryption, disk compression, firewall or prior installs of SQL or Express software. I also tried logging in as user "Administrator" and running the install, but I get the same error. Any thoughts Thanks.

  • KOLY

    Hey Ethan,

    You still having this problem

    Regards,

    Mike Wachal
    SQL Express team

    ----
    Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=307712&SiteID=1



  • Erik_MSFT

    Hi Ethan,

    This is me confirming that if your CPU doesn't support prefetch, SQL Express will fail. You can read the KB article to be "official."

    919392 Error message when you try to install SQL Server 2005 Express Edition or SQL Server 2005 Express Edition with Advanced Services: "Server SQL Server is terminating because of fatal exception c000001d"
    http://support.microsoft.com/default.aspx scid=kb;EN-US;919392

    Regards,

    Mike Wachal
    SQL Express team

    ----
    Mark the best posts as Answers!



  • Guennadi Vanine

    Mike,

    Thank you for your reply.

    My problem is still not solved, but I have more information about this. I've shared this in this post https://forums.microsoft.com/MSDN/ShowPost.aspx PostID=379689&SiteID=1 .

    Of course, I've downloaded the software again and I've also tried both versions of SQL Server Express Edition SP1.

    For development and test purposes, I use an old computer as a server. This computer is based on an AMD K6-III CPU, which seems to be problematic when used with SQL Server Express. What is rather surprising is that Windows Server 2003 SP1 works perfectly on this machine as well as .Net 2.0.

    BUT... This possible compatibility issue has never been confirmed by Microsoft so a lot of poeple are still looking for a workaround because the installer just displays a warning and continues its process until it fails to start the service.

    Best regards.


  • DevDells

    I just tracked down some information about a possible cause here that may be interesting. The two most common causes of this error are:

    1. You're media is bad. - i.e. Try downloading the installer again, but I figure you've done this.
    2. Your CPU does not support cache prefetching.

    I don't have a list of CPUs that this affects, but it's worth checking into with your CPU mfg. I'd be real interested in hearing back if this is the issue.

    Regards,

    Mike Wachal
    SQL Express team

    ----
    Mark the best posts as Answers!



  • Commonman

    Hello,

    I really don't know what to do.

    I've reinstalled Windows Server 2003 with IIS, reinstalled .Net 2.0, reinstalled Windows Server 2003 SP1 and the circa 30 Hotfixes and it still doesn't works.

    I've tried to install the SQL Server 2005 Express Edition and the SQL Server 2005 Express Edition with Advanced Services.

    Same error again and again.

    Do I have to set special ACL

    Best regards.


  • Nele

    Hi again,

    I'm still stuck. I really don't know what to do. Even an "all default settings" didn't work.

    Here's my log :


    2006-05-11 03:40:05.23 Server      Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)
     Apr 14 2006 01:12:25
     Copyright (c) 1988-2005 Microsoft Corporation
     Express Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

    2006-05-11 03:40:05.23 Server      (c) 2005 Microsoft Corporation.
    2006-05-11 03:40:05.23 Server      All rights reserved.
    2006-05-11 03:40:05.23 Server      Server process ID is 572.
    2006-05-11 03:40:05.23 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2006-05-11 03:40:05.24 Server      This instance of SQL Server last reported using a process ID of 1480 at 11.05.2006 03:38:44 (local) 11.05.2006 01:38:44 (UTC). This is an informational message only; no user action is required.
    2006-05-11 03:40:05.24 Server      Registry startup parameters:
    2006-05-11 03:40:05.24 Server        -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
    2006-05-11 03:40:05.24 Server        -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
    2006-05-11 03:40:05.24 Server        -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2006-05-11 03:40:05.24 Server      Command Line Startup Parameters:
    2006-05-11 03:40:05.24 Server        -m SqlSetup
    2006-05-11 03:40:05.24 Server        SqlSetup
    2006-05-11 03:40:05.24 Server        -Q
    2006-05-11 03:40:05.24 Server        -q French_CI_AS
    2006-05-11 03:40:05.24 Server        -T 4022
    2006-05-11 03:40:05.24 Server        -T 3659
    2006-05-11 03:40:05.24 Server        -T 3610
    2006-05-11 03:40:05.24 Server        -T 4010
    2006-05-11 03:40:05.26 Server      Error: 17311, Severity: 16, State: 1.
    2006-05-11 03:40:05.26 Server      SQL Server is terminating because of fatal exception c000001d. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
    2006-05-11 03:40:05.27 Server      Using 'dbghelp.dll' version '4.0.5'
    2006-05-11 03:40:05.31 Server      **Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
    2006-05-11 03:40:05.31 Server      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0024.txt
    2006-05-11 03:40:05.31 Server      * *******************************************************************************
    2006-05-11 03:40:05.31 Server      *
    2006-05-11 03:40:05.31 Server      * BEGIN STACK DUMP:
    2006-05-11 03:40:05.31 Server      *   05/11/06 03:40:05 spid 0
    2006-05-11 03:40:05.31 Server      *
    2006-05-11 03:40:05.31 Server      * ex_handle_except encountered exception C000001D - Server terminating
    2006-05-11 03:40:05.31 Server      *
    2006-05-11 03:40:05.31 Server      *
    2006-05-11 03:40:05.31 Server      *  MODULE                          BASE      END       SIZE
    2006-05-11 03:40:05.31 Server      * sqlservr                       01000000  02BCEFFF  01bcf000
    2006-05-11 03:40:05.31 Server      * ntdll                          7C920000  7C9E5FFF  000c6000
    2006-05-11 03:40:05.31 Server      * kernel32                       7C800000  7C911FFF  00112000
    2006-05-11 03:40:05.31 Server      * MSVCR80                        78130000  781CAFFF  0009b000
    2006-05-11 03:40:05.31 Server      * msvcrt                         77B70000  77BC9FFF  0005a000
    2006-05-11 03:40:05.31 Server      * MSVCP80                        7C420000  7C4A6FFF  00087000
    2006-05-11 03:40:05.31 Server      * ADVAPI32                       77D70000  77E1DFFF  000ae000
    2006-05-11 03:40:05.31 Server      * RPCRT4                         77C20000  77CBEFFF  0009f000
    2006-05-11 03:40:05.31 Server      * USER32                         77F30000  77FC1FFF  00092000
    2006-05-11 03:40:05.31 Server      * GDI32                          77BD0000  77C17FFF  00048000
    2006-05-11 03:40:05.31 Server      * CRYPT32                        76160000  761F4FFF  00095000
    2006-05-11 03:40:05.31 Server      * MSASN1                         76140000  76151FFF  00012000
    2006-05-11 03:40:05.31 Server      * Secur32                        76F00000  76F12FFF  00013000
    2006-05-11 03:40:05.31 Server      * MSWSOCK                        719F0000  71A31FFF  00042000
    2006-05-11 03:40:05.31 Server      * WS2_32                         71AD0000  71AE6FFF  00017000
    2006-05-11 03:40:05.31 Server      * WS2HELP                        71AC0000  71AC7FFF  00008000
    2006-05-11 03:40:05.31 Server      * USERENV                        768D0000  76995FFF  000c6000
    2006-05-11 03:40:05.31 Server      * opends60                       333E0000  333E6FFF  00007000
    2006-05-11 03:40:05.31 Server      * NETAPI32                       71B10000  71B67FFF  00058000
    2006-05-11 03:40:05.31 Server      * SHELL32                        7C9F0000  7D1FFFFF  00810000
    2006-05-11 03:40:05.31 Server      * SHLWAPI                        77CD0000  77D21FFF  00052000
    2006-05-11 03:40:05.31 Server      * comctl32                       77E20000  77F22FFF  00103000
    2006-05-11 03:40:05.31 Server      * psapi                          76B20000  76B2AFFF  0000b000
    2006-05-11 03:40:05.31 Server      * instapi                        48060000  48069FFF  0000a000
    2006-05-11 03:40:05.31 Server      * sqlevn70                       4F610000  4F7FAFFF  001eb000
    2006-05-11 03:40:05.31 Server      * sqlevn70                       007D0000  00963FFF  00194000
    2006-05-11 03:40:05.31 Server      * dbghelp                        03000000  03112FFF  00113000
    2006-05-11 03:40:05.31 Server      *
    2006-05-11 03:40:05.31 Server      *        Edi: 0072C548:  000E21C8  00000000  00000000  00000000  00000000  00000000 
    2006-05-11 03:40:05.31 Server      *        Esi: 00000000: 
    2006-05-11 03:40:05.31 Server      *        Eax: 0072C42C:  000042AC  00000000  00000000  7C815DEA  00000000  0000000C 
    2006-05-11 03:40:05.31 Server      *        Ebx: 0000003F: 
    2006-05-11 03:40:05.32 Server      *        Ecx: 0072CA9C:  00000000  00010007  00000000  0090008E  000E21CC  0072C45C 
    2006-05-11 03:40:05.32 Server      *        Edx: 0000003D: 
    2006-05-11 03:40:05.32 Server      *        Eip: 7C815DEA:  10C2C95E  90909000  A1649090  00000018  C334408B  891C428B 
    2006-05-11 03:40:05.32 Server      *        Ebp: 0072C47C:  0072C4C0  02187744  000042AC  00000000  00000000  00000000 
    2006-05-11 03:40:05.32 Server      *      SegCs: 0030001B: 
    2006-05-11 03:40:05.32 Server      *     EFlags: 00000246: 
    2006-05-11 03:40:05.32 Server      *        Esp: 0072C428:  00000000  000042AC  00000000  00000000  7C815DEA  00000000 
    2006-05-11 03:40:05.32 Server      *      SegSs: 78130023:  00000000  00000000  00000000  00000000  00000000  00000000 
    2006-05-11 03:40:05.32 Server      * *******************************************************************************
    2006-05-11 03:40:05.32 Server      * -------------------------------------------------------------------------------
    2006-05-11 03:40:05.32 Server      * Short Stack Dump
    2006-05-11 03:40:05.35 Server      7C815DEA Module(kernel32+00015DEA)
    2006-05-11 03:40:05.35 Server      02187744 Module(sqlservr+01187744)
    2006-05-11 03:40:05.35 Server      0218B600 Module(sqlservr+0118B600)
    2006-05-11 03:40:05.35 Server      0218B1AD Module(sqlservr+0118B1AD)
    2006-05-11 03:40:05.35 Server      023F4109 Module(sqlservr+013F4109)
    2006-05-11 03:40:05.35 Server      7C8595F7 Module(kernel32+000595F7)
    2006-05-11 03:40:05.39 Server      7C8440A1 Module(kernel32+000440A1)
    2006-05-11 03:40:05.39 Server      Stack Signature for the dump is 0xDF65101C


    Any ideas

    Thank you for your help,

    Best regards.


  • Fadi L

    Hi Tom,

    Are you upgrading from Express RTM to Express Advanced

    It would be usefull if you could check the SQL Error Log to see if there is additional information about why SQL failed to start. The log will be in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG for a default installation of SQL Express.

    Regards,

    Mike Wachal
    SQL Express team

    ----
    Please mark your thread as Answered when you get your solution.



  • jeromyk

    Hi everybody,

    I have the same problem as Queue256. The wizard fails to start the SqlServer service. I can't even start it manually.

    My config is : Windows Server 2003 SP1, .Net Framework 2.0, IIS. I'm trying to install SQL Server Express SP1.

    I have started the process over several times, after having uninstalled everything and having deleted the SQL server folders too. I'm using the admin account and default installation values.

    Best regards.


  • tht1guy

    Hi Tom,

    Have you resolved this issue yet If you're still having a problem please get back to me with the answer to my question so we can move forward.

    Regards,

    Mike Wachal
    SQL Express team

    ----
    Please mark your thread as Answered when you get your solution.



  • Jimi J

    Thank you, Mike !

    This kb article is fairly new (Article ID 919392 - June 2, 2006 - Rev. 1.0) and was not available when I first reported this problem. I prefer by far such an article, giving a clear and definite explanation, to an unconfirmed and unofficial hypothesis regarding an MS product found somewhere on the web.

    Have a nice day.

    Best regards.


  • == The SQL Server service failed to start ==