FIX: Async Keyset Cursors and Memory Pressure May Cause AV and Server Shutdown (226154)
The information in this article applies to:
This article was previously published under Q226154
BUG #: 55013 (SQLBUG_70)
SYMPTOMS
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.
WORKAROUND
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.
STATUS
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.
Modification Type: | Major | Last Reviewed: | 3/14/2006 |
---|
Keywords: | kbBug kbfix KB226154 |
---|
|