Virtual machine fails to power on with the error: File already has an encoding UTF-8

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• After importing a virtual machine using vCenter Converter 4.0, the virtual machine fails to power on.
• vSphere Client reports these errors:
• • File "<path to vmx file>" line XX: File already has an encoding "UTF-8".
  • Cannot open configuration file <path to fix file>

Environment

VMware ESX 4.0.x

Resolution

This issue occurs if the converted virtual machine was originally:

• Hosted on VMware Workstation or VMware Server.
• Converted using VMware Converter 3.0.3.

The affected virtual machines' .vmx file have the entry .encoding = "windows-1252" which is not removed by VMware Converter 3.0.3 during conversions. Subsequent conversions add the entry .encoding = "UTF-8" to the .vmx file, causing two .encoding lines to appear in the .vmx file. As a result, the virtual machine can no longer be powered on.

To resolve this issue, remove one of the .encoding lines from the virtual machines' .vmx file:

1. For ESX 4.0, login to the ESX host via the service console or SSH.
   For ESXi 4.0, login to the ESXi host via tech support mode. For more information, see Tech Support Mode for Emergency Support (1003677).
2. Open the virtual machine configuration file (.vmx) using a text editor.
3. Delete this line from the file:
   
   .encoding = "windows-1252"
   
4. Save the file and power on the virtual machine.

Additional Information

The issue is not observed in later versions of VMware Converter.