Skip to main content

VMWare – Failed to lock the file - Cannot open the disk vmdlk or one of the snapshot disks it depends on

I face this issue when my VMWare could not open the virtual machine and was giving error: Failed to lock the file - Cannot open the disk *.vmdlk or one of the snapshot disks it depends on.

Cannot open the disk 'G:\VPC\WinXpPro\Windows XP Professional-000001.vmdk' or one of the snapshot disks it depends on.
Reason: Failed to lock the file.

image

Resolution: To solve this issue I opened the folder that has my virtual machine files ('G:\VPC\WinXpPro\). I found couple of folders that are named as ***.lck. I select them all and deleted them. You can also try to rename them if not comfortable with deleting them.

Windows XP Professional-000002.vmdk.lck
564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck
Windows XP Professional.vmdk.lck
Windows XP Professional-000001.vmdk.lck
Windows XP Professional.vmx.lck

image

Comments

  1. Thanks for the valuable information!

    ReplyDelete
  2. This blog is written by a blogger regarding some internet issues. These are such issues that sometimes I need to face during college-paper-writing-service.reviews and also at the time when I upload my essays. The basic concern of this blog is about the issue of VMWare and how to resolve the issue.

    ReplyDelete
  3. History, memory and overlooking. Stunning! I like it and value the author of this book or full guide on writing a cover letter. I will read the book in two or three days as I get free from studies. a debt of gratitude is in order for allowing to the perusers to peruse this book.

    ReplyDelete

Post a Comment

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then ...

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs.   25 Best Blogs of 2009     25 Best Blogs 2008   25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog ...

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck ...