VMware Cloud Community
NYSDHCR
Enthusiast
Enthusiast

Unable to deploy vm from template

(VC 2.5 U2 - ESX 2.5U2) I am receiving the following error message when attempting to deploy a vm from a Windows 2003 R2 SP2 X86 template: A"A file not found. [vm_template/WIN2K3_R2_SP2.vmdk" The file is indeed there, and so is the flat file for the vmdk. I can convert the template into a vm, and then back, but I am still not able to deploy a vm from this template? Anyone else experience this before? The templates sit in a shared lun on our SAN. This template has worked for us in the past.

0 Kudos
4 Replies
Vmotioner
Contributor
Contributor

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

0 Kudos
NYSDHCR
Enthusiast
Enthusiast

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!!!

0 Kudos
vmroyale
Immortal
Immortal

Hello. This sounds like it might be the same thing that VMwarewolf posted about recently.

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
0 Kudos
sabya1232003
Enthusiast
Enthusiast

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

0 Kudos