The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)
View by Article ID
Troubleshooting errors resulting from non-ASCII names
Symptoms
Importing a virtual machine fails.
VMware VirtualCenter fails to start.
You may see one or more of these errors:
Unhandled exception: not well-formed (invalid token).
P2VError UFAD_SYSTEM_ERROR(Invalid response code: 400 Bad Request).
vmware-ufad.exe died on startup, check your %TEMP% setting
Invalid SOAP request: not well-formed (invalid token).
Task failed: not well-formed (invalid token).
Unknown error generated from client (Catchall).
An unexpected error occurred!
Microsoft JET Database Engine Error.
Syntax error in UPDATE statement.
User DOMAIN\username could not be allocated a VM for desktop DESKTOP_NAME - reason: No responses received
Failed to establish Vim connection
Secure connection to the VDM server has been dropped
A VDM client is closing down
The tunnel initiation failed
Folders with Non-ASCII characters show as blank folders using the Browse datastore option.
You may see the error:
['vcbMounter' 3356 error] Error: Other error encountered: at line number 7, not well-formed (invalid token)
Purpose
This article explains why certain error messages appear in various VMware products. The article also provides suggestions on how to avoid the issue.
Note: This issue can cause secure connections in Virtual Desktop Manager (VDM) to fail.
Resolution
This issue is caused by the ASCII to 8-bit Unicode Transformation Format (UTF-8) string conversion. If any of these fields contain a non-standard US-English ASCII character it can cause unexpected behavior to occur:
Annotation
Display name
Floppy image name
Parallel port file name
Serial port file name
CD-ROM ISO name
Remote computer names
VMware Converter specific issues:
Environment variables on the source server, such as TMP, and TEMP. Use the SET command to verify your environment variables.
The paths to the Documents and Settings and Program Filesfolders on the source server
Non-ASCII characters used in folders on vmfs datastores presented to ESX hosts are not currently supported. Change the folder name to use ASCII characters only.
To ensure that you do not run into the error, these fields cannot contain any non-standard US-English ASCII characters. Any characters other than ASCII 33 - 127, such as special French, Russian, or Japanese characters may produce one of the errors referenced in this article.
Additional Information
With certain versions of VMware Converter you may experience this error when starting the application:
Microsoft Visual C++ Runtime Library - Runtime Error!
To resolve this issue:
Install the latest version of VMware Converter.
Verify that the user name does not contain ! or & or non-ASCII characters. For more information, see the VMware Converter 3 Release Notes.
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.
