We are currently running robot version 20.4.5 and last night I attempted to upgrade to 21.10.3. The upgrade was successful and everything was running and the Orchestrator could see all the robots.
We run a HD setup where a single Windows Terminal Server hosts all the robots and this has worked perfectly for the 3 years we have been running UiPath.
We also switch all of our processes that do not use UI interactions to Background processes so the majority of them are background processes that run on Unattended bots.
Following the upgrade, all our automations failed to execute. The reason for this was that when they were running, rather than running under the ‘robot user’ account they were running under a user NT AUTHORITY\LOCAL SERVICE.
Previously in 20.4.5, the background processes ran under a robot user, even though they were running in Session 0 and the UiPath documentation indicates that this is exactly what should happen. As a result we have a number of these automations that run out SQL selects and use the robot account to do this. There is no UI interaction so so need for the automation to log in.
With the new version, the automations fail because NT AUTHORITY\LOCAL SERVICE is not an authorised user of the database.
We have had to roll back to 20.4.5 which is working, however we need to understand this issue in order to upgrade. Is anyone able to help? Do we need to be on Modern Folders or something to make sure the Background processes can run under a given user?
I am afraid not, however it does look like it’s related to the Process setup but the menu item to do the setup is only available when you use Modern Folders.
I am going to have to install another copy to try and figure it out
Sure thing. Please have a look at this screenshot
Image_2021-12-23_15-20-49
1268×952 93.6 KB
I have been informed by support that this is where you must configure the setup
Starting with the 2021.10 release, running unattended background automations on service-mode robots run by default under the built-in "Local Service” Windows user. Prior to this, the username and password configured for the robot in Orchestrator were used.
To use credentials specified in Orchestrator, you need to configure the
UIPATH_HEADLESS_WITH_USER
environment variable and set the value to
True
.
More information can be found in the
running background processes
document.
