Knowledge Base

Validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

1. If the source is a physical server and is or may be a blade server, verify that the console devices are not directed at the blade during conversion. For more information, see Converting a physical blade server fails (1000508) .
2. Verify that Converter can connect to the source server to install the Converter Agent. For more information, see The agent fails to install due to a connection error (1001344) .
3. Ensure that the VMware Agent is correctly installed and running. For more information, see Verifying proper installation and functionality of Converter Agent (1006603).
4. Verify that the failure is not due to an operating system problem on the source server. For more information, see Troubleshooting damaged OS components that cause conversion failure (1006489).
5. Confirm that there is proper network connectivity between the source server, Converter, and the destination. For more information, see Checking networking connections between Converter end points (1006607).

Note: If your problem still exists after trying the steps in this article, please file a support request with VMware Support and note this KB Article ID in the problem description. For more information, see How to Submit a Support Request.