ahmedrehim89
Contributor
Contributor

Not a valid VM Configurationg file

Hi

I try to run this VM this error appear to me 

ahmedrehim89_1-1664967999495.png

I noticed that vmx file is empty and 0 kb file

ahmedrehim89_2-1664968153175.png

I upload the log files of this VM .. Can anyone help me with this issue .

 

Labels (1)
0 Kudos
13 Replies
RDPetruska
Leadership
Leadership

Either attach the vmware.log file to a post here so we can run a utility to extract the vmx from the log., or search for the log2vmx (I think that's the name/label) tool in the forum.

0 Kudos
ahmedrehim89
Contributor
Contributor

Done I upload the log files

thanks for your help

0 Kudos
ahmedrehim89
Contributor
Contributor

Done

Thanks For Your Help

0 Kudos
RDPetruska
Leadership
Leadership

Attached is the extracted file, zipped up.  Try this.

0 Kudos
ahmedrehim89
Contributor
Contributor

after replace the file this error appear

ahmedrehim89_0-1664976937336.png

 

0 Kudos
ahmedrehim89
Contributor
Contributor

can anyone help me with last error ??

0 Kudos
maksym007
Hot Shot
Hot Shot

Did you do any snapshots of this VM?

 

0 Kudos
a_p_
Leadership
Leadership

Restoring VMs with snapshots can be tricky.
I strongly recommend that the first thing you do, is to backup the VM's files/folder, to have a way back in case something doesn't work as expected.

Here's what I like you to do:

  1. close VMware Workstation
  2. create a new directory on the E: drive (e.g. "E:\VM-Rescue")
  3. run dir E:\VM\shubra\Shoubra\*.* /one > E:\VM-Rescue\filelist.txt
  4. extract the files from the attached .zip archive to E:\VM-Rescue
  5. Drag&Drop the VM's folder onto Get-VmdkHeader.cmd (this will extract the Metadata from the .vmdk files)
  6. copy the VM's .vmsd, its .vmx, and .vmx~ files as well as the latest vmware.log to E:\VM-Rescue
  7. compress/zip E:\Rescue, and attach the .zip archive to your next reply

Note: The attached scrips will only extract metadata, i.e. no user data.

André

0 Kudos
ahmedrehim89
Contributor
Contributor

thanks for your help this is the required compressed file

0 Kudos
ahmedrehim89
Contributor
Contributor

Any Update ??

0 Kudos
a_p_
Leadership
Leadership

What you may want to try is to delete the following files, and folders:

09/04/2022 02:47 PM 13,019,119,616 564d3b6c-4ff6-b00e-472c-9ea414dd5f4b.vmem
09/26/2018 08:23 PM <DIR> caches
09/04/2022 02:00 PM <DIR> Shoubra-Snapshot13.vmem.lck
09/24/2022 04:49 PM <DIR> Shoubra-Snapshot34.vmem.lck

and remove all lines from the .vmx file that contain "rollingtier" to disable "Autoprotect".

André

0 Kudos
ahmedrehim89
Contributor
Contributor

Same error appears

0 Kudos
a_p_
Leadership
Leadership

The snapshot chaining looks strange. Theres a cross reference in the chain, that havn't seen before!?

Assuming that you have a current backup of the VM's folder, delete the below files.
This should allow you to use the VM in its current state, but you can't switch between snapshots anymore.

09/23/2022 05:13 PM 1,733 Shoubra.vmsd
09/24/2022 04:49 PM 73,269,248 Shoubra-000002.vmdk
09/23/2022 05:13 PM 610,533,376 Shoubra-000003.vmdk
09/24/2022 04:49 PM 469,106,688 Shoubra-000005.vmdk
04/24/2019 06:52 PM 33,153 Shoubra-Snapshot1.vmsn
09/04/2022 02:00 PM 13,019,119,616 Shoubra-Snapshot13.vmem
09/04/2022 02:00 PM 3,539,848 Shoubra-Snapshot13.vmsn
08/24/2022 03:43 PM 33,895 Shoubra-Snapshot2.vmsn
09/21/2022 05:03 PM 13,019,119,616 Shoubra-Snapshot31.vmem
09/21/2022 05:03 PM 2,393,492 Shoubra-Snapshot31.vmsn
09/23/2022 05:11 PM 13,019,119,616 Shoubra-Snapshot33.vmem
09/23/2022 05:11 PM 2,393,492 Shoubra-Snapshot33.vmsn
09/24/2022 04:49 PM 13,019,119,616 Shoubra-Snapshot34.vmem
09/24/2022 04:49 PM 39,973 Shoubra-Snapshot34.vmsn

André

0 Kudos