BUG: Inserts Can Cause Error Message 1203 to OccurLast reviewed: April 30, 1997Article ID: Q124355 |
The information in this article applies to:
SYMPTOMSInserts can cause the following 1203 error message to occur if a table has a non-unique clustered index, and is running on a multiprocessor machine with SMP support:
Msg 1203 Level 20 State 1 Caller of lock manager is incorrectly trying to unlock an unlocked object. spid=%d locktype=%d dbid=%d lockid=%ld. WORKAROUNDTurn off dedicated multiprocessor support to allow the insert to complete. Another option is to replace the clustered index on the problem table with a nonclustered index, which would prevent the error. In addition, adding or subtracting several rows from the table will most likely change the state of the table and allow the insert to complete.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server version 4.21a. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: Windows NT smp
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |