BUG: Creating New TCP/IP Advanced Entry Deletes Existing Advanced Entries

• Microsoft SQL Server versions 6.5 Service Pack 5 and 5a, 7.0

SYMPTOMS

Existing SQL Server advance entries are deleted when a new TCP/IP sockets advanced entry is created from the ODBC administrator during a data source name (DSN) configuration.

This behavior only occurs with the SQL Server ODBC Driver version 3.70.0623. Previous and later versions of the driver allow you to create the advanced entries without deleting existing entries.

CAUSE

When a DSN is created with the SQL Server ODBC Driver version 3.60.0319, clicking Client Configuration opens the SQL Server 6.5 Client Configuration Utility (WindbVer.exe), which is used to set up and modify advanced entries.

With the 3.70.0623 version of the SQL Server ODBC driver a new client utility interface was introduced and this utility is causing the problem to occur.

RESOLUTION

Do not create advanced entries when a DSN is being configured using the SQL Server ODBC Driver unless the SQL Server 7.0 service pack 2 (SP2) client components are installed on the computer.

STATUS

Microsoft has confirmed this to be a bug in the SQL Server client configuration utility that is installed by SQL Server 7.0 (Original release) as well as SQL Server 7.00 service pack (SP1). The Cliconfg.dll and Cliconfg.exe files that are installed by SQL Server 7.0 SP2 fixes the problem.

MORE INFORMATION

Steps to Reproduce Behavior

1. Go to the Net Library tab and set the Default Network to Named.



2. Go to the Advanced tab and create two entries:

   
   entry#1 : dbmssocn, <ip-address1>,1433
   entry#2 : dbmssocn, <ip-address2>,1433 

1. Go to the System DSN tab and click Add. While configuring the DSN, click Client Configuration and create a new entry for sockets using the name that was entered in the Server field.


The correct TCP/IP address and port number should be entered so that the DSN can be successfully created.

entry#3 : dbmssocn, <ip-address3>, <port3> 

After you complete these steps, when you run the ClientConfig utility again, you will see that only entry3 exists in the Advanced tab. Previously existing entries entry#1 and entry#2 are missing when viewed from the Registry editor (regedt32) under the following:

HKLM_LM\Software\Microsoft\MSSQLServer\Client\ConnectTo
HKLM_LM\ Software\Microsoft\MSSQLServer\Client\TDS

Additional query words:

Keywords : kbbug7.00 kbSQLServ700bug
Version : winnt:6.5 Service Pack 5 and 5a,7.0
Platform : winnt
Issue type : kbbug