When executing etautil commands containing local non-US characters in a Windows command prompt, scripts fail because characters are misinterpreted. This occurs when the command shell environment character encoding does not align with the command input.
Identity Manager 14.5
The issue occurs because the default Windows command shell code page (e.g., 437 for US English) does not support characters outside the standard ASCII range (0-127). When etautil processes commands containing these characters, the input is misread. You can verify the active code page by running chcp in the command prompt.
Use one of the following solutions to resolve the character encoding issue:
Solution 1: Update the Console Code Page Change the active console code page in your batch script to support your local character set.
chcp command followed by your specific code page identifier (e.g., 1252 for Western European).etautil command immediately following the code page change.Example:
Solution 2: Process via Input File Use the -f flag to process instructions from a text file. This prevents the command shell from translating characters before they reach the etautil tool.
inputfile.txt) containing the full etautil update statement.etautil with the -f flag pointing to the input file.Example:
To speak with a customer representative or a Support Engineer see . Scroll to the bottom of the page and click on your respective region.