Microsoft KB Archive/827204

= BUG: You may not be able to connect to an instance of Microsoft SQL Server 2000 Desktop Engine SP3a after you enable the server network libraries =

Article ID: 827204

Article Last Modified on 4/18/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Desktop Engine

-



Bug #: 469996 (SQL Server 8.0)



SYMPTOMS
When you try to connect to an instance of Microsoft SQL Server 2000 Desktop Engine Service Pack 3a (also known as MSDE 2000 SP3a) you may not be able to connect to the instances successfully, and you may receive the following error message:

[DBMSLPCN]SQL Server does not exist or access denied.

[DBMSLPCN]ConnectionOpen (Connect).

This problem may occur when you try to connect to an instance of MSDE 2000 SP3a after you enable the TCP/IP server network library or the Named Pipes server network library for the instance by using the Server Network Utility from SQL Server Enterprise Manager.

This problem may also occur for an instance of Microsoft SQL Server 2000 that was upgraded from MSDE 2000 SP3a.



WORKAROUND
To work around this problem, follow these steps:
 * 1) Disable the server network libraries.
 * 2) Start the Server Network Utility from the command line and use the Server Network Utility to enable the required server network libraries.

Note Do not use the Server Network Utility from SQL Server Enterprise Manager to enable the server network libraries.

To start the Server Network Utility from the command line and to enable the server network libraries by using the Server Network Utility, follow these steps:

To enable the TCP/IP server network library

 * 1) Click Start, and then click Run.
 * 2) In the Run dialog box, type Svrnetcn.exe in the Open box, and then click OK.

Note By default, the Svrnetcn.exe file is available in the following folder:

 /Program Files/Microsoft SQL Server/80/Tools/BINN
 * 1) Click OK.
 * 2) In the Server Network Utility dialog box, click the General tab.
 * 3) Select your instance of MSDE 2000 SP3a or SQL Server 2000 from the Instance(s) on this server list.
 * 4) In the Disabled Protocols list box, select TCP/IP, and then click Enable.
 * 5) In the Enabled Protocols list box, select TCP/IP, and then click Properties.
 * 6) In the  - TCP/IP dialog box, type 0 in the Default Port box, and then click OK.
 * 7) In the Server Network Utility dialog box, click OK.

Note You may receive a message that states that the changes made will be saved but the changes will take effect only after you restart the SQL Server service. In the Server Network Utility message box, click OK.
 * 1) Restart your instance of MSDE 2000 SP3a, or your instance of SQL Server 2000.

To enable the Named Pipes server network library

 * 1) Click Start, and then click Run.
 * 2) In the Run dialog box, type Svrnetcn.exe in the Open box, and then click OK.

Note By default, the Svrnetcn.exe file is available in the following folder:

 /Program Files/Microsoft SQL Server/80/Tools/BINN
 * 1) In the Server Network Utility dialog box, click the General tab.
 * 2) Select your instance of MSDE 2000 SP3a, or your instance of SQL Server 2000 from the Instance(s) on this server list.
 * 3) In the Disabled Protocols list box, select Named Pipes, click Enable, and then click OK.

Note You may receive a message that states that the changes made will be saved but the changes will take effect only after you restart the SQL Server service. In the Server Network Utility message box, click OK.
 * 1) Restart the SQL Server service of the instance of MSDE 2000 SP3a, or the instance of SQL Server 2000.



MORE INFORMATION
When you disable the network protocols for an instance of MSDE 2000 SP3a, and you then upgrade the instance to SQL Server 2000, the network protocols of the upgraded instance of SQL Server may also be disabled. You can use the Server Network Utility to enable or to disable the network protocols of the upgraded instance of SQL Server.

However, if you enable the TCP/IP protocol and the Named Pipes protocol and you then set the TCP/IP server network library properties by using the Server Network Utility in SQL Server Enterprise Manager, attempts to connect to the instance of SQL Server may fail.

Steps to reproduce the behavior
 Install a named instance of MSDE 2000 SP3a with the DISABLENETWORKPROTOCOLS switch set to 1. To do so, follow these steps:  Open a command prompt.  Move to the MSDE 2000 SP3a installation folder, and then run the following command at the command prompt: setup /i  INSTANCENAME= SAPWD=sa DISABLENETWORKPROTOCOLS=1 /l*v c:\msdelog.txt Note Replace  and   with the name of your SQL Server and the name of the Windows Installer Package file path.   In SQL Server Enterprise Manager, register your instance of MSDE 2000 SP3a.</li> In the SQL Server Enterprise Manager window, locate and then right-click your instance of MSDE 2000 SP3a, and then click Properties.</li> In the SQL Server Properties (Configure) - <Instance Name> dialog box, click Network Configuration.</li> In the Server Network Utility dialog box, click the General tab.</li> In the Disabled Protocols list box, select TCP/IP, and then click Enable.</li> In the Disabled Protocols list box, select Named Pipes, and then click Enable.</li> In the Enabled Protocols list box, select TCP/IP, and then click Properties.</li> In the <Server Name> - TCP/IP dialog box, type 0 in the Default Port text box, and then click OK.</li> In the Server Network Utility dialog box, click OK.

Note You may receive a message that states that the changes made will be saved but the changes will take effect only after you restart the SQL Server service. In the Server Network Utility message box, click OK.</li> Restart the instance of MSDE 2000 SP3a.</li> Open Registry Editor, and then verify whether the value of the following registry key is empty:

</li> Connect to the instance of MSDE 2000 SP3a by using the osql utility. To do so, follow these steps:

If your instance of MSDE 2000 SP3a is running on the local computer, open a command prompt, and then run the following code:

osql -E -S (local)\[InstanceName]

If your instance of MSDE 2000 SP3a is running on a remote computer, open a command prompt, and then run the following code:

osql -E -S [Server]\[InstanceName]

Note You may notice that the connection attempts to your instance of MSDE 2000 SP3a fail, and you receive the error message that is mentioned in the &quot;Symptoms&quot; section.</li></ol>

<div class="references_section">