FIX: Async Keyset Cursors and Memory Pressure May Cause AV and Server Shutdown

This article was previously published under Q226154
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 55013 (SQLBUG_70)
If users are executing asynchronous keyset cursors while SQL Server is under memory pressure, a handled access violation (AV) and/or a runtime error that ends the SQL Server process may occur.

The client application may be returned one of the following errors before the access violation or shutdown of the server:
Error: 16942
Could not generate asynchronous keyset. The cursor has been deallocated.
Error: 16917
Cursor is not open.
To work around this problem, disable asynchronous keyset cursors by changing the 'cursor threshold' configuration value to -1 (which is the default).

You also may be able to avoid this problem by increasing the memory available to SQL Server or by reducing memory consumption of other applications on the SQL Server.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
The following errors and stack trace may be seen in the error log when encountering this problem:

Short Stack Dump0x005aec8e Module(sqlservr+1aec8e) (CCursorXCFetch::ResetPoplThreadLocalStore+d)0x005aeba6 Module(sqlservr+1aeba6) (CCursorXCFetch::ResetScan+1d)0x0059c046 Module(sqlservr+19c046) (CCursor::Close+b6)0x0059bf5e Module(sqlservr+19bf5e) (CCursor::Open+145)0x00599ae7 Module(sqlservr+199ae7) (CCursorSimpleStmt::XretExecute+a1)0x00419efa Module(sqlservr+19efa) (CMsqlExecContext::ExecuteStmts+118)0x00419a0f Module(sqlservr+19a0f) (CMsqlExecContext::Execute+16b)Error occurred during cursor close.Error occurred during cursor cleanup.				
The server may also shut down prematurely when encountering this problem. If SQL Server is running as a service, the error log will contain no indication of why the shutdown occurred.

If SQL Server is running from the console, the following message will be dumped to the console before the shutdown:
runtime error R6025
- pure virtual function call
async asynch terminate terminates terminated killed errorlog

Article ID: 226154 - Last Review: 10/20/2013 22:49:52 - Revision: 2.0

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB226154