Converter 5.1 - Error 2338

Hi,

I have several VM's on 2 locations, one datacenter that is managed by us on our site and several VM's hosted on external hosting company datacenter.
Our own platform runs for now version 4.3 and the remote location run 5.1
I need to import few VM's from the remote location to our own location and trying to do that using Converter 5.1 hot-cloning.

The converter is installed on dedicated VM with external NIC that is reachable from the remote location and internal NIC that is connected to the vcenter and the ESXi hosts.
The converter is able to connect to the remote VM and get all settings done, but when I'm trying to run it, it fails at 1% with the error "Platform specific error 2338"

I checked the logs and so far was able to find out only those errors:
warning 'Default'] Disk number 1 has been skipped because of errors while reading partition table
warning 'Default'] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted
warning 'Default'] [MoveActiveDiskIfNeeded] GetFirstBootDisk failed, mntapi error: 176
warning 'Default'] Partition:Invalid sector magic number
warning 'Default'] [PopulateCapabilities] Volume-based cloning was disabled due to: <no volumes are recognized>

Any idea what can be the problem here and how it can be resolved?
I saw that those errors are mentioned with Converter 4.3, but I'm using Converter 5.1
The source VM is Windows 7SP1

Attaching the log for more information.
Any help will be highly appreciated
cloudbaseAsked:
Who is Participating?
 
AbhishekJhaConnect With a Mentor Commented:
0
 
cloudbaseAuthor Commented:
0
 
Zephyr ICTCloud ArchitectCommented:
Few things:

- Did you run a chkdsk on the source machine?
- Is any anti-virus/backup software running on the source machine?
- De-install - reboot - re-install the converter agent.
- Try with disabling ssl: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2020517

These things can take time to troubleshoot, if you have the possibility to cold-clone, that might be a better option if it keeps failing.
0
 
vmwarun - ArunCommented:
1.Check the free space on %TEMP% directory of the source VM.
2.Is name resolution working fine on the source?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.