Sign out of all RDP sessions on Robot machines before starting a job on them.
window displays, among others, the errors that caused a job to fail.
Below is a list of frequently encountered errors, and what you can do when you encounter them:
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
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.
If you are sure that the username with which you connected the Robot to Orchestrator is the same as the one on the machine, please use the Regutil.exe tool to deactivate the Robot license and reconnect to Orchestrator. Find more details here.
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.
If the Robot username is in a domain, the username needs to be in the
The error is thrown if the Robot password is not provided. To add the password, edit the Robot, as explained here.
This error is displayed if you are trying to run a process on an Attended Robot from Orchestrator.
There are two types of occurances:
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
command-line function. If the 60 seconds timeout period expires, the error is displayed.
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
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.
This error is related to a known Windows issue. For more information, please use the
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.”
The issue is encountered if the
parameter in the
file is set to
while using High-Density Robots.
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 only works over un-authenticated proxy connections.
This occurs when the public key of the certificate is not imported or it is not imported in the trusted root certification authorities of the local machine. Read about Web Certificates for more information.
This error can occur when you execute processes created prior to 2018.3.
Processes created prior to 2018.3 depend on the legacy UI Automation package, namely
Core.Activities. When you run them in the current version, you must use a
meta-package that migrates the activities using the new System and UIAutomation packages.
By default, the legacy
package is not published anywhere, so the migration meta-package is used. However, if the legacy
was published on custom feeds or Orchestrator by users, the legacy package is installed, which exhibits this error.
To solve or avoid this issue, simply remove the legacy
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.
This issue occurs on Studio v2018.3.2 and above, when executing projects that are using the 18.3.6864.20582 version of the
If you have projects created with Studio v2018.3.1 which were using the
dependency version 18.3.6864.20582 you must open them in Studio and the
dependency must be updated to the 18.3.6877.28298 version.
If you have projects created in versions prior to v2018.3.1 and weren’t opened with this version, but v2018.3.1 is already installed, you must perform the following steps to prevent compatibility issues with future versions of the UiPath Platform. You must delete the 2018.3.6864.20598 version of the
dependency from the following locations:
- The Orchestrator feed
- The default packages location –
%Program Files (x86)%\UiPath\Studio\Packages
- The NuGet cache –
If Studio/Robot v2018.3.1 was NOT previously installed and the 18.3.6864.20582 version of
package is not deployed locally or on your Orchestrator feed, then you can upgrade to v2018.3.2 without any risks.
If you ever installed other 2018.3 versions than the Enterprise Studio v2018.3.1 edition (eg. Community Stable v2018.3.0 or any prior beta versions for both Enterprise and Community), the above applies as well. Do not use any
with version less or equal than 18.3.6864.20582, and
with version less or equal than 2018.3.6864.20598.
Updated about a year ago
Uipath Logon Failure Unknown User Name or Bad Password