Starting a new job in System Center 2012 Virtual Machine Manager fails with error 2606

Symptoms

When starting a new job in System Center 2012 Virtual Machine Manager (VMM) the following error may be generated:

Error (2606)
Unable to perform the job because one or more of the selected objects are locked by another job.

Recommended Action
To find out which job is locking the object, in the Jobs view, group by Status, and find the running or canceling job for the object. When the job is complete, try again.



A VMM trace will show lines similar to the following:

48412,04:24:10.457 02-10-2014,0x097C,0x05BC,4,CarmineObjectLock.cs,822,0x00000000,CarmineObjectLock; Task 257b4ee6-f1c7-4c71-9b07-3eb4682d001f Failed Acquiring Delete lock on VM object with ID 6ac448fa-752c-4ebc-94b2-08da290ab479 because Task 2880a0e0-58cf-4097-a567-13a7effbac0c has Write lock,{00000000-0000-0000-0000-000000000000},1,


Cause

This error is caused by locked records in the VMM database due to another job placing a lock on the objects that this job is attempting to access. This is by design.

Resolution

To see what object locks currently exist, use the following VMM database query:

SELECT * FROM [VirtualManagerDB].[dbo].[tbl_VMM_Lock] where TaskID='Task_GUID'

If any records are present, make a backup of the database and run the command:

DELETE FROM [VirtualManagerDB].[dbo].[tbl_VMM_Lock] where TaskID='Task_GUID'



For example (from the error above):


DELETE FROM [VirtualManagerDB].[dbo].[tbl_VMM_Lock] where TaskID='2880a0e0-58cf-4097-a567-13a7effbac0c'



Properties

Article ID: 2795040 - Last Review: Jan 23, 2013 - Revision: 1

Microsoft System Center 2012 Virtual Machine Manager

Feedback