BUG: Broken Connection Can Cause Next Connection to Hang

 Last reviewed: April 29, 1997
Article ID: Q117512

The information in this article applies to:
  • Microsoft SQL Server Programmer's Toolkit, version 4.2
BUG# 10048 (4.21)

SYMPTOMS

A connection to an OS/2 SQL Server made with an application using OS/2 4.21 DB-Library (DB-Lib) is broken and causes a 1608 error to be generated in the SQL Server error log. If the next connection to the OS/2 Server is from an application using OS/2 4.21 DB-Lib, the second connection will hang.

If the second connection is made using any earlier version of OS/2 DB- Library or the second connection is from any other platform, there is no problem.

If the original error is generated by anything other than an OS/2 application using 4.21 version of DB-Library, there is no problem.

WORKAROUND

Use version 4.20.50 of DB-Library for the OS/2 applications.

STATUS

Microsoft has confirmed this to be a problem in DB-Library version 4.21.00 for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: errorlog dblib
Keywords : kbbug4.21 kbprg SSrvDB_Lib
Version : 4.21
Platform : OS/2

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