2005 April CTP Install Failure

SQL Server Setup could not conect to the database service for server configuration. The error was: [Microsoft}{SQL Native Client} Named Pipes Provider: Could not open a connection to SQL Server [2]. 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 File" in SQL Server Books Online.

That is the error when attempting to install to W2003 running as a VPC2004 guest OS. The framework and VS Beta 2 are installed and functional.

During setup I recall no configuration option that required the use of Named Pipes. For the most part I used all default settings during install.

The following is all I could find in the log...

MSI (s) (D8:9C) [15:19:14:137]: Note: 1: 1708
MSI (s) (D8:9C) [15:19:14:137]: Product: Microsoft SQL Server 2005 CTP -- Installation failed.
The error message also implies an instance of SQL Server could not be found when the install apparently attempted to make a connection but the reference to the number 2 in brackets is confusing, e.g. [2].

When SQL Native Client copies over the legacy registry hive it doesn't enable shared memory. During installation of SQL Server 2005 the SQL Setup program uses the SQL Native Client to connect to the newly installed database instance using shared memory. Since shared memory is not enabled setup fails to connect.

Work Around
When setup encounters this error the error dialog contains a "retry" button.
1) Open Regedit
2) Navigate to \HKEY_LOCAL_MACHINE\SOFTWARE\Microsost\MSSQLServer\Client\SNI9.0
3) Open the key ProtocolOrder, you should see the values tcp and np
4) Add "sm" to the begining to the reg key value. The reg key should look like this after editing:
sm
tcp
np
5) Save the changes to the reg key
6) Go back to SQL setup and click "Retry". Setup should finish installing

Dan
SQL Server Setup Team
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Dan Jones MSFT wrote:

When SQL Native Client copies over the legacy registry hive it doesn't enable shared memory...

Work Around

When setup encounters this error the error dialog contains a "retry" button.
1) Open Regedit
2) Navigate to \HKEY_LOCAL_MACHINE\SOFTWARE\Microsost\MSSQLServer\Client\SNI9.0
3) Open the key ProtocolOrder, you should see the values tcp and np
4) Add "sm" to the begining to the reg key value. The reg key should look like this after editing:
sm
tcp
np
5) Save the changes to the reg key
6) Go back to SQL setup and click "Retry". Setup should finish installing

...

Thanks Dan. I'll give that a try this evening...

|||

clintonG wrote:

Dan Jones MSFT wrote:

When SQL Native Client copies over the legacy registry hive it doesn't enable shared memory...

Work Around
...

Thanks Dan. I'll give that a try this evening...

No joy yet. The registry hack enabled the install to proceed but now chokes when trying to install "Workstation Components..." with the following...

Error reading from file: F:\My DOwnloads\~Application Vendors\Microsoft\SQL Server\SQL Server 2005 CTP - April 2005 - Developer Edition\SQLDEV\Setup\Program Files\Microsoft SQL Server\90\Tools\Profiler\TraceDefinitions\1033\Microsoft Data Transformation Services TraceDescriptions 9.0.0.xml. Verify that the file exists and that you can access it.|||Ok, you hit another issue. You're running into an Windows Installer issue with the depth of the path. Windows Installer only supports installing from paths up to 255 characters. You path is 262. I suggest you create a share to it that shortens the path.

Dan|||

Dan Jones MSFT wrote:

Ok, you hit another issue. You're running into an Windows Installer issue with the depth of the path. Windows Installer only supports installing from paths up to 255 characters. You path is 262. I suggest you create a share to it that shortens the path.

Dan

As it turns out I moved the entire SQLDEV directory from the network share and put it into the root of the drive where I was attempting to install. The install then proceeded without a single problem of any kind. Thanks for hanging in there with me Dan I had forgotten about that little 'gotcha.'

|||That's not actually the cause of this error (I've just come across it too..) the real problem is that the file exists but MS had missed the .xml extension on this particular file. Locate it and add .xml to the end and the install works okay|||Changing the registry key was not easy as you mentioned. When I added sm in front of tcp np, I kept getting a bunch of sqaure box characters. How do I enter them properly.
Thank you.