i cannot export to .ovf file...i keep getting the attached error

[wakaIT]

I keep getting error attached

[wakaIT]

see ovftool.log attached

[wakaIT]

is andre in the house?

[ThompsG]

Hi there,

Looking through the log it appears that you are getting access denied when opening fortimail-vm-64bit-1024gb-hw7-disk2.vmdk

2016-02-05T21:10:13.619+01:00 [06788 verbose 'Default'] Opening disk target fortimail-vm-64bit-1024gb-hw7-disk2.vmdk

2016-02-05T21:10:13.635+01:00 [06788 info 'Default'] CoreDump: Writing minidump

2016-02-05T21:10:15.866+01:00 [06788 panic 'Default']

-->

--> Panic: Win32 exception: Access Violation (0xc0000005)

Can you confirm that you are running VMware Workstation with the "Run as Administrator" option?

Kind regards.

[wakaIT]

Yes, I used the 'Run as Admininistrator' Option

Still getting the same error.

And the backup location is to an external hard drive.

[continuum]

I would regard the export to an external harddrive  as an experimental feature - can you export to a fregular drive ?
On external harddisks you may run intoproblems using vmdk-slices larger than 2gb.
In the list of vmdks I see only 2 snapshots - something is strange here ... have the snapshots been manually renamed ?
Please attach the vmx-file to your next reply - also please add the vmdk-descriptorfiles.
If the vmdk is split into pieces -do you have 2gb-slices or do they get larger than that ?

[wakaIT]

The Hard disk is 2TB

Also see attached the vmx file and screenshot showing all files associated with the virtual machine in question.

It has more than one vmdk files and some are more than 200GB while another one is as large as 800+GB.

[brunofernandez1]

as I can see you have some lock files on your disk.

did you have shut down the vm before you tried to export it?

is the vmdk disk maybe attached also to other vms?

[Ahmed_Selim]

Please attach the vmx file.

Sometimes that happens because some error in the unicode in the vmx file    

[wakaIT]

Yes i Shut down the VM before trying to export it.

The vmdk disks are not attached to any other VMs.

Cloning  was done around november though.

[wakaIT]

vmdk already attached.

Please check conversation trail

[ThompsG]

Hi,

Can you confirm that the second VMDK is allocated 2TB - the ovftool.log is only detecting it as 1TB:

-->     <Disk ovf:capacity="1024" ovf:capacityAllocationUnits="byte * 2^30" ovf:diskId="vmdisk2" ovf:fileRef="file2" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"/>

Also as other posters have mentioned there appears to be a mismatch with snapshots with the first vmdk only having one currently and the second vmdk having four in the chain according to the screenshot provided. Are you able to explain why this might be the case?

The snapshots against vmdisk2 are also quite large (200GB+) however I'm not convinced this is the issue as from the logs you can see that an error is generated 1 second after trying to open vmdisk2. When you shut the VM down to export, can you confirm that there is no *.lck directories left before starting the process? Can you also check the VMX file to confirm that it lists the VM as having a clean shutdown?

I'm wondering if it is possible for you to post the vmdk descriptor files here. To do this you will need to download dsfo from here: http://members.ozemail.com.au/~nulifetv/freezip/freeware/dsfok.zip

The syntax is as follows: dsfo <vmdk name> 512 1024 <descriptor name>

Thanks and kind regards.

[wakaIT]

The VMDK is actually allocated 1TB

The Virtual machine uses two .vmdks

disk1 and disk2

disk2 is the one that grows(or increases)

Also the Virtual machine has been cloned before, maybe that will help.

See attached, the vmx file showns vm had a clean shutdown

The following commands were run to get the .vmdk descriptor files which have been attached therein:

dsfo "C:\Users\Administrator\Documents\Virtual Machines\fortimail-vm-64bit-1024gb-hw7\fortimail-vm-64bit-1024gb-hw7-disk1.vmdk" 512 1024 " C:\Users\Administrator\Documents\Virtual Machines\disk1.txt"

dsfo "C:\Users\Administrator\Documents\Virtual Machines\fortimail-vm-64bit-1024gb-hw7\fortimail-vm-64bit-1024gb-hw7-disk2.vmdk" 512 1024 "C:\Users\Administrator\Documents\Virtual Machines\disk2.txt"

dsfo "C:\Users\Administrator\Documents\Virtual Machines\fortimail-vm-64bit-1024gb-hw7\fortimail-vm-64bit-1024gb-hw7-disk1-000003.vmdk" 512 1024 "C:\Users\Administrator\Documents\Virtual Machines\disk1-000003.txt"

dsfo "C:\Users\Administrator\Documents\Virtual Machines\fortimail-vm-64bit-1024gb-hw7\fortimail-vm-64bit-1024gb-hw7-disk2.vmdk" 512 1024 " C:\Users\Administrator\Documents\Virtual Machines\disk2.txt"

dsfo "C:\Users\Administrator\Documents\Virtual Machines\fortimail-vm-64bit-1024gb-hw7\fortimail-vm-64bit-1024gb-hw7-disk2-000001.vmdk" 512 1024 "C:\Users\Administrator\Documents\Virtual Machines\disk2-000001.txt"

dsfo "C:\Users\Administrator\Documents\Virtual Machines\fortimail-vm-64bit-1024gb-hw7\fortimail-vm-64bit-1024gb-hw7-disk2-000002.vmdk" 512 1024 "C:\Users\Administrator\Documents\Virtual Machines\disk2-000002.txt"

dsfo "C:\Users\Administrator\Documents\Virtual Machines\fortimail-vm-64bit-1024gb-hw7\fortimail-vm-64bit-1024gb-hw7-disk2-000003.vmdk" 512 1024 "C:\Users\Administrator\Documents\Virtual Machines\disk2-000003.txt"

dsfo "C:\Users\Administrator\Documents\Virtual Machines\fortimail-vm-64bit-1024gb-hw7\fortimail-vm-64bit-1024gb-hw7-disk2-000004.vmdk" 512 1024 "C:\Users\Administrator\Documents\Virtual Machines\disk2-000004.txt"

Awaiting your prompt response

[continuum]

Now thats interesting: the snapshots for disk 2 use this 2 new parameters:

ddb.consolidateDestFileName
ddb.resumeConsolidateSector

I dont know what you have tried before to get this additional ddb-entries.
But I doubt that the ovf-tool knows how to deal with them.
Do you really need to export the VM with all the snapshots ?
I guess that if you clone fortimail-vm-64bit-1024gb-hw7-disk2-000004.vmdk to fortimail-vm-64bit-1024gb-hw7-disk2-new.vmdk with vmware-vdiskmanager.exe then the ovf-export would work.