BUG: SQL Server ODBC Driver Removes Entry From WIN.INI

 Last reviewed: September 9, 1996
Article ID: Q112513
The information in this article applies to:
  • Microsoft Open Database Connectivity, version 1.0

BUG# ODBCSS: 2834 (1.01.22807)

SYMPTOMS

If an existing data source is reconfigured in such a way that only its name is changed using either ODBC Administrator or ODBC icon from Control Panel for the SQL Server driver, the corresponding server entry in the WIN.INI entry (for non-default network or Network Library) is removed.

For example, assume a data source called MYSOURCE is configured and maps to a SQL Server machine called SQLNT1. Also it is using dbmsspx3 net-library. So in the ODBC.INI file, the server entry for [MYSOURCE] would be SQLNT1 and the corresponding entry in WIN.INI for this would be under SQL Server section as follows: 

   [SQL Server]
   SQLNT1=dbmsspx3,SQLNT1
Now if the data source name is changed from MYSOURCE to NEWSRC using ODBC Administrator or ODBC icon in the control panel, the above entry for SQLNT1 will be removed. This happens even though the server entry in ODBC.INI for the [NEWSRC] still points to SQLNT1.

NOTE: In case of default network and net-library, no entry in needed in the WIN.INI.

WORKAROUND

Remove the data source and the add it back again. That will add the entry back in WIN.INI.

STATUS

Microsoft has confirmed this to be a problem in SQL Server Driver version 1.01.2807. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbusage
KBSubcategory:

Additional reference words: 1.01.2807 Access VB Visual Basic Visual C++



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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.