Microsoft KB Archive/133250

= Unable to connect to SQL Server if default protocol Is changed =

Article ID: 133250

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 1.0 Standard Edition
 * Microsoft Systems Management Server 1.1 Standard Edition
 * Microsoft Systems Management Server 1.2 Standard Edition

-



This article was previously published under Q133250



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:

Error message 1

Unable to connect: SQL Server is unavailable or does not exist. Specified SQL Server not found.

Error message 2

Couldn't connect to server.

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:

 Registering connects for XXXXXX (server name)

sa (default value)

SMS (default value)

 Registered the types

 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) Click the Net Library tab.
 * 3) Do one of the following:
 * 4) * Click Named Pipes as the default network for the net library configuration.

By default, SQL Server is configured for named pipes.
 * 1) * Click the Alias tab, click Add, type the server name of the SQL server that contains the SMS database, and then click Named Pipes as the net library. Then, click OK.

Additional query words: prodsm sms

Keywords: kbinterop kbnetwork kbsetup kbsmsadmin KB133250

-

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

© Microsoft Corporation. All rights reserved.