Physical to virtual (P2V) conversion fails with the error: A general system error occurred. Found dangling SSL error
Article ID: 304481
Updated On:
Products
VMware
Issue/Introduction
Symptoms:
- Physical to virtual (P2V) conversion fails.
- You see the error:
A general system error occurred. Found dangling SSL error
Note: This occurs on both Converter standalone 4.3 build 292238 and vCenter Server 4.1 converter plugin versions.
- The Converter server log and vmware-converter-server-1.log contains entries similar to:
[#18] [2011-06-28 15:21:11.451 05872 error 'App'] Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1)
[#18] [2011-06-29 10:47:02.232 04796 info 'App'] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded
[#18] [2011-06-29 10:47:02.232 04796 info 'vmomi.soapStub[16]'] Resetting stub adapter for server PIPE:\\.\pipe\vmware-converter-worker-soap : Closed
[#19] [2011-06-29 10:49:02.591 04608 error 'App'] Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1)
[#19] [2011-06-29 10:51:02.373 05984 info 'App'] [diagnosticManager,357] Generating Converter.Server log bundle.
- The Converter worker log and vmware-converter-worker-1.log contains entries similar to:
[#18] [2011-06-29 10:50:34.904 04732 warning 'App'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server host.domain.abc failed: No such host is known
[#18] [2011-06-29 10:50:34.904 04732 info 'App'] [,0] Error 2338 opening disk vpxa-nfc://[VMFS02]
Environment
VMware vCenter Converter Standalone 5.0.x
VMware vCenter Converter Standalone 4.3.x
VMware vCenter Converter Standalone 5.1.x
VMware vCenter Converter 4.2.x
VMware vCenter Converter Standalone 4.0.x
VMware vCenter Converter 4.1.x
VMware vCenter Converter Standalone 4.3.x
VMware vCenter Converter Standalone 5.1.x
VMware vCenter Converter 4.2.x
VMware vCenter Converter Standalone 4.0.x
VMware vCenter Converter 4.1.x
Cause
Resolution
This issue may occur if you have name resolution problem on your physical server.
To resolve this issue, ensure your DNS settings are configured properly on your physical server:
To resolve this issue, ensure your DNS settings are configured properly on your physical server:
- Verify that your DNS server is running and not malfunctioning and you are able to resolve DNS from the source to vCenter Server and the ESX host. In a Microsoft Active Directory environment, this is generally your Domain Controller.
- Attempt to ping your Domain Controller by hostname. If the ping fails, attempt to ping the machine by IP address. For more information, see Testing network connectivity with the ping command (1003486).
- If you can ping your Domain Controller but DNS queries are failing, check to see that your guest machine is set to use the Domain Controller as its preferred DNS servers.
- Click on Start > Run and type control netconnections.
- Right click on the active network adapter for physical server and click Properties.
- Select the item in the list for Internet Protocol (TCP/IP), and click Properties.
- Select the radio button for Use the following DNS server addresses.
- Check to see if the IP addresses match those for your Domain Controller/Active Directory Integrated DNS server, and if not, add the IP addresses of your Active Directory servers.
- Ensure that the hosts file entries do not conflict with DNS. If a hosts file is configured locally, any host name-to-address mappings are loaded from that file when the DNS client starts and may cause issues with resolution locally.
To verify this behavior:
- Click Start > Run, type %systemroot%/system32/drivers/etc/, and click OK.
- Open the hosts file using a text editor.
- Look for lines similar to:
<ip address associated with hostname> <hostname in your environment>
For example:
127.0.0.1 localhost
- If information here conflicts with information that should be in DNS, remove it and allow your DNS server to be authoritative for name-to-address mappings.
Additional Information
Feedback
Yes
No
Powered by
