Link to home
Start Free TrialLog in
Avatar of golspie987
golspie987

asked on

Installing SQL server 2005 - failure error 29503

I am trying and failing to install the said software and am running out of ideas. The error is the standard "SQL server has failed to start error 29503"
I have retrieved the following from the log files.
----------------------------------------------------------------

Service MSSQL$SQLEXPRESS with parameters '-m
SqlSetup -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is
being started at Sat Oct 17 16:09:24 2009
Service failed unexpectedly (1067)
        Error Code: 0x8007042b (1067)
Windows Error Text: The process terminated unexpectedly.
  Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Sat Oct 25 08:47:19 2008
     Function Name: sqls::Service::Start
Source Line Number: 301



---- Context -----------------------------------------------


Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS



Error Code: 1067
MSI (s) (50!94) [16:09:36:546]: 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.
.

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.

--------------------------------------------------------------------
I have checked that the Domain register is in place, I have attempted to install as a local service rather than a network service and still no luck.
I am running Windows XP SP3 on an Intel dual core processor.
Does anyone have any ideas as to how to get round these problems?
Peter
Avatar of olivera1990
olivera1990

Try to search for Errorlog and open it up and see ., It might have more information
It should be Somewhere like this 'H:\Data Files\MSSQL.1\MSSQL\LOG\ERRORLOG'.
Avatar of golspie987

ASKER

Hi,I have checked the error log as you suggested and have found the following:


2009-10-18 18:35:35.82 Server      Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
      Nov 24 2008 13:01:59
      Copyright (c) 1988-2005 Microsoft Corporation
      Express Edition with Advanced Services on Windows NT 5.1 (Build 2600: Service Pack 3)

2009-10-18 18:35:35.85 Server      (c) 2005 Microsoft Corporation.
2009-10-18 18:35:35.85 Server      All rights reserved.
2009-10-18 18:35:35.85 Server      Server process ID is 3056.
2009-10-18 18:35:35.85 Server      Authentication mode is MIXED.
2009-10-18 18:35:35.85 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-10-18 18:35:35.85 Server      Registry startup parameters:
2009-10-18 18:35:35.85 Server             -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-10-18 18:35:35.85 Server             -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-10-18 18:35:35.85 Server             -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-10-18 18:35:35.85 Server      Command Line Startup Parameters:
2009-10-18 18:35:35.85 Server             -m SqlSetup
2009-10-18 18:35:35.85 Server             SqlSetup
2009-10-18 18:35:35.85 Server             -Q
2009-10-18 18:35:35.85 Server             -q SQL_Latin1_General_CP1_CI_AS
2009-10-18 18:35:35.85 Server             -T 4022
2009-10-18 18:35:35.85 Server             -T 3659
2009-10-18 18:35:35.85 Server             -T 3610
2009-10-18 18:35:35.85 Server             -T 4010
2009-10-18 18:35:35.88 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-10-18 18:35:35.88 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2009-10-18 18:35:36.31 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.
2009-10-18 18:35:36.34 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2009-10-18 18:35:36.34 spid5s      Warning ******************
2009-10-18 18:35:36.34 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2009-10-18 18:35:36.35 spid5s      Starting up database 'master'.
2009-10-18 18:35:36.43 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-10-18 18:35:36.49 spid5s      SQL Trace ID 1 was started by login "sa".
2009-10-18 18:35:36.51 spid5s      Starting up database 'mssqlsystemresource'.
2009-10-18 18:35:36.54 spid5s      The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2009-10-18 18:35:36.92 spid5s      Error: 15209, Severity: 16, State: 1.
2009-10-18 18:35:36.92 spid5s      An error occurred during encryption.
2009-10-18 18:35:36.92 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

I have Googled this error 15209 and am no clearer as to the solution. Anyone help?
Peter
Hi, This looks like an error which comes when the ratio of logical processors to physical sockets is not a power of 2. Here are some steps to workaround this problem:

Follow these steps before you install SQL Server 2005:
1.Copy the setup files of the release version of SQL Server 2005 to a folder in a local drive.

Note You must copy all the setup files that include the Servers folder and the Tools folder to a local drive.
2.Download the SQL Server 2005 SP2 or SP3 package, and then expand it on the local drive by using the /X parameter. For example, run the following command to expand the package:
SQLServer2005SP2-KB921896-x64-ENU.exe /X
3.Note the full paths to the new .msp files in the expanded update package. For example:
D:\temp\SP2\hotfixsql\files\sqlrun_sql.msp
4.At the command prompt, run the Setup.exe file from the release version by using the appropriate path to involve the new .msp file in the setup.

For example, the following command uses the update package to update the SQL Server Database Engine component to the service pack level:
D:\temp\Servers\setup.exe HOTFIXPATCH="D:\temp\SQL2005_12Procs\SP2\hotfixsql\files\sqlrun_sql.msp"
Note After you complete this step, the installation of SQL Server 2005 is in a configuration that is unsupported.
5.Apply the service pack package by running the hotfix.exe file in the expanded location. This step applies all service pack components and returns the installation of SQL Server 2005 to a supported state.
ASKER CERTIFIED SOLUTION
Avatar of golspie987
golspie987

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks Peter. Nice findings and that's really helpful. The solution that I have provided will work for the same error when the ratio of logical processors to physical sockets is not a power of 2.

Hope that helps!

Thnx,
Vj