Unable to Connect to SQL Server If Default Protocol Is Changed

 Last reviewed: April 15, 1997
Article ID: Q133250

The information in this article applies to:
  • Microsoft Systems Management Server versions 1.0, 1.1, and 1.2
  • Microsoft SQL Server versions 4.21a, 6.0, and 6.5

SYMPTOMS

When you change the default network protocol in the SQL Client Configuration Utility, one of the following error messages appears in the SQL Server Administrator or Systems Management Server Administrator program:

  • Unable to connect: SQL Server is unavailable or does not exist. Specified SQL Server not found.
  • Couldn't connect to server <server name>.

Additionally, after changing the default network protocol, Setup may fail, with the following error message in the Smssetup.log when upgrading from Systems Management Server 1.0 or 1.1 to version 1.2: 

   <mm-dd-yyyy hh:mm:ss> Registering connects for XXXXXX (server name)
   sa (default value)
   SMS (default value)
   <mm-dd-yyyy hh:mm:ss> Registered the types
   <mm-dd-yyyy hh:mm:ss> Upgrade thread: Failed to register SQL connection
   types.

RESOLUTION

To correct this problem, perform the following steps:

  1. Run the SQL Client Configuration utility.

  2. Select the Default Network for Net Library (by default, SQL Server is configured for Named Pipes).

  3. Run SQL Server Setup and click Continue twice.

  4. Click Change Network Support and then click Continue.

  5. Select the network protocol(s) you want SQL Server to use.

Additional query words: prodsm sms
Keywords : kbinterop kbnetwork ntconfig ntinterop smsadmin smssetup
Version : 1.0 1.1 1.2 4.21a 6.0 6.5
Platform : WINDOWS

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: April 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.