This article was previously published under Q238091
This article has been archived. It is offered "as is" and will no longer be updated.
Existing SQL Server advanced entries are deleted when the server name that is the same as the advanced entries is added or edited from the ODBC administrator during a data source name (DSN) configuration.
This problem may occur in the SQL Server ODBC driver version 3.70.0623 or later. The earlier versions of the SQL Server ODBC driver allow you to create the advanced entries without deleting existing entries.
When a DSN is created with the SQL Server ODBC Driver version 3.60.0319 or earlier, 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 the new client utility is causing the problem to occur.
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.
The Cliconfg.dll and Cliconfg.exe files that are installed by SQL Server 7.0 SP2 fix the problem.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
Steps to Reproduce Behavior
Using SQL Server 6.5 Client Configuration Utility perform the following steps:
Go to the Net Library tab and set the Default Network to Named.
Using the ODBC Administrator version 3.510.3513 or higher with SQL Server ODBC driver version 3.70.0623 perform this step:
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: