Microsoft KB Archive/317261

= FIX: Setup to Named Instance of SQL Server 2000 Fails with General Network Error =

Article ID: 317261

Article Last Modified on 10/16/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q317261



BUG #: 355349 (SHILOH_BUGS)



SYMPTOMS
When you install SQL Server 2000 as a named instance and create an alias for that instance (which can be seen on the Alias tab in the SQL Server Client Network Utility), the installation of SP1 on that instance may sometimes fail with the following error message:

Setup failed to configure the server. Refer to the server error logs and C:\WINNT\sqlstp.log for more information.

The following error message is also seen:

Error running script: sp1_serv_uni.sql (1)

When the error occurs, the following error message is logged in the Sp1_serv_uni.out file for a SQL Server 2000 SP1 installation, and in Sqlsp.log file for a SQL Server 2000 installation.

When setting an alias as Named Pipe:

ConnectionRead (WrapperRead)

When setting an alias as TCP/IP socket:

ConnectionRead (recv)



CAUSE
SQL Server uses Cnfgsrv.exe when the setup attempts to configure the SQL Server computer. The Cnfgsrv.exe file forces SQL Server to start and listen only on Local Shared Memory (LPC). However, when you have an alias, Cnfgsrv.exe forces Netlib to try to use the protocol defined by that alias, even if the protocol is not LPC. Use of a protocol other than LPC causes the failure to occur.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

Before the release of Microsoft SQL Server 2000 SP2, to resolve the problem, you must delete the alias name before you attempt the installation. For information on how to delete an alias, please refer to the &quot;Client Network Utility&quot; topic in SQL Server 2000 Books Online.



STATUS
Microsoft has confirmed that this is a problem in SQL Server 2000 and SQL Server Service Pack 1.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Keywords: kbbug kbfix KB317261

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.