Microsoft KB Archive/306865

= BUG: SQL Server May Not Listen on TCP/IP Sockets When TCP/IP is the Only Protocol =

Article ID: 306865

Article Last Modified on 10/3/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q306865



BUG #: 353545 (SHILOH_BUGS)



SYMPTOMS
In a SQL Server 2000 custom installation, if TCP/IP is the only selected protocol and all other protocols are disabled, SQL Server may not initialize and listen on TCP/IP sockets. The Server Network Utility shows that it is listening only on TCP/IP port 1433 even though it is not. Clients may fail to connect and the following error messages may occur:

Connection failed: SQL State: '01000' SQL Server Error: 11004 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect). Connection Failed: SQL State: '08001' SQL Server Error: 6 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.

Unable to connect to server 'servername': Server: Msg 6, Level 16 state 1. [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.

[TCP/IP Sockets]Specified SQL server not found. [TCP/IP Sockets]ConnectionOpen (Connect).

Note that the preceding error message can exist for TCP/IP connectivity problems other than this specific situation. To identify if SQL Server is not listening on TCP/IP, check to see if the value for TcpPort in the following registry key is incorrectly set to blank or empty:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\ [Instance Name]\MSSQLServer\SuperSocketNetLib\Tcp\REG_SZ TcpPort=



WORKAROUND
To work around this problem, follow these steps:  Start Registry Editor (Regedt32.exe). Locate the TcpPort value in the following key in the registry:

Named instance:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\[InstanceName]\MSSQLServer\SuperSocketNetLib\Tcp\TcpPort

Default instance:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\TCP\TcpPort

 On the Edit menu, click String. Enter either of the following values:  Type the port number you want. -or-

 Enter a value of 0 to have SQL Server dynamically detect and assign a port the next time SQL Server starts. </li> Click OK.</li> Quit Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbpending KB306865

-

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

© Microsoft Corporation. All rights reserved.