error 2606 unable to perform the job because one or more of the selected jobs are locked by another job

Question

_{Wednesday, February 6, 2013 11:56 PM}

Sigh.  I'm stuck.  For seemingly no reason host refreshes started erroring out with the error in the title.  Everything is Windows 2012, using VMM 2012 SP1.  I've tried:

• reboot host server
• reboot vmm server
• remove server via GUI (fails with same error)
• remove server via powershell with -force (same error)
• throwing coffee cup into wall
• using foul language

How can I clean this up?

The error indicates that I should look for running or cancelled jobs and wait for them to complete.  There are no running jobs and the cancelled jobs are, well, cancelled, so they won't ever complete.

All replies (2)

_{Thursday, February 7, 2013 2:13 AM ✅Answered | 1 vote}

Hi,

You may refer to this article:

Starting a new job in System Center 2012 Virtual Machine Manager fails with error 2606
http://support.microsoft.com/kb/2795040

This KB talks about an issue where you can get error 2606 when starting a new job in VMM 2012. Error 2606 can occur when a new job is started if there’s another job that already has locks on the db. It’s pretty standard behavior but the KB shows you how to figure out what objects locks currently exist.

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

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

For more information please refer to following MS articles:

Error 2606 - Host Not Responding
http://social.technet.microsoft.com/forums/en-US/virtualmachinemanager/thread/d7d5d208-589a-4ce0-8252-7c7ed00dbafc/

System Center 2012 Virtual Machine Manager SP1 Maintenance Mode Causes Refresh Errors 13926, 2606
http://support.microsoft.com/kb/2800073

Hope this helps!

TechNet Subscriber Support

If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

Lawrence

TechNet Community Support

_{Thursday, December 4, 2014 3:42 PM}

Just as an FYI. Mine failed with the same error and it was because I was cloning a VM with a DVD ISO attached.

I unmounted the ISO and the clone worked just fine. It would be SO USEFUL if the error hinted at this cause rather than a generic one.