How to Troubleshoot Orchestrator Text Issues?

News Knowledge Base
1

How to Troubleshoot Orchestrator Text Issues ?

Issue Description: In versions 20.4+, the Orchestrator font files are located in the /Identity folder. Some customer environments have security settings that block these files from being loaded onto Orchestrator. This issue can cause the text not to display correctly in Orchestrator.

Resolution: To resolve this issue, follow these steps:

  1. Try a Different Browser:

    1. Use a different browser to see if the issue persists
    2. If using Internet Explorer (IE), enable Font Download and Active Scripting.

  2. Compare HAR Files:

    1. Secure HAR files from both the non-working environment and a working one
    2. Compare the differences to identify what settings might be causing the issue.

  3. Review Browser Console Logs:

    • Check the browser console and network logs for any exceptions, specifically looking for mentions of font files like in the screenshot below:
1.png

  1. Verify IIS Settings:

    1. Navigate to the Orchestrator installation and in the Identity folder search for the listed .woff files from the browser console
    2. Ensure that the user who is used to run the Orchestrator Application Pool Identity has read and write permissions to the folder(s) housing these files
    3. Check if the files are corrupt by copying and pasting the same files from a working environment and restarting IIS.

  2. Check IIS Logs:

    1. If the issue persists, check the IIS logs to see if the requests for the .woff files are returning a 200 code or something else
    2. A 200 code indicates that IIS is successfully making the request, but something else is preventing the request from completing in the communication between the Orchestrator and the Browser.

  3. Identify Server Security Settings:

    1. Work with the IT team to identify any server security settings that might be blocking the font files
    2. In one case, in the request filtering settings, as part of the server security hardening requirements, were causing the issue. Adjusting these settings for the /Identity and /Webhooks folders resolved the problem.
2.png

  1. Review Event Viewer Logs:

    1. Gather the Application Event Viewer logs and provide them to the UiPath Product Support team for further analysis
    2. Follow the guide on How to get Application Logs from the Event Viewer for detailed instructions.