Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Troubleshooting when vCenter Converter fails to complete a conversion of a physical or virtual machine (1006284)

Symptoms

  • vCenter Converter does not complete during the conversion process.
  • The Converter Agent does not install properly.
  • The free disk space or used disk space reported in the New Conversion wizard is incorrect.
  • You are unable to initiate a connection to a physical or virtual machine to convert.
  • You receive one or more of these errors:
    • Operating system could not be found
    • Unable to determine guest operating system
    • Unable to read OS info from system disk: sysimage.fault.PlatformError
    • VmiQuerySourceInfoTask::task{0}: Image processing task has failed with MethodFault::Exception: sysimage.fault.UnableToDetermineGuestOs
      Failed to get info for \\.\PhysicalDrive0: error Reading disk \\.\PhysicalDrive0's geometry: The device is not ready (21)
    • Fatal error occurred. The most common reason for this is loss of network connection. The wizard will now be closed.
    • Failed to connect to \\<hostname>\pipe\vmware-ufad-p2v30-vmdb .
      Reason: The network path was not found. . Error code: 53.
    • Error 1219: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
    • Failed to take snapshot of the source volume
    • stcbasic.sys not installed or snapshot creation failed. err=2
    • vsnap does not have admin rights
    • Error opening disk device: Incorrect function (1)
    • Failed to get capacity for \\.\PhysicalDrive0 : error opening disk device: Incorrect function (1)
    • sysimage.fault.OsVersionNotFound
    • Warning: no attached disks were detected.
    • The COM Server with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} and name SW_PROV cannot be started. [0x80070422]
    • Unknown error returned by VMware Converter Agent
    • P2VError UFAD_SYSTEM_ERROR(Internal Error)
    • Failed to connect
    • Giving up trying to connect
    • Failed to establish Vim connection to hostname.domain.com.
      Vmacore::Exception: The requested name is valid, but no data of the requested type was found.
    • Image processing task has failed with MethodFault::Exception: sysimage.fault.IncompatibilityFault
    • ERROR: Unable to open file %s
    • [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server hostname.domain.coml failed: The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
    • sysimage.fault.FileOpenError
    • Task failed: P2VError FILE_OPEN_FAILED
    • Unable to find server

Resolution

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. Do not skip a step.  
  1. Confirm that there is proper network connectivity between the source server, vCenter Converter, and the destination. For more information, see Verifying and troubleshooting networking connections that may cause vCenter Converter to fail (1006607).

  2. Verify that vCenter Converter can connect to the source server to install the Converter Agent. For more information, see vCenter Converter Agent fails to install due to a connection error (1001344).

  3. Ensure that the Converter Agent is correctly installed and running. For more information, see Ensuring proper installation of vCenter Converter and functionality of the 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 operating system components that can cause conversion failures with vCenter Converter (1006489).

  5. If you have teamed NICs on your vCenter Server, ESX/ESXi hosts, and your source system, ensure that the NIC team is working properly. VMware Converter may be unable to determine the target and/or source server if the NIC team has failed over or is not communicating. For help troubleshooting this issue, see NIC team failover, failback, or vMotion results in loss of network connectivity (1003969).

  6. If the source is a physical blade server, verify that the console devices are not directed at the blade during conversion. For more information, see Converting a physical blade server with vCenter Converter fails (1000508) 
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.

Tags

conversion-converter  conversion-wizard  converting-server  converting-server-fails  converting-vm  converting-vm-fails  convert-machine  convert-machine-fails  converter-windows-fails  converter  converting-virtual-machine  converting-virtual-machine-fails  converting-virtual-machine-corrupt-disk  convert-linux-fails

Update History

01/22/2014 - Added 5.5.x to product versions 08/17/2012 - Updated for 5.x 04/26/2011 - Included information about NIC teaming, and additional error messages.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 10 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 10 Ratings
Actions
KB: