VMware Cloud Community
Akbari
Contributor
Contributor

Converter Failing at 2%

All,

I am trying to conver a physical (windows 2003 Server R2 with Sp2 - 64 bit) to a VM. I have tried 3 times and every time I get Converter agent error

( ERROR: VMware Converter Agent System Error).

Any idea? Here is the last portion of the logs and I have also attached the full version to this posting.

Any pointer is greatly appreciated.

Returning OS as display Windows Server 2003 Standard x64 Edition

Found a candidate system volume at idx=0

Found a candidate system volume at idx=1

OS resides on partition 1 , disk path

GetDisks: disk= GetDisks: disk= Prepared... Performing volume-based cloning... Opening the target computer... Creating local connection to the co-located slave Registering disposable session object id=computer= Associating disposable session object id=computer= with session id=A85658A0-CAB4-4344-85C3-A40C289EBE20 Getting disks... GetDisks: disk= GetDisks: disk= Disk 0 id=disk= Disk 1 id=disk= Partitioning disk disk= DISKLIB-DSCPTR: Opened : "PRODUCTVM2-flat.vmdk" 0 (0xa) DISKLIB-LINK : Opened '
ProductVMWHost\d$\PRODUCTVM2\PRODUCTVM2.vmdk' (0xa): monolithicFlat, 50976294 sectors / 24891 Mb. DISKLIB-LIB : Opened "" (flags 0xa). 020B6858 DISKLIB-DSCPTR: Opened : "PRODUCTVM2 (2)-flat.vmdk" 0 (0xa) DISKLIB-LINK : Opened '
ProductVMWHost\d$\PRODUCTVM2\PRODUCTVM2 (2).vmdk' (0xa): monolithicFlat, 57932438 sectors / 28288 Mb. DISKLIB-LIB : Opened " (2).vmdk" (flags 0xa). 0208ECF0 No geometry.biosSectors defined, No geometry.biosHeads defined, No geometry.biosCylinders defined, No geometry.biosSectors defined, No geometry.biosHeads defined, Partitioning disk disk=
No geometry.biosSectors defined, No geometry.biosHeads defined, No geometry.biosCylinders defined, No geometry.biosSectors defined, No geometry.biosHeads defined, Error writing partition table Builing partition list: Can't have more then one active partition on a disk. object explicitly disposed: computer= Cleaning up computer's child objects Unregistring disk id=disk= Unregistring disk id=disk= Cloning failed! CloneTask::task: Image processing task has failed with SystemError: "InternalError" CloneTask::task: SetState to error Remote task CloneTask::task completed Waiting for updates from CloneTask::task Got an update from CloneTask::task Cleaning up remote task CloneTask::task Disposing task wrapper for task CloneTask::task object explicitly disposed: CloneTask::task CloneTask::task being destroyed VmiImportTask::task step "clone to VM" failed Reporting image processing task failure for task CloneTask::task ImageProcessingTask FAILED. Fault name: vmodl.fault.SystemError VmiImportTask::task step "clone to VM" destroyed Cloning failed: vmodl.fault.SystemError Removing destination VM Successfully connected to UfaLocalVMCreator VmiImportTask::task step "create and clone to VM" destroyed VmiImportTask::task step "Clone VM" destroyed VmiImportTask::task: Image processing task has failed with SystemError: "InternalError" VmiImportTask::task: SetState to error object explicitly disposed: VmiImportTask::task object explicitly disposed: computer= Cleaning up computer's child objects Unregistring volume id=attVol={computer=,1} Unregistring volume id=attVol={computer={2202622998d91b89190c31c8980df6baba3cfd5d},2} Unregistring volume id=attVol={computer={2202622998d91b89190c31c8980df6baba3cfd5d},3} Unregistring disk id=disk=

Unregistring disk id=disk=

VmiImportTask::task being destroyed

CloseSession called for session id=A85658A0-CAB4-4344-85C3-A40C289EBE20

Removed vmdb connection /db/connection/#7/

0 Kudos
1 Reply
mkagzi
Enthusiast
Enthusiast

Here are some steps that we need to do to confirm connection between the source and destination machine.

Check basic network:

· ping from source system to VC host

· ping from VC to ESX target system

· ping from source system to ESX target system

· ping from ESX target system to VC host

· ping from ESX target to source system

Check the port usage (use telnet to verify):

· Converter application to remote physical machine - 445 and 139

· Converter application to VirtualCenter Server - 443

· Converter application to ESX Server 3.x - 443

· Physical machine to VirtualCenter Server - 443

· Physical machine to ESX Server 3.x - 443 and 902

      • If you are using Converter 3.0.1 make sure you do not have a web server using port 443 while running Converter

Check credentials and privileges:

· Ensure that each username can login to all systems (you may want to create one admin account on all systems to simply the testing)

· Ensure the user has permission to create a VM on the target system

· Ensure the user has access to LUNs on the target system

· Ensure the user has write privilege on target system storage devices

· Verify that the user can create a new VM on each target system from VirtualCenter

Verify space requirements:

· Check available file space on all systems (Depending on your method you will either need space equal to the selected drive or to the space used on the source drive.)

· Verify that the Target VMname does not exist on target system

· Optionally, turn firewall off on 3.0.1 ESX servers

Try the following steps:

1) Log onto the source machine using local admin privileges

2) Install VMware Converter on the source machine

3) Run VMware Converter

Make sure you do not have any software mirror or software raid on your disks.

If it still fails, please provide the following information by attaching the documents (please do not paste them):

1) What percentage did it fail at?

2) Logs - File - Export Log (from within converter)

3) Screen shot of the disk management screen

0 Kudos