Cannot Install TCP/IP After Installing SQL Server

 Last reviewed: September 3, 1996
Article ID: Q128430
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

After you install SQL server and then run Control Panel to install TCP/IP, Connectivity Utilities is unavailable (grayed out), even though TCP/IP is not installed.

CAUSE

When you install SQL Server and choose to include the TCP/IP connectivity on a computer running Windows NT without TCP/IP installed, a message is displayed that asks you if you want to proceed. If you select Yes, false TCP/IP and Parameter keys are created in the following registry key under the HKEY_LOCAL_MACHINE subtree: 

   \SYSTEM\CURRENTCONTROLSET\SERVICES
When you attempt to install TCP/IP, Windows NT finds the registry entries, and believes that TCP/IP is already installed, and installs utilities, but not the protocol.

WORKAROUND

To work around this problem, delete the registry keys created by SQL Server, install TCP/IP, and then reinstall SQL Server.

KBCategory: kbnetwork kbinterop
KBSubcategory: nttcp NTSrvWkst
Additional reference words: prodnt

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 3, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.