Issues post Orch 22.4.1 Upgrade - Timeouts

Help Orchestrator
,
1

Has anyone experienced a large spike in app exceptions after updating On-Prem Orch from 21.10.3 to 22.4.1? We went from averaging 3-4% app exceptions daily to immediately 6-7% app exceptions. We process around 40,000 transactions daily, so this is a very large spike. No other changes were made at the time of upgrade. Most errors seem to be “Timeout reached”. I’m still working on exact numbers, but just curious if anyone else has experience the same and how you solved. TIA!

2

Based on Prerequisites for Installation

image
image1020×269 15.5 KB

<add key="Database.IsolationLevel" value="ReadCommitted" /> in C:\Program Files (x86)\UiPath\Orchestrator\UiPath.Orchestrator.dll.config

The query should be ALTER DATABASE orchdb SET READ_COMMITTED_SNAPSHOT ON

Let us know if this helped.

3

“READ_COMMITTED_SNAPSHOT” was already “ON” on the database, however, UiPath.Orchestrator.dll.config does not have the Database.IsolationLevel key present. What is the default value of this key? If the default is already “ReadCommitted”, I do not expect any improvement. I will have to wait until the weekend to restart IIS, else I would just go ahead and add the key.

4

Can we get the documentation update to include the Database.IsolationLevel and it’s default value? I don’t see it mentioned in the latest

5

Asked internally to update the documentation.

6

This did not resolve the issue.