Microsoft KB Archive/308766

= FIX: Enabling TCP/IP Through the Server Network Utility May Not Enable the Server to Listen on TCP/IP =

Article ID: 308766

Article Last Modified on 10/17/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q308766



BUG #: 354417 (SHILOH_BUGS)



SYMPTOMS
The Server Network Utility has two list boxes titled Disabled Protocols and Enabled Protocols.

If you move a protocol from the Disabled list to the Enabled list, click OK and then stop and restart the server, SQL Server does not enable the protocol on the server.

After you restart the server, you can confirm that TCP/IP is not enabled if you see the following error message in the SQL Server error log:

2001-10-30 16:58:25.00 server SQL server listening on Shared Memory, Named Pipes.

Note that the server is listening only on Shared Memory and Named Pipes and TCP/IP is not in the list.



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



WORKAROUND
To work around the problem, use the Server Network Utility and navigate to the properties of the newly enabled TCP/IP protocol and press OK in that dialog box.

For example, when you enable TCP/IP:
 * 1) Use the SQL Network Utility and click to select TCP/IP from the list of Disabled Protocols in the left pane.
 * 2) Click Enable. TCP/IP moves to the right pane and is now part of the Enabled Protocol list.
 * 3) Click to select TCP/IP in the right pane, and then click Properties.
 * 4) In the Properties dialog box, click OK to accept the default port settings.
 * 5) Click OK to close the Server Network Utility tool.
 * 6) Stop and restart the SQL Server instance for this protocol to go into effect.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Keywords: kbbug kbfix KB308766

-

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

© Microsoft Corporation. All rights reserved.