FIX: Error 231 After Opening a Server Side CursorLast reviewed: October 29, 1997Article ID: Q165621 |
The information in this article applies to:
SYMPTOMSIn a multi-threaded application that has two threads, when the first thread does a SQLExecDirect of a select statement and the second thread does a SQLCancel in the middle of the select, the driver does not get a response back from the server, and therefore closes the connection. The following error is reported by the Net-Library:
Error 231: ConnectionTransact (GetOverLappedResult()).The SQL Server driver then reports the following error:
szSqlState = "08S01", *pfNativeError = 0, *pcbErrorMsg = 61 szErrorMsg = "[Microsoft][ODBC SQL Server Driver]Communication link failure" WORKAROUNDThere is no known workaround at this time.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server driver version 2.65. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.
|
Additional query words: odbc cursor
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |