- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Integrations
- Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors
Frequently Encountered Orchestrator Errors
This error is occasionally encountered when trying to get assets or queue items during workflow execution. This happens due to a Transport Layer Security failure for Windows devices attempting a TLS connection to a device that does not support Extended Master Secret. This is not an Orchestrator issue. Find here more details on the matter and how to mitigate it.
This error is encountered if the username provided for the Robot does not coincide with the one used on the Robot machine. For more information on how to connect the Robot or Orchestrator correctly, see the Connecting Robots to Orchestrator page.
It can occur when you are trying to start a job directly from the Robot machine (from the tray or Studio), and the machine username is not the same as the one used to connect the Robot to Orchestrator. For example, if you connected the Robot to Orchestrator using the ABC username, you cannot start jobs on the Robot from the tray or Studio using a different user, such as XYZ.
Uipath.LicenseTool.exe
to deactivate the Robot license and reconnect to Orchestrator.
This occurs when you tried to start a job on a Robot for which the credentials (the username and/or password) provided in Orchestrator are incorrect.
domain\username
format.
The error is thrown if the Robot password is not provided. To add the password, make sure you add machine credentials when enabling unattended automation capabilities for an account.
This error is displayed if you are trying to run a process on an Attended Robot from Orchestrator.
Executor Start Process Failed, Reason: A Specified Logon Session Does Not Exist. It May Already Have Been Terminated
There are two types of occurrences:
A. Every time you try to start the Robot - This means that a logon session cannot be created at the moment. This happens if you are connected to the Robot machine with a different username with RDP. To avoid this error, sign off all the RDP connections on the Robot machine.
B. Randomly - In this case, you can attempt the following:
- Check if the Robot machine has enough resources (CPU, Memory).
- Check the connection time using the
mstsc
command-line function. If the 60 seconds timeout period expires, the error is displayed.
An Existing Connection Was Forcibly Closed by the Remote Host “Oops! We’re Sorry! It Seems Orchestrator Is Down.”
This issue can occur in the following cases:
- The server is restarted in Internet Information Services (IIS).
- The server is shut down.
- The connection to the server is suddenly lost.
Encountered if, in Orchestrator, you start and kill a job quickly, while the process is still being downloaded on the Robot machine.
The issue occurs when the connection between the Robot and Orchestrator is lost for a scheduled job with the Terminate After option enabled.
This error is displayed in the following cases:
A. Projects containing UI Automation - when a RDP connection already exists in the background (minimized).
B. As a known Windows issue.
enableLowLevel
tracing option and provide the generated .etl file to our support team.
The issue occurs whenever the RDP connection to the Robot machine is lost. Learn how to avoid this by Executing Tasks in a Minimized RDP Window.
This is caused by an external issue.
"An attached device is not working for one of these reasons: (1) it is switched off, or connected improperly; (2) the floppy disk and drive types are incompatible; (3) the floppy disk is not properly inserted in the drive; (4) the drive door is open; or (5) the floppy disk is not properly formatted."
Executor Start Process Failed, Reason System.Runtime.InteropServices.COMException (0x800700AA): The Requested Resource Is in Use
logIntoConsole
parameter in the UiPath.settings
file is set to true
while using High-Density Robots.
Execution Error: System.UnauthorizedAccessException: Access to the Path 'C:ProgramDataUiPath…is Denied
This error is encountered in the following situations:
A. If High-Density and regular Robots write or modify the same file. To avoid this, generate different files for Robots and unique user IDs.
B. If a Robot does not have write permissions for the target folder.
C. If the file has been created and the Robot cannot edit it.
This issue occurs when schedules overlap (2-3 schedules start at the same time).
The issues occur when not all users on a machine are connected as Robots to Orchestrator.
Check the Robot LAN Settings for an enabled proxy server. If a proxy server is specified, check out how Redirecting Robots through a Proxy Server works.
This error can occur when you execute processes created prior to 2018.3.
Core.Activities
. When you run them in the current version, you must use a Core.Activities
meta-package that migrates the activities using the new System and UIAutomation packages.
Core.Activities
package is not published anywhere, so the migration meta-package is used. However, if the legacy Core.Activities
was published on custom feeds or Orchestrator by users, the legacy package is installed, which exhibits this error.
Core.Activities
package from any custom feed before trying to execute the process again. Also, remember to check out how to Open Projects Created with Previous Versions.
UiPath.UIAutomation.Activities
package.
UiPath.UIAutomation.Activities
dependency version 18.3.6864.20582 you must open them in Studio and the UiPath.UIAutomation.Activities
dependency must be updated to the 18.3.6877.28298 version.
UiPath.Core.Activities
dependency from the following locations:
- The Orchestrator feed
- The default packages location -
%Program Files (x86)%\UiPath\Studio\Packages
in versions prior to 2021.4 or%Program Files%\UiPath\Studio\Packages
starting with version 2021.4 - The NuGet cache -
%userprofile%\.nuget\packages\uipath.core.activities
UiPath.UIAutomation.Activities
package is not deployed locally or on your Orchestrator feed, then you can upgrade to v2018.3.2 without any risks.
UiPath.UIAutomation.Activities
with version less or equal than 18.3.6864.20582, and UiPath.Core.Activities
with version less or equal than 2018.3.6864.20598.
This error can occur when trying to access Orchestrator, due to a browser persistent cookies issue.
To solve or avoid this issue, clear the cookies in your browser. For example, for Chrome browsers, follow these instructions to clear the cookies, making sure you select All time as time range. Internet Explorer or Firefox browsers also have detailed instructions on how to delete the cookies.
Bad Request - Request too long
- HTTP Error 400. The size of the request headers is too long.
response, it is likely that the token signing certificates don't match on each node in a high availability configuration.
UiPath.Orchestrator.Core.Exceptions.BadRequestException: Error code - 1413, Message - 'The user is not a member of the specified
AD domain.'
True
.
To correct it, follow these steps:
- In IIS Manager, select your Orchestrator website and then navigate to Application Pools.
- From the list of application pools, right-click Identity or Orchestrator and select Advanced Settings. The Advanced Settings window is displayed.
-
On the Process Model section, set the Load User Profile to True.
- Could Not Create SSL/TLS Secure Channel
- No Robot Available for User X
- Permission Missing: Launcher
- Logon Failure: Unknown User Name or Bad Password
- Executor Start Process Failed, Reason System.UnauthorizedAccessException: Access Is Denied.
- Permission Missing: Remote Execution
- Executor Start Process Failed, Reason: A Specified Logon Session Does Not Exist. It May Already Have Been Terminated
- An Existing Connection Was Forcibly Closed by the Remote Host “Oops! We’re Sorry! It Seems Orchestrator Is Down.”
- Value Cannot Be Null
- Job Not Found
- The Handle Is Invalid
- An Attempt Was Made to Reference a Token That Does Not Exist
- Desktop Has Been Disconnected While Performing UI Actions
- A Device Attached to the System Is Not Functioning
- Executor Start Process Failed, Reason System.Runtime.InteropServices.COMException (0x800700AA): The Requested Resource Is in Use
- Execution Error: System.UnauthorizedAccessException: Access to the Path 'C:ProgramDataUiPath…is Denied
- Robot Already Running for User
- Bad Request and The Remote Host Did Not Answer in a Timely Manner.
- Cannot Upgrade the Legacy UiPath.Core.Activities Package.
- System.Runtime.InteropServices.COMException: Licence Permission Missing
- Bad Request - Request Too Long
- The User Is Not a Member of the Specified AD Domain.