PRB: Unable to Connect to Stand-Alone SQL Server

• Microsoft SQL Server, versions 4.2x, 6.0, and 6.5

SYMPTOMS

Attempting to connect to SQL Server on a stand-alone computer or a laptop computer with no network connections may fail with the following error message:

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

CAUSE

By default, client connections to SQL Server are made over a network protocol. Without a simulated network connection, the connection to SQL Server cannot be made unless a local named pipes connection is forced.

WORKAROUND

To simulate network connectivity, install the MS Loopback Adapter according to the following steps for the version of Windows NT Server you are using:

Windows NT Server 4.0:

1. In Control Panel Network, click the Adapters tab and then click Add.

2. From the list, select the MS Loopback Adapter.

1. In Control Panel Network, click Add Adapter.

2. From the Network Adapter Card menu, select MS Loopback Adapter.

If you are unable to install the MS Loopack Adapter, shut down the workstation service (through Control Panel Services) to force a local named pipes connection to be made during installation. Be aware that this approach extends the installation time considerably. After the server is installed, you can restart the workstation services. For subsequent connections, you can force a local named pipes connection to the server by not specifying the server name at connection time. You may also specify ".", or "(local)" as the server name in ISQL/w and in SQL Enterprise Manager when registering the server. Alternatively, you can add an advanced entry in the client configuration utility, specifying ".", or "(local)" as the connection string for the server name.

For 16-bit applications, the MS Loopback Adapter is required. For more information, see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q130745
   TITLE     : Connecting to Standalone SQL Server Using 16-bit Apps.

1. From a command prompt, type the following:

   cd \sql\binn setup /t RegistryRebuild = On

   NOTE: For SQL Server version 6.0, you can use either = On or = True for the Setup command line.

   NOTE: For SQL Server version 6.5, the default directory is \Mssql\Binn.

   NOTE: Be sure to type the Setup command exactly as indicated, including capitalization. There must be a space on both sides of the equal sign.

2. Build your master. When the retry dialog appears, task out and setup an advanced client config as the server name, named pipes, ".". Then press the retry button in SQL Server setup.

3. Once you have a valid master built, run the upgrade to ensure all scripts are active. This may again encounter the login error. Reset the client configuration advanced entry.