Having had no luck getting prior versions of Sql Server Express to install on Vista RC2. I was hoping that SP2 would install with no problems however I'm still getting the same error as before and can't find any working solution to this anywhere on the web.
The actual error I'm getting occurs when the install tries to start the SQL Server service and connect. I get
TITLE: Microsoft SQL Server 2005 Setup
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
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.
This error apparently also occurs on other platforms than Vista. Any ideas how to get past this? The Vista install is still pretty much a clean install.
TIA Adrian Heath
Hi Adrian,
The most obvious question is, "did you check the setup logs?" as per the instructions in the message? The setup logs will help track down the root cause of the error. I've installed SSE on many different builds of Vista without problems, so I know it's possible.
Mike
|||I did but the final entry basically says the same as the displayed error and it was hard to figure out if any other part of the preceeding 5Mb of log was relevant. The complete log entry is as follows. If you have any suggestions what else to look for in the log please let me know.
TIA Adrian Heath
Error Code: 233
MSI (s) (C0!C4) [22:58:58:097]: Product: Microsoft SQL Server 2005 Express Edition -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
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.
Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
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.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Fri Nov 17 22:58:58 2006
Service MSSQL$SQLEXPRESS with parameters '-m SqlSetup -Q -qLatin1_General_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Fri Nov 17 22:58:58 2006
Attempt to start service when it is already running
SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to accept client connections
Service MSSQL$SQLEXPRESS started at Fri Nov 17 22:58:58 2006
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=08001, level=-1, state=-1, native_error=233, msg=[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
sqlstate=08001, level=-1, state=-1, native_error=233, msg=[Microsoft][SQL Native Client]Client unable to establish connection
Error Code: 0x800700e9 (233)
Windows Error Text: No process is on the other end of the pipe.
Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Wed Aug 2 16:21:01 2006
Function Name: OdbcConnection::connect@.connect
Source Line Number: 148
- Context --
Connecting to SQL Server
ExecuteSqlCommands
Originial error was 800700e9 (233)
Do_sqlScript
SqlScriptHlpr
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=197758&SiteID=1
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||
Thanks
SS Express is now installed
I followed the instructions for removing certificates from here
http://support.microsoft.com/default.aspx/kb/309398/
(mentioned near the bottom of the link suggested above) and the install completed. I'm not sure what the two certificates were from, I guess they are Vista default certificates but if so why have more people not reported this problem?
Oh well it's working now
Thanks again for the help
Adrian Heath
No comments:
Post a Comment