Microsoft KB Archive/114528

BUG: Server Not Responding to dbcancel() Last reviewed: April 29, 1997 Article ID: Q114528

The information in this article applies to: Microsoft SQL Server versions 4.2 and 4.2a for OS/2 BUG# 1690 (4.2) SYMPTOMS After a DB-Library (DB-Lib) call returns FAIL due to DB-Library error 10024, SQL Server connection timed out subsequent calls to dbcancel() return FAIL and result in multiple 10024 errors. The current command batch is not canceled and calls to dbsqlexec() will fail with error 10038: Attempt to Initiate a New SQL Server operation with results pending. CAUSE When a query times out due to certain locking conditions, SQL Server may be unable to respond to the attention signal sent by dbcancel(). When the locks that caused the original query to timeout are freed, dbcancel() can be executed successfully, and subsequent calls to dbsqlexec() will not generate 10038 errors. WORKAROUND Should dbcancel() return FAIL due to a 10024 error, it is necessary to either wait for the locking condition on the SQL Server to clear, or to close the current DBPROCESS and open another. STATUS Microsoft has confirmed this to be a problem in SQL Server version 4.2 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: dblib Keywords : kbbug4.20 kbprg SSrvDB_Lib Version : 4.2 4.2a 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.