This article was previously published under Q241304
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 18803 (SQLBUG_65)
The following error may occur:
Msg 1203, Level 20, State 2, Line 2 Caller of lock manager is incorrectly trying to unlock an unlocked object. spid=10 locktype=4 dbid=8 lockid=912006280
If all of the following are true:
A row is inserted into a table that has a foreign key constraint to another table.
An INSERT trigger is fired by the INSERT.
The trigger rolls back the transaction, but continues processing and starts a new transaction.
The server is running SQL Server 6.5 SP5a or later.
NOTE: The values listed for spid, locktype, dbid and lockid will differ from case to case.
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 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 INF: How to Obtain SQL Server 6.5 Post Service Pack 5a Update
For more information, contact your primary support provider.
This fix requires that trace flag 251 be enabled to resolve the problem. To enable this trace flag, add -T251 to the startup parameters of SQL Server.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
245672 BUG: Insert Trigger that Issues a Rollback May Cause Error 1203