but the templating process just pointed the new VM's virtual disk to the template's VMDK file. Looking at the settings of the VM that the validation process was barking about, it's virtual hard disk file was pointing to the template's VMDK instead of it's own.īasically the deployment of the template to that VM failed. When I tried to VMotion the VMs the validaton failed stating the other host didn't have a datastore on which a VMDK that was attached to it resided. I then tried to VMotion all of my other VMs to the host on which I had removed the problem datastore to reboot the host again. As a last resort I stopped presenting the LUN to one of the ESX hosts. I removed the problem template/VM from the VC inventory. When I tried to remove it I received an error that stated that the datastore was in use, even though I migrated all of the VMs off the datastore and there were no running VMs using the datastore - or so I thought. Well as a last resort I was going to remove the datastore on which the template resided and recreate it. BTW, that is not a knock on VMware Support - they were very helpful and extremely knowledgeable and tried a lot of things I didn't know of. I also followed the procedure in this document: I even called VMware support and they were stumped as well. I tried almost everything I knew of to resolve the issue - migrating the VMs off the host and rebooting it, moving all the VMs back and rebooting our second host, cloning the template, copying the disk via vmkfstools - all failed because the datastore thought the file was in use. I received the "Unable to access a file since it is locked" error. Thinking it could possibly be a template issue I converted the template to a VM and tried to power it on. Looking through vmware.log there was an error that stated it couldn't open the VMDK flat file because "Device or resource busy." When we tried to deploy another VM from the template VC popped up the error that it couldn't find the VMDK file associated with the template. We deployed almost 10 VMs from this template with no problems.
#Accountedge pro 2018 unable to access lock file update
We had created a template on our new VI3 system (ESX 3.5 update 1 and VC 2.5 Update 1).
I just wanted to post this information for others that might be having the same issue.
0 kommentar(er)
