BUG: Handled Exception Error Caused by Server Side Cursors

 Last reviewed: June 30, 1997
Article ID: Q170616
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16809 (Windows NT: 6.5)

SYMPTOMS

Server side cursors may cause a handled exception error that closes the client thread on the server if all of the following conditions are true:

  • The cursor contains a text pointer clause.
  • The cursor's concurrency is set to optimistic.
  • The cursor type is keyset.
  • The fetch type is absolute and returns 1 row.

The EXCEPTION_ACCESS_VIOLATION raised is with sp_cursorfetch. This problem occurs when doing a SQLExtendedFetch from a client application, such as Visual Basic or ISQL/W.

STATUS

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

Additional query words: AV Access Violation
Keywords : kbbug6.50 kbprg kbusage SSrvGPF SSrvProg SSrvTran_SQL
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbpending

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