VMware "Failed to lock the file" when reverting back to Snapshot

remove the lck file from the vm folder and try again. please feedback

there is folder .lck created on the location the machine you need to delete it .. see here :

http://www.networknet.nl/apps/wp/archives/396

Thanks for the quick response

I've stopped the virtual machine and checked the datastore but there are no .lck files or folders

When i try to revert to the snapshot with the VM running it fails and then stops the VM

If i try to revert to the snapshot with the VM powered off it just fails

Any further ideas?

ok , check this from vmware :

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033571

also see here  ... its one of possibilities to this problem

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004545

That's a special Snapshot Created by a Third Party Backup Application, it's not designed to be Reverted to.

Leave well alone.

What Backup Application do you use?

We use Netvault, but im not trying to revert back to the SNapshot that the backup created, im trying to revert to the one before it "20111220":  

The Backup is not still running?

You may have to delete the Helper, if you can?

look here :

http://blog.laksha.net/2009/10/vmx-is-not-valid-virtual-machine.html

No, the backup finished before we tried to revert to the snapshot

Tried to delete the Helper but that fails as well, with the same error message

Is the VM Power-On ?

Yes the VM will power on fine, but if we try to revert to the snapshot it fails and powers off the VM at the same time

Can you revert, if the VM is OFF?

look at this case , its same of yours exactly

http://community.spiceworks.com/topic/155873-vmware-reason-failed-to-lock-the-file

In that case they can't power on their VM, but we can, just can't revert it back to a previous snapshot.

If i try to revert while the VM is powered off it fails with exactly the same error message, but obviously doesn't do anything else as the VM is already powered off

We have a backup from before the snapshot was taken so are going to try and restore the entire VM from that - i'll let you know!

Full resotre from a seperate back of the virtual server resolved the problem