INF: Handling ODBC Errors in Remote SQL Server Setups

 Last reviewed: May 2, 1997
Article ID: Q149920

The information in this article applies to:
  • Microsoft SQL Server, version 6.0

SUMMARY

Errors generated during the ODBC portion of a SQL Server 6.0 or later remote setup are displayed on the remote server, not the one running setup.

MORE INFORMATION

SQL Server's setup program uses ODBC's setup program to install or upgrade the Win32 ODBC components. The ODBC setup is invoked on the remote server because the ODBC setup itself does not have a remote option. If any ODBC components are running on the remote server, the messages from the ODBC setup saying it cannot replace in-use ODBC DLLs are displayed on the remote server, not on the server running the SQL Server setup. If there are no users at the remote server to respond to these errors, it will appear that the remote SQL Server setup is hung in the ODBC setup phase. If a user on the remote server replies IGNORE to the messages they see without informing the user running setup, the setup user may not be aware that some ODBC DLLs were not upgraded.

Users should ensure that no ODBC applications or tools are running on the remote server at the time the remote setup is started. This includes the ODBC Administrator launched from Control Panel. Or, have a user at the remote site monitor the remote server for ODBC setup errors.

Additional query words: setup debug
Keywords : kbsetup kbusage odbc SSrvInst
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.