Article ID: 272426 - Last Review: September 6, 2006 - Revision: 4.0 FIX: Error Message 1203 Followed by Stack Overflow With Keyset CursorsThis article was previously published under Q272426 BUG #: 18833(SQLBUG_65) SYMPTOMS When the FETCH process of a keyset cursor is blocked by
another user transaction during lock escalation and is then subsequently
released from blocking, the following 1203 error message occurs:
Caller of lock manager is incorrectly trying to unlock
an unlocked object. spid=%d locktype=%d dbid=%d lockid=%Id CAUSE When the FETCH process completes, it tries to release the
locks that are no longer held due to lock escalation. WORKAROUND Change to a different cursor type (for example, Dynamic).
STATUS Microsoft has confirmed this to be a problem in SQL Server
version 6.5. This problem has been corrected in the Post Service Pack 5a Update
for Microsoft SQL Server version 6.5. To install the Post Service Pack 5a
Update, you must have either SQL Server 6.5 SP5 or SP5a installed. For information about how to download and install the SQL Server 6.5 Service Pack 5a, refer to the following article in the Microsoft Knowledge Base: 197177
(http://support.microsoft.com/kb/197177/EN-US/
)
INF: How to Obtain SQL Server 6.5 Service Pack 5a
If you already have SQL Server 6.5 SP5 or SP5a installed, you can
download the Post SP5a Update from the following article in the Microsoft
Knowledge Base: 274036
(http://support.microsoft.com/kb/274036/EN-US/
)
INF: How to Obtain SQL Server 6.5 Post Service Pack 5a Update
For more information, contact your primary support provider.
| Article Translations
|

Back to the top
