Command output including non-Ascii characters are incorrectly displayed in application scheduler

When utilizing the application scheduler on some Non-English versions of Windows, commands that output non-ascii characters (e.g. Umlaut in German) may cause the following issues:

• Non-Ascii characters in event id 10200 are not displayed correctly in the event viewer
• Non-Ascii characters in event id 10200 may not be stored in the built-in PostgreSQL database

Problems with character translations usually occur when the main code page of Windows detected by the agent differs from the code page set in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\OEMCP.

To determine whether there is a code page mismatch, follow these steps:

1. Restart the EventSentry agent (EventSentry service)
2. In the event viewer, open the Application event log and look for event 1014 from the event source EventSentry
3. In the event, note down the detected code page (e.g. 437, 850, 1252, ...)
4. Open the command prompt and execute chcp

If the output from chcp doesn't match the code page reported in event 1014, then this may cause issue with the application scheduler and some validation scripts.

To resolve this issue follow these steps:

1. Open regedit.exe
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage
3. The value of OEMCP should reflect the output of the chcp command. Change it to the value shown in event 1014.
4. Restart Windows

After restarting, open the command prompt again and execute chcp, the reported code page should now match the value shown in EventSentry's event 1014.