when a failure occurs at 98% usually the machine has copied over, the vmdk's have been created at the target sight.
you should be able to navigate to the target location and manually create your machine by building a new Win2K3 64bit Guest and mounting the already existing VMDKs as its disks.
Conversion has 2 phases - cloning the data and reconfiguration. Cloning has finished successfully and your VM has all the data (the VM is created at the destination in the beginning of the conversion, there is no need to recreate it). First just try to power it on. If it succeeds , you are lucky :-) It it does not (e.g. BSOD), the errors in the log are:
2013-07-01T16:56:00.460-04:00 [03188 error 'task-3'] Error 2 (opening key) saving registry key mntApi163093493130307997\ControlSet001\Services\rhelfltr into \\.\vstor2-mntapi20-shared-6E126F12000010000000000005000000\WINDOWS\$Reconfig$\mntApi163093493130307997-ControlSet001-Services-rhelfltr-reg
2013-07-01T16:56:00.507-04:00 [03188 error 'task-3'] Error 2 (opening key) saving registry key mntApi163093493130307997\ControlSet001\Services\rhelnet into \\.\vstor2-mntapi20-shared-6E126F12000010000000000005000000\WINDOWS\$Reconfig$\mntApi163093493130307997-ControlSet001-Services-rhelnet-reg
2013-07-01T16:56:00.507-04:00 [03188 error 'task-3'] Error 2 (opening key) saving registry key mntApi163093493130307997\ControlSet001\Services\rhelscsi into \\.\vstor2-mntapi20-shared-6E126F12000010000000000005000000\WINDOWS\$Reconfig$\mntApi163093493130307997-ControlSet001-Services-rhelscsi-reg
2013-07-01T16:56:00.538-04:00 [03188 error 'task-3'] Error 2 (opening key) saving registry key mntApi163093493130307997\ControlSet001\Services\coherence into \\.\vstor2-mntapi20-shared-6E126F12000010000000000005000000\WINDOWS\$Reconfig$\mntApi163093493130307997-ControlSet001-Services-coherence-reg
2013-07-01T16:56:00.554-04:00 [03188 error 'task-3'] Error 2 (opening key) saving registry key mntApi163093493130307997\ControlSet001\Services\toolsrv into \\.\vstor2-mntapi20-shared-6E126F12000010000000000005000000\WINDOWS\$Reconfig$\mntApi163093493130307997-ControlSet001-Services-toolsrv-reg
which do not seem critical (I think these were error during making backups of the registry keys
and:
2013-07-01T16:56:00.679-04:00 [03188 error 'task-3'] Could not find symmpi.sys in \\.\vstor2-mntapi20-shared-6E126F12000010000000000005000000\WINDOWS\Driver Cache\amd64\sp2.cab
2013-07-01T16:56:00.788-04:00 [03188 error 'task-3'] Could not find symmpi.sys in \\.\vstor2-mntapi20-shared-6E126F12000010000000000005000000\WINDOWS\Driver Cache\amd64\driver.cab
2013-07-01T16:56:00.788-04:00 [03188 error 'task-3'] Unable to find symmpi.sys in the specified CAB files
I don't know why the Windows doesn't have symmpi.sys in its driver cache. What you may do as a workaround is to mount the vmdk of the converted Windows in another Windows VM and copy this file (e.g. from another Windows machine) to \Windows\System32\drivers folder in the mounted disk.
This is a bit hackerish but easy to do:
- edit settings of the VM you will mount the vmdk; add the vmdk file as an existing disk.
- go to OS console. Disk manager in Windows will automatically recognize the new disk. Just mount it to a drive letter and copy the file.
- remove the vmdk from the VM without deleting it from disk!
HTH
Plamen
Have you try to run the destination VM? What the result is?
Now I install Converter Standalone Client 5 on windows 7 Sp1 64bit
But when opening see message :
config file error: not well-formed (invalid token) (Line 4)
and this a log event for error:
Faulting application name: converter.exe, version: 8.1.0.15346, time stamp: 0x51642626 Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9 Exception code: 0x40000015 Fault offset: 0x0005beae Faulting process id: 0x598 Faulting application start time: 0x01ce78c1be883441 Faulting application path: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\converter.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll Report Id: 16eb6cdd-e4b5-11e2-ab85-005056c00008
Is there old converter installed? If yes - first remove it.
Othervise please send a logs, to see the exact error.
Thanks POCEH The log is already in first discussion
Faulting application name: converter.exe, version: 8.1.0.15346, time stamp: 0x51642626 Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9 Exception code: 0x40000015 Fault offset: 0x0005beae Faulting process id: 0x598 Faulting application start time: 0x01ce78c1be883441 Faulting application path: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\converter.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll Report Id: 16eb6cdd-e4b5-11e2-ab85-005056c00008
Where is the first discussion? Please attach the link.
vCenter: 5.1.0
Standalone Converter: 5.1.0
ESXi : 5.1
I am unable to complete any P2V conversions with vCenter Standalone Converter. I get the error message "Unable to obtain hardware information for the selected machine" every time I run the converter. I have used 'Run as Administrator,' rebooted source system, and rebooted vCenter server with no luck. Any ideas will be greatly appreciated.
Thanks!
What's your Windows version? If it Vista+ try to turn off UAC. HTH
It was my understanding that if you have an Enterprise Plus license for ESX, the cold clone CD was available to you with Converter, but I dont see it under the Converter downloads.
We are going to be doing some P2Vs soon and I would like to have the CD on hand just in case we need it.
Can anyone point out its secret location? 
Thanks!
Windows Server 2008 R2 SP1, I have the UAC turned off on the 2 servers. I am able to complete the conversion if I install the Standalone Converter on the local server and run it, but I would prefer to run it from a server/workstation and be able to monitor all the jobs at once from a centralized location.
Sorry POCEH
But whats log you mean? Because I mean the event log
Faulting application name: converter.exe, version: 8.1.0.15346, time stamp: 0x51642626 Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9 Exception code: 0x40000015 Fault offset: 0x0005beae Faulting process id: 0x598 Faulting application start time: 0x01ce78c1be883441 Faulting application path: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\converter.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll Report Id: 16eb6cdd-e4b5-11e2-ab85-005056c00008
You need to use local administrator account and UAC disabled to do P2V on remote Windows, also ensure 'Use Sharing Wizard' disabled.
From you *multiple* posted even I can see only that your MSVCRT is not the requested version 9.0.30729.4148
HTH
Sorry POCEH
But how can I resolve this problem
Cold clone CD is not available anymore (it was last available with version 4.1 IIRC, but itself is version 3) and has been removed from downloads.
There were some posts in the forum with links to 3rd party 'secret locations'.
Regards
It might well be that config file error and MSVCR90 version are unrelated.
Why don't you try to completely remove converter installation and then install it anew?
you could down load MOA by Ulli
http://www.sanbarrow.com/moa.html
This is a very good Coldclone replacement
Hello,
I'm back with log file. Log contains only situation related to this topic. Before starting new conversion operation I've removed all previous logs.
Regards
EDIT: I've checked worker log file and this information:
[PopulateVolumeProperties] volume \\?\Volume{90f40b30-30cd-11e2-849d-000c29da83b7}\ corresponds to \Device\HarddiskVolumeShadowCopy1 device name.
mem> 2013-07-07T22:40:47.140+02:00 [06288 info 'Default'] [GetDriveLetterOrMountPoint] Mount point for volume \\?\Volume{90f40b30-30cd-11e2-849d-000c29da83b7}\ is \\?\Volume{90f40b30-30cd-11e2-849d-000c29da83b7}\
mem> 2013-07-07T22:40:50.881+02:00 [06288 panic 'Default'] (Log recursion level 2) Win32 exception: Access Violation (0xc0000005)
showed me where the problem is. I've runned diskshadow.exe, and performed delete shadows all operation. Now I can move forward with conversion. Thanks
I recently upgraded a CentOS 5 system to 6.4 on bare metal. I've been backing up by rsync'ing the system to both a local USB drive and a remote system's USB drive. The backup is a snapshot of the live system's filesystem, which is spread across a couple of LVM mounts (plus an LVM swap).
I'm now trying my hand at VMware and have another identical server running offsite and loaded with ESXi 5.1. It seems like I should be able to take my USB image and convert that to a virtual server on this second system. I downloaded and installed Converter but don't see any options for my situation. Do I need to take this server to the site and convert from the running server? Or is there some way to turn my filesystem snapshot into something that Converter can use? It looks like Converter can convert from a virtual filesystem, so is there some tool that can turn a snapshot into a virtual filesystem?