SQL Server 2005 Setup could not connect to the database service for server configuration.
Hi,
I am trying to install SQL Express 2005 (SP3 included in MSI). This is a clean install and no previous versions of SQL have ever been installed. The error I am getting is:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
I have tried Windows mode, mixed mode with and without a passsword for the sa account but still the same error.
Please can anyone help - thanks.
Here is the rror log:
2010-03-23 16:00:32.71 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 on Windows NT 5.2 (Build 3790: Service Pack 2)
2010-03-23 16:00:32.74 Server (c) 2005 Microsoft Corporation.
2010-03-23 16:00:32.74 Server All rights reserved.
2010-03-23 16:00:32.74 Server Server process ID is 32312.
2010-03-23 16:00:32.74 Server Authentication mode is MIXED.
2010-03-23 16:00:32.74 Server Logging SQL Server messages in file 'c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\E
2010-03-23 16:00:32.75 Server Registry startup parameters:
2010-03-23 16:00:32.77 Server -d c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\
2010-03-23 16:00:32.77 Server -e c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\E
2010-03-23 16:00:32.77 Server -l c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\
2010-03-23 16:00:32.77 Server Command Line Startup Parameters:
2010-03-23 16:00:32.77 Server -m SqlSetup
2010-03-23 16:00:32.77 Server SqlSetup
2010-03-23 16:00:32.77 Server -Q
2010-03-23 16:00:32.77 Server -q SQL_Latin1_General_CP1_CI_
2010-03-23 16:00:32.77 Server -T 4022
2010-03-23 16:00:32.77 Server -T 3659
2010-03-23 16:00:32.77 Server -T 3610
2010-03-23 16:00:32.77 Server -T 4010
2010-03-23 16:00:32.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-03-23 16:00:32.79 Server Detected 8 CPUs. This is an informational message; no user action is required.
2010-03-23 16:00:33.11 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.
2010-03-23 16:00:33.60 Server Database Mirroring Transport is disabled in the endpoint configuration.
2010-03-23 16:00:33.65 spid5s Warning ******************
2010-03-23 16:00:33.67 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2010-03-23 16:00:33.73 spid5s Starting up database 'master'.
2010-03-23 16:00:34.10 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2010-03-23 16:00:34.31 spid5s SQL Trace ID 1 was started by login "sa".
2010-03-23 16:00:34.40 spid5s Starting up database 'mssqlsystemresource'.
2010-03-23 16:00:34.44 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2010-03-23 16:00:34.89 spid5s Password policy update was successful.
2010-03-23 16:00:34.92 spid7s Starting up database 'model'.
2010-03-23 16:00:34.92 spid5s Server name is '109-104-81-154\SQLEXPRESS
2010-03-23 16:00:34.92 spid5s Starting up database 'msdb'.
2010-03-23 16:00:35.30 Server A self-generated certificate was successfully loaded for encryption.
2010-03-23 16:00:35.30 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRE
2010-03-23 16:00:35.31 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.
2010-03-23 16:00:35.36 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2010-03-23 16:00:35.71 spid7s Clearing tempdb database.
2010-03-23 16:00:35.95 spid7s Starting up database 'tempdb'.
2010-03-23 16:00:36.00 spid5s Recovery is complete. This is an informational message only. No user action is required.
2010-03-23 16:00:36.14 Logon Error: 18456, Severity: 14, State: 10.
2010-03-23 16:00:36.14 Logon Login failed for user 'sa'. [CLIENT: <local machine>]
2010-03-23 16:00:38.80 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2010-03-23 16:00:38.80 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
I am trying to install SQL Express 2005 (SP3 included in MSI). This is a clean install and no previous versions of SQL have ever been installed. The error I am getting is:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
I have tried Windows mode, mixed mode with and without a passsword for the sa account but still the same error.
Please can anyone help - thanks.
Here is the rror log:
2010-03-23 16:00:32.71 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 on Windows NT 5.2 (Build 3790: Service Pack 2)
2010-03-23 16:00:32.74 Server (c) 2005 Microsoft Corporation.
2010-03-23 16:00:32.74 Server All rights reserved.
2010-03-23 16:00:32.74 Server Server process ID is 32312.
2010-03-23 16:00:32.74 Server Authentication mode is MIXED.
2010-03-23 16:00:32.74 Server Logging SQL Server messages in file 'c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\E
2010-03-23 16:00:32.75 Server Registry startup parameters:
2010-03-23 16:00:32.77 Server -d c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\
2010-03-23 16:00:32.77 Server -e c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\E
2010-03-23 16:00:32.77 Server -l c:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\
2010-03-23 16:00:32.77 Server Command Line Startup Parameters:
2010-03-23 16:00:32.77 Server -m SqlSetup
2010-03-23 16:00:32.77 Server SqlSetup
2010-03-23 16:00:32.77 Server -Q
2010-03-23 16:00:32.77 Server -q SQL_Latin1_General_CP1_CI_
2010-03-23 16:00:32.77 Server -T 4022
2010-03-23 16:00:32.77 Server -T 3659
2010-03-23 16:00:32.77 Server -T 3610
2010-03-23 16:00:32.77 Server -T 4010
2010-03-23 16:00:32.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-03-23 16:00:32.79 Server Detected 8 CPUs. This is an informational message; no user action is required.
2010-03-23 16:00:33.11 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.
2010-03-23 16:00:33.60 Server Database Mirroring Transport is disabled in the endpoint configuration.
2010-03-23 16:00:33.65 spid5s Warning ******************
2010-03-23 16:00:33.67 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2010-03-23 16:00:33.73 spid5s Starting up database 'master'.
2010-03-23 16:00:34.10 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2010-03-23 16:00:34.31 spid5s SQL Trace ID 1 was started by login "sa".
2010-03-23 16:00:34.40 spid5s Starting up database 'mssqlsystemresource'.
2010-03-23 16:00:34.44 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2010-03-23 16:00:34.89 spid5s Password policy update was successful.
2010-03-23 16:00:34.92 spid7s Starting up database 'model'.
2010-03-23 16:00:34.92 spid5s Server name is '109-104-81-154\SQLEXPRESS
2010-03-23 16:00:34.92 spid5s Starting up database 'msdb'.
2010-03-23 16:00:35.30 Server A self-generated certificate was successfully loaded for encryption.
2010-03-23 16:00:35.30 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRE
2010-03-23 16:00:35.31 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.
2010-03-23 16:00:35.36 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2010-03-23 16:00:35.71 spid7s Clearing tempdb database.
2010-03-23 16:00:35.95 spid7s Starting up database 'tempdb'.
2010-03-23 16:00:36.00 spid5s Recovery is complete. This is an informational message only. No user action is required.
2010-03-23 16:00:36.14 Logon Error: 18456, Severity: 14, State: 10.
2010-03-23 16:00:36.14 Logon Login failed for user 'sa'. [CLIENT: <local machine>]
2010-03-23 16:00:38.80 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2010-03-23 16:00:38.80 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
ASKER
Hi,
I have done as you suggested but still the same issue. I have attached a screen shot of the actual error and the point at which it goes wrong.
SQL-Error.jpg
I have done as you suggested but still the same issue. I have attached a screen shot of the actual error and the point at which it goes wrong.
SQL-Error.jpg
what OS? turn on windws firewall?
ASKER
Hi,
Server 2003 Enterprise SP2 64-bit. No firewall.
Server 2003 Enterprise SP2 64-bit. No firewall.
Do you have the pre-requisites installed in your machine..
And are you trying to install 32 or 64 version of SQL server 2005..
And are you trying to install 32 or 64 version of SQL server 2005..
ASKER
Hi,
I have all the pre-requisites installed.
I downloaded the 64-bit installation MSI package.
I have all the pre-requisites installed.
I downloaded the 64-bit installation MSI package.
What other applications do you have installed? Just because you didn't install SQL Server express does not mean that some other application didn't install it first.
Heard similar issue before with the installation package from someone.
Can you try installing the one in the link below:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3181842a-4090-4431-acdd-9a1c832e65a6&displaylang=en
Can you try installing the one in the link below:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3181842a-4090-4431-acdd-9a1c832e65a6&displaylang=en
ASKER
Hi,
bhess1: The server is a clean build with nothing but Server 2003 SP2 installed and the .NET Framework versions 2 & 3.5 + SP's.
rrjegan17: Downloaded what you suggested but still same issue. BTW - I did uninstall everything, removed any residule directories and cleaned the registy. Plus rebooted the server before re-installing.
bhess1: The server is a clean build with nothing but Server 2003 SP2 installed and the .NET Framework versions 2 & 3.5 + SP's.
rrjegan17: Downloaded what you suggested but still same issue. BTW - I did uninstall everything, removed any residule directories and cleaned the registy. Plus rebooted the server before re-installing.
Is there any pre-existing issues or any configuration issues existing in your server..
Have you tried installing Evaluation edition of SQL Server once and find whether you are obtaining the same error or not..
ASKER
Hi,
Sorry for the delay in replying but I got the server completly reimaged. Unfortunatlely I am still unable to install SQL 2005. I also tried SQL 2008 and this also failed.
There is obviously something very wrong with the server image. We rent this server and I have no control over the image, so all I can do is ask the ISP to provide a different image and try again.
Sorry for the delay in replying but I got the server completly reimaged. Unfortunatlely I am still unable to install SQL 2005. I also tried SQL 2008 and this also failed.
There is obviously something very wrong with the server image. We rent this server and I have no control over the image, so all I can do is ask the ISP to provide a different image and try again.
Suspect something with the image..
Try installing SQL Server 2005 or 2008 in some other machine installed through some other image or Installation Disk and check it out once..
Try installing SQL Server 2005 or 2008 in some other machine installed through some other image or Installation Disk and check it out once..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
I went back to the ISP with reference to the MSDN article you pointed me to and asked the question was it failing because our server is a VPS in a server farm. The ISP then offered to install SQL 2008 Express x64 for us and it now works.
I have asked them for details of what they did, as they said that they had to install it using command line switches. I think it would be nice to put this information in to this log for those that have the same problem. Hopefully, they will pass on that information.
I went back to the ISP with reference to the MSDN article you pointed me to and asked the question was it failing because our server is a VPS in a server farm. The ISP then offered to install SQL 2008 Express x64 for us and it now works.
I have asked them for details of what they did, as they said that they had to install it using command line switches. I think it would be nice to put this information in to this log for those that have the same problem. Hopefully, they will pass on that information.
ASKER
Thank you for sticking with it. I will update this log if I ever get an answer back from the ISP.
Welcome.. And I usually try to stay till the question is closed..
If command line installation worked, then this should be the appropriate article for that:
http://msdn.microsoft.com/en-us/library/ms144259%28SQL.90%29.aspx
If you get any additional info from your ISP, then post that here..
If command line installation worked, then this should be the appropriate article for that:
http://msdn.microsoft.com/en-us/library/ms144259%28SQL.90%29.aspx
If you get any additional info from your ISP, then post that here..
ASKER
Hi,
Here is how the ISP installed SQL on the VPS
setup.exe /action=Install /INSTALLSHAREDWOWDIR="C:\P
Here is how the ISP installed SQL on the VPS
setup.exe /action=Install /INSTALLSHAREDWOWDIR="C:\P
Thanks for sharing it out here..
So you don't have SQL Server installed in your machine right..
If you have partial or incomplete installation, then uninstall it and then provide strong password for sa and try it out once..