Process ID %d attempting to unlock unowned resource %.*ls.

Details
Product: SQL Server
Event ID: 1203
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: LK_NOT
Message: Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
   
Explanation

This error occurs when SQL Server is engaged in some activity other than ordinary post-processing cleanup and it finds that a particular page that it is trying to unlock is already unlocked.

Possible Causes

The underlying cause of this error may be related to structural problems within the affected database. SQL Server manages the acquisition and release of pages to maintain concurrency control in the multiuser environment. This mechanism is maintained by using various internal lock structures that identify the page and the type of lock present. Locks are acquired for processing of affected pages and released when the processing is finished.

   
User Action

Execute DBCC CHECKDB against the database in which the object belongs. If DBCC CHECKDB reports no errors, try to reestablish the connection and execute the command.

Important:

If you are executing DBCC CHECKDB with one of the REPAIR clauses does not correct the index problem, or if you are not sure what effect DBCC CHECKDB with a REPAIR clause has on your data, contact your primary support provider.

   
   
Version: 9.0
Component: SQLEngine
Symbolic Name: LK_NOT
Message: Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
   
Explanation

This error occurs when SQL Server 2005 is engaged in some activity other than ordinary post-processing cleanup and it finds that a particular page that it is trying to unlock is already unlocked.

   
User Action

Execute DBCC CHECKDB against the database in which the object belongs. If DBCC CHECKDB reports no errors, try to reestablish the connection and execute the command.

Important:

If you are executing DBCC CHECKDB with one of the REPAIR clauses does not correct the index problem, or if you are not sure what effect DBCC CHECKDB with a REPAIR clause has on your data, contact your primary support provider.

   
   
Version: 8.0
Component: SQL Engine
Message: Process ID %d attempting to unlock unowned resource %.*ls.
   
Explanation

This error occurs when Microsoft® SQL Server™ is engaged in some activity other than normal post-processing cleanup and it finds that a particular page it is attempting to unlock is already unlocked. The underlying cause for this error may be related to structural problems within the affected database. SQL Server manages the acquisition and release of pages to maintain concurrency control in the multi-user environment. This mechanism is maintained through the use of various internal lock structures that identify the page and the type of lock present. Locks are acquired for processing of affected pages and released when the processing is completed.

   
User Action

Execute DBCC CHECKDB against the database in which the object belongs. If DBCC CHECKDB reports no errors, attempt to reestablish the connection and execute the command.

Important  If executing DBCC CHECKDB with one of the repair clauses does not correct the index problem, or if you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider.

Related:

Leave a Reply