BUG: Low LE Threshold Maximum Can Cause 1203, 216 & 603 Errors

ID: Q152626

The information in this article applies to:

SYMPTOMS

A query may return one or more of the following error messages:

Msg 1203, Level 20, State 2
Caller of lock manager is incorrectly trying to unlock an unlocked
object. spid=11 locktype=7 dbid=2 lockid=132.

Msg 216, Level 16, State 3
Attempt to drop temporary object(s) failed during cleanup processing.
Command has been aborted.

Msg 603, Level 19, State 1

When the Msg 603 error occurs, the actual error message is not returned, and the user connection is disconnected.

Occasionally, an access violation error occurs in conjunction with the above messages.


CAUSE

These errors occur if LE THRESHOLD MAXIMUM has been set to a very low value.


WORKAROUND

Increase the value of LE THRESHOLD MAXIMUM with sp_configure.


STATUS

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


MORE INFORMATION

If you examine the errorlog, you will find one or more error messages similar to the following:

Error : 1203, Severity: 20, State: 2
Caller of lock manager is incorrectly trying to unlock an unlocked
object. spid=11 locktype=7 dbid=2 lockid=1.

Error: 603, Severity: 19, State: 1

WARNING: Pss found with open sdes; pspid 11, psuid 1, pcurdb 2, system
table entry 0, sdesp 0xa4b718, objid 8

WARNING: Process being freed while holding Dataserver semaphore



Additional query words: AV 


Keywords          : kbnetwork SSrvGen SSrvLock kbbug6.00 
Version           : 6.0
Platform          : WINDOWS 
Issue type        :

Last Reviewed: March 27, 1999