BUG: Recursive Error 1203 When Cancelling Striped Table Dump

 Last reviewed: January 27, 1998
Article ID: Q179925
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: NT: 17654 (6.5)

SYMPTOMS

Canceling a striped table dump operation may result in SQL Server recursively logging error 1203. To stop logging the error, you must restart SQL Server. The sequence of messages in the errorlog is: 

   dmptable: User attention received
   Error : 1203, Severity: 20, State: 2
   Caller of lock manager is incorrectly trying to unlock an unlocked
   object. spid=42 locktype=2 dbid=8 lockid=761105802.

   ... <repeat of above error 1203>
Note that the locktype will be 2 (a shared table lock) for this particular problem.

CAUSE

Because of a synchronization issue, multiple threads are trying to release the same lock on the table, causing the second thread to receive the error 1203. In an effort to clean up, the message is logged recursively.

WORKAROUND

To work around this problem, do either of the following:

  • Dump tables to a single dump device.

    -or-

  • Avoid canceling the operation when striping the dump to multiple devices.

STATUS

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

Additional query words: attn attention cancel SQLCancel dbcancel message
msg
Keywords : kbbug6.50 SSrvAdmin ssrvtrans_sql
Version : WINNT:6.5
Platform : winnt
Issue type : kbbug
Solution Type : kbworkaround

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 27, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.