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.

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.

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.

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:

This issue can occur in the following cases:

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.

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."

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.

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.

To correct it, follow these steps: