Troubleshooting vCenter Converter when conversion fails at reconfiguration

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• When using vCenter Converter, conversion fails between 95% and 99%.
• Reconfiguration fails to complete.
• The virtual machine is created at the destination but does not start.
• You receive one or more of these errors:
• • extendedOsInfo,190] msdos.sys is non-existent or inaccessible
  • [extendedOsInfo,203] FAILED parsing NTFS or Win9x_DOS partition
  • [diskSet,549] Guessing which volume is system volume...
  • Image processing task has failed with MethodFault::Exception:
  • sysimage.fault.OsVersionNotFound
  • sysimage.fault.ReconfigFault

Environment

VMware vCenter Converter Standalone 4.0.x
VMware vCenter Converter 4.0.x
VMware vCenter Converter Standalone 5.5.x
VMware vCenter Converter Standalone 4.3.x
VMware vCenter Converter Standalone 5.0.x
VMware Converter 3.0.x
VMware vCenter Converter 4.1.x
VMware vCenter Converter 4.2.x

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. Verify that the boot.ini file is valid and compatible on the source system. Repairing the boot.ini may be required if vCenter Converter is unable to recognize the operating system. For help troubleshooting and repairing this file, see Using vCenter Converter conversion fails at 99% with the error: Unable to determine guest OS or sysimage.fault.OsVersionNotFound (1001610).
   
   
2. Check for missing files or drivers on the source server that are required during reconfiguration. Examine the log files to see what files are required. For more information, see Troubleshooting missing drivers or Windows file errors that can cause vCenter Converter to fail during reconfiguration (1006858).

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.

Additional Information