I'm experiencing a problem installing SQL Server Express 2005. I thought I had the same problem as Tom from a recent thread but his error file is quite different from mine. The Visual Basic Express
package properly installed everything except SQL Server. I've run
it many times, but the service fails
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 event
viewer shows this error:
Product: Microsoft SQL Server 2005 Express Edition -- Error 29503. 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."
The error is (1067) The process terminated unexpectedly.
The error log is:
2006-05-02 16:10:58.07 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: Service Pack 2)
2006-05-02 16:10:58.08 Server (c) 2005 Microsoft Corporation.
2006-05-02 16:10:58.08 Server All rights reserved.
2006-05-02 16:10:58.09 Server Server process ID is 816.
2006-05-02 16:10:58.09 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-05-02 16:10:58.09 Server This instance of SQL Server last reported using a process ID of 2748 at 5/2/2006 4:10:29 PM (local) 5/2/2006 9:10:29 PM (UTC). This is an informational message only; no user action is required.
2006-05-02 16:10:58.15 Server Registry startup parameters:
2006-05-02 16:10:58.15 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-05-02 16:10:58.15 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-05-02 16:10:58.16 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-05-02 16:10:58.28 Server Error: 17311, Severity: 16, State: 1.
2006-05-02 16:10:58.28 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-02 16:10:58.30 Server Using 'dbghelp.dll' version '4.0.5'
2006-05-02 16:10:58.36 Server **Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
2006-05-02 16:10:58.36 Server ***Stack Dump being sent to c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0005.txt
2006-05-02 16:10:58.36 Server * *******************************************************************************
2006-05-02 16:10:58.36 Server *
2006-05-02 16:10:58.36 Server * BEGIN STACK DUMP:
2006-05-02 16:10:58.36 Server * 05/02/06 16:10:58 spid 0
2006-05-02 16:10:58.36 Server *
2006-05-02 16:10:58.36 Server * ex_handle_except encountered exception C000001D - Server terminating
2006-05-02 16:10:58.36 Server *
2006-05-02 16:10:58.36 Server *
2006-05-02 16:10:58.36 Server * MODULE BASE END SIZE
2006-05-02 16:10:58.36 Server * sqlservr 01000000 02BCEFFF 01bcf000
2006-05-02 16:10:58.36 Server * ntdll 7C900000 7C9AFFFF 000b0000
2006-05-02 16:10:58.36 Server * kernel32 7C800000 7C8F3FFF 000f4000
2006-05-02 16:10:58.36 Server * MSVCR80 78130000 781CAFFF 0009b000
2006-05-02 16:10:58.36 Server * msvcrt 77C10000 77C67FFF 00058000
2006-05-02 16:10:58.37 Server * MSVCP80 7C420000 7C4A6FFF 00087000
2006-05-02 16:10:58.37 Server * ADVAPI32 77DD0000 77E6AFFF 0009b000
2006-05-02 16:10:58.37 Server * RPCRT4 77E70000 77F00FFF 00091000
2006-05-02 16:10:58.37 Server * USER32 77D40000 77DCFFFF 00090000
2006-05-02 16:10:58.37 Server * GDI32 77F10000 77F56FFF 00047000
2006-05-02 16:10:58.37 Server * CRYPT32 77A80000 77B13FFF 00094000
2006-05-02 16:10:58.37 Server * MSASN1 77B20000 77B31FFF 00012000
2006-05-02 16:10:58.37 Server * Secur32 77FE0000 77FF0FFF 00011000
2006-05-02 16:10:58.37 Server * MSWSOCK 71A50000 71A8EFFF 0003f000
2006-05-02 16:10:58.37 Server * WS2_32 71AB0000 71AC6FFF 00017000
2006-05-02 16:10:58.37 Server * WS2HELP 71AA0000 71AA7FFF 00008000
2006-05-02 16:10:58.37 Server * USERENV 769C0000 76A72FFF 000b3000
2006-05-02 16:10:58.37 Server * opends60 333E0000 333E6FFF 00007000
2006-05-02 16:10:58.37 Server * NETAPI32 5B860000 5B8B3FFF 00054000
2006-05-02 16:10:58.37 Server * SHELL32 7C9C0000 7D1D4FFF 00815000
2006-05-02 16:10:58.37 Server * SHLWAPI 77F60000 77FD5FFF 00076000
2006-05-02 16:10:58.37 Server * OCMAPIHK 10000000 1000CFFF 0000d000
2006-05-02 16:10:58.37 Server * comctl32 773D0000 774D1FFF 00102000
2006-05-02 16:10:58.37 Server * comctl32 5D090000 5D126FFF 00097000
2006-05-02 16:10:58.37 Server * psapi 76BF0000 76BFAFFF 0000b000
2006-05-02 16:10:58.37 Server * instapi 48060000 48069FFF 0000a000
2006-05-02 16:10:58.37 Server * sqlevn70 4F610000 4F7A3FFF 00194000
2006-05-02 16:10:58.37 Server * dbghelp 03000000 03112FFF 00113000
2006-05-02 16:10:58.37 Server *
2006-05-02 16:10:58.37 Server * Edi: 0075C528: 000E1068 00000000 00000000 00000000 0075C548 00000000
2006-05-02 16:10:58.37 Server * Esi: 00000000:
2006-05-02 16:10:58.37 Server * Eax: 0075C40C: 000042AC 00000000 00000000 7C81EB33 00000000 0000000C
2006-05-02 16:10:58.37 Server * Ebx: 0000003F:
2006-05-02 16:10:58.38 Server * Ecx: 0075CA7C: 00000000 0001001F 00000000 00000000 00000000 00000000
2006-05-02 16:10:58.38 Server * Edx: 0000003D:
2006-05-02 16:10:58.38 Server * Eip: 7C81EB33: 10C2C95E 0FFF8500 FED0E68E FC558BFF 0F0C5589 7D8B16B7
2006-05-02 16:10:58.38 Server * Ebp: 0075C45C: 0075C4A0 02187744 000042AC 00000000 00000000 00000000
2006-05-02 16:10:58.38 Server * SegCs: 0000001B:
2006-05-02 16:10:58.38 Server * EFlags: 00080246:
2006-05-02 16:10:58.38 Server * Esp: 0075C408: 00000000 000042AC 00000000 00000000 7C81EB33 00000000
2006-05-02 16:10:58.38 Server * SegSs: 00000023:
2006-05-02 16:10:58.38 Server * *******************************************************************************
2006-05-02 16:10:58.38 Server * -------------------------------------------------------------------------------
2006-05-02 16:10:58.38 Server * Short Stack Dump
2006-05-02 16:10:58.50 Server 7C81EB33 Module(kernel32+0001EB33)
2006-05-02 16:10:58.50 Server 02187744 Module(sqlservr+01187744)
2006-05-02 16:10:58.51 Server 0218B600 Module(sqlservr+0118B600)
2006-05-02 16:10:58.51 Server 0218B1AD Module(sqlservr+0118B1AD)
2006-05-02 16:10:58.51 Server 023F4109 Module(sqlservr+013F4109)
2006-05-02 16:10:58.51 Server 7C862CD3 Module(kernel32+00062CD3)
2006-05-02 16:10:58.57 Server 7C83AA6B Module(kernel32+0003AA6B)
2006-05-02 16:10:58.60 Server Stack Signature for the dump is 0xDF483EDE
2006-05-02 16:10:59.33 Server External dump process return code 0x20000001.
External dump process returned no errors.
Any thoughts Thanks.
SQL Server Express fails to install
Hot Topic
- Description for Calculated Measures?
- Incremental cube processing
- Updating a text field with a sub-query
- FOR XML in web page- OK what's next
- How connect SQL server 2000 with c#.net .....?
- Can't start SSIS
- Poison Message Sample in BOL
- Can't uninstall Reporting Services
- getting a double line as underline
- Complex Quieries - Reporting Services
SQL Server
- Random variable modeling using T-SQL
- How do you create Users?
- Mssearch.exe consuming High CPU over extended time period
- Where is the old Enterprise Manager :(
- not able to login in other computers!
- Thank u very much
- Error updating data in table that uses a trigger?
- Looping over files not available in my ssis
- sorting the packages in the solution explorer window
- SQL Server pricing
SQL Server Express fails to install
LaurieCSI
korggy
Kumar Puran
Rhapsy
looks similar to bug FDBK16177.
I am having the same problem on an older box I am using for testing. I guess it is because of the old K6 - 450 processor
rasoul
I just wanted to confirm that if you have a CPU that doesn't support the full PIII instruction set, specifically prefetch, you will get the error being discussed here. This information is now documented in a KB article.
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
----
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
joshlarsen
Hello,
As mentionned here https://forums.microsoft.com/MSDN/ShowPost.aspx PostID=377860&SiteID=1 , I have the same problem as you, with the same error.
dflAdam, I also have a K6-III, but everything else works just fine : Windows Server 2003 SP1, .Net 2.0, aso. I have found this information : http://channel9.msdn.com/ShowPost.aspx PostID=28640 but it is not confirmed ba Microsoft.
Note that it also exists a free Oracle Express Edition, with the same limitations as SQL Server 2005 Express Edition. .Net 2.0 supports access to this database. Maybe it could be useful to test it if is confirmed by Microsoft that SQL Server 2005 Express Edition won't work on a K6-III processor.
Best regards.