Log for VMware Converter Enterprise Client, pid=4376, version=4.0.1, build=build-103517, option=Release, section=2
Current working directory: C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\Converter Enterprise 4.0.1
HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2.
HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 2 logical CPUs.
Using system libcrypto, version 90709F
Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
Making sure that UFAD interface has version vmware-converter-4.0.1
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
UFAD interface version is vmware-converter-4.0.1
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Connecting to host resvavc01.vastera.com on port 443 using protocol https
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Making sure that UFAD interface has version vmware-converter-4.0.1
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
UFAD interface version is vmware-converter-4.0.1
Successfully connected to VMImporter
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Making sure that UFAD interface has version vmware-converter-4.0.1
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
UFAD interface version is vmware-converter-4.0.1
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Connecting to host resvavc01.vastera.com on port 443 using protocol https
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Connecting to IPC$ on 10.6.6.28 as vastera\sirakm
Successfully connected to IPC$ on 10.6.6.28
Connecting to
10.6.6.28\pipe\vmware-converter-vmdb, use SSL: true
Failed to connect to
10.6.6.28\pipe\vmware-converter-vmdb. Reason: The system cannot find the file specified. . Error code: 2.
Starting vmware-converter on 10.6.6.28
Failed to open service handle to with access level 983103: 1060
Failed to startup VMware Converter Agent service on 10.6.6.28. Reason: Service control manager error.
Unable to start vmware-converter service
Connecting to
10.6.6.28\pipe\vmware-converter-vmdb, use SSL: true
Failed to connect to
10.6.6.28\pipe\vmware-converter-vmdb. Reason: The system cannot find the file specified. . Error code: 2.
Starting vmware-converter on 10.6.6.28
Failed to open service handle to with access level 983103: 1060
Failed to startup VMware Converter Agent service on 10.6.6.28. Reason: Service control manager error.
Unable to start vmware-converter service
Connecting to
10.6.6.28\pipe\vmware-converter-vmdb, use SSL: true
Failed to connect to
10.6.6.28\pipe\vmware-converter-vmdb. Reason: The system cannot find the file specified. . Error code: 2.
Starting vmware-converter on 10.6.6.28
Failed to open service handle to with access level 983103: 1060
Failed to startup VMware Converter Agent service on 10.6.6.28. Reason: Service control manager error.
Unable to start vmware-converter service
Giving up trying to connect to
10.6.6.28\pipe\vmware-converter-vmdb
Task failed: P2VError UFA_NOT_RUNNING()
Installing UFAD to hostname=10.6.6.28, username=vastera\sirakm, postponeReboot=1
Connecting to ADMIN$ on 10.6.6.28 as vastera\sirakm
Successfully connected to ADMIN$ on 10.6.6.28
MakeSafeDirectory: directory exists, skipping safety check
MakeSafeDirectory: directory exists, skipping safety check
MakeSafeDirectory: directory exists, skipping safety check
Starting service with args: com.vmware.courier-fsdkcipdicxitmbg
Sending control 1 to service failed: 1062
Connecting to IPC$ on 10.6.6.28 as vastera\sirakm
Successfully connected to IPC$ on 10.6.6.28
Connecting to
10.6.6.28\pipe\vmware-converter-vmdb, use SSL: true
Successfully connected to
10.6.6.28\pipe\vmware-converter-vmdb
Unsetting unknown path: /vmomi/
Making sure that UFAD interface has version vmware-converter-4.0.1
UFAD interface version is vmware-converter-4.0.1
Successfully connected to VMImporter
Successfully connected to VMImporter
Successfully connected to VMImporter
Successfully connected to VMImporter
Making sure that UFAD interface has version vmware-converter-4.0.1
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
UFAD interface version is vmware-converter-4.0.1
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Connecting to host resvavc01.vastera.com on port 443 using protocol https
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs resvavc01.vastera.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Connecting to IPC$ on 10.6.6.31 as vastera\sirakm
SMB manager: Error connecting to share http://\\10.6.6.31\IPC$: 1203
Failed to connect to IPC$ on 10.6.6.31. Reason: Unspecified error in remote execution mechanism
You have confirmed that there is no firewall service running on the physical machine you are trying to P2V
Yes, I have confirmed that. Both servers are on he same segment (VLAN) of a switched network with no firewall. The Windowws firewall is not running. The TCP/IP helper service and volume shadow copy service are both running.
are you using the latest version VM converter 4 which is built in on the ESX 3.5 update 2? that will provide better success rate. By the way, to work around this, usually I will reinstall the converter agent on the physical machine. Not only that, I also find that some VM may have problem with the update manager agent. By reinstalling that, it solved the problem most of the time.
I had the same problem. I installed the VC-Client and started the import process from a Server, which was in the same network.
Can you open a Windows-Share (for example <Your Destination System>\c$) from your VC-Client PC?