- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Robot admin guide
Session troubleshooting
The robot receives the error "Cannot bring the target application in foreground because the Windows session is locked".
Unnecessary running of idle Remote Desktop Services sessions, automatic sign-ins and lock of the last interactive user after system restarts, or the activation of news and interests on the taskbar.
Ensure the settings for the following group policies are disabled or not configured:
-
News and interests
-
Session Time Limits (find it under Remote Desktop Services > Remote Desktop Session Host )
-
Windows Logon Options
To do that:
-
Open the Local Group Policy Editor.
-
Navigate to Computer Configuration > Administrative Templates > Windows Components.
-
Look for the corresponding policy setting and verify the state is Not configured or Disabled:
-
For News and interest, look for the Enable news and interests on the taskbar setting.
-
For Session Time Limits, look for the Set time limit for active but idle Remote Desktop Services sessions setting.
-
For Windows Logon Options, look for the Sign-in and lock last interactive user automatically after a restart setting.
-
If the problem persists, export and send the following text files to UiPath Support:
-
Open the Local Group Policy Editor.
-
Navigate to Computer Configuration > Administrative Templates > Windows Components.
-
Select the following policies:
-
Connections (find it under Remote Desktop Services > Remote Desktop Session Host )
-
Session Time Limits (find it under Remote Desktop Services > Remote Desktop Session Host )
-
-
For each policy, select Action from the ribbon and then Export the settings with the
.txtformat.
In unattended scenarios, Robots are unable to log in due to a security pop-up that reports sign-in information. As a result, jobs fail with the following error message: "Could not start executor. A specified logon session does not exist. It may already have been terminated. (0x80070520)".
The policy Display information about previous logons during user logon prevents robot sessions from being created. When this policy is enabled, robots cannot initiate a login session, leading to the error message mentioned above.
Disable the Display information about previous logons during user logon policy:
-
Open the Group Policy Editor on the affected machines by running
gpedit.mscfrom the start menu or Command Prompt. -
Go to Computer Configuration > Administrative Templates > System > Logon.
-
Locate the policy titled Display information about previous logons during user logon.
-
Set this policy to Disabled.
-
Once the policy is disabled, ensure the changes are applied. You may need to run
gpupdate /forcefrom the Command Prompt or restart the affected machine. -
Test whether the robot is able to log in successfully without encountering the error.
