Dynamics Community Forum Thread Details

Prerequisite Validation throwing "Unable to translate Unicode character \uDE57 at index 61 to specified code page."

I have a Win2012 Server Standard (v 6.3, build 9600) that already has AX Client installed from an existing AX 2012 R3 install folder. We want to re-install the client. I ran the Prerequisite Validation for "Client" only, and the setup is failing with JIT error:

************** Exception Text **************
System.Text.EncoderFallbackException: Unable to translate Unicode character \uDE57 at index 61 to specified code page.
at System.Text.EncoderExceptionFallbackBuffer.Fallback(Char charUnknown, Int32 index)
at System.Text.EncoderFallbackBuffer.InternalFallback(Char ch, Char*& chars)
at System.Text.UTF8Encoding.GetBytes(Char* chars, Int32 charCount, Byte* bytes, Int32 byteCount, EncoderNLS baseEncoder)
at System.Text.EncoderNLS.GetBytes(Char* chars, Int32 charCount, Byte* bytes, Int32 byteCount, Boolean flush)
at System.Text.EncoderNLS.GetBytes(Char[] chars, Int32 charIndex, Int32 charCount, Byte[] bytes, Int32 byteIndex, Boolean flush)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Dispose(Boolean disposing)
at System.IO.TextWriter.Dispose()
at System.IO.TextWriter.SyncTextWriter.Dispose(Boolean disposing)
at System.IO.TextWriter.Dispose()
at Microsoft.Dynamics.AX.PrerequisiteUtility.PrereqUtilLogger.LogMessage(String message)
at Microsoft.Dynamics.Setup.PrereqAssembly.Utilities.LogMessage(Verbosity verbosity, String message)
at Microsoft.Dynamics.Setup.PrereqAssembly.MSIPackageCheck.Execute()
at Microsoft.Dynamics.Setup.PrereqAssembly.Prerequisite.Execute()
at Microsoft.Dynamics.Setup.PrereqAssembly.PreReqCollection.PerformAsyncPrereqChecks(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

This same installation folder works fine on another VM of ours, so I suspect the issue is with this particular VM. When I try to install client ayways, it throws this error, I suspect root issue is same as this one.

Any idea?

Quick Links