Try restarting this service form the ESX host console
Service mgmt-vmware restart
Your Host will disconnect for a few second from VC and come back.Try to deploy again. No impact to your VMs
I found the answer I was looking for! A post by djflux at http://communities.vmware.com/thread/152969 "So if you receive the "Unable to access a file since it is locked" when powering on a VM, or receive an error about can't find the file when trying to deploy a new VM from a template, check ALL your VM's vmx files to make sure that one of them is not actually using that template/VMs VMDK file."
I found that someone deployed a vm from a template and the .vmdk it was referencing was the one in the template folder! Using FASTSCP, I copied each of the .vmdks from the template folder and the vm's folder and switched them, then I attached the correct .vmdk and my issue was resolved!
Gotta love this forum!!!
I faced similar problem today ..created the 1st VM from the template and edited the Virtual H/W at the same time ....the VM was up and running but i never noticed that its pointing to the template vmdk file
Could realize the problem when i was not able to create another VM using the same tempalate.It was beacuse the vmdk was locked by the previous VM.
The issue was resolved after manually editing 1st VM ....pointed the correct vmdk ..All set now