I confirmed that the password for the robot is correct by updating the robot in orchestrator and ensuring I was able to log into the machine with the robot account. I then ran the job and got the same error message as listed above.
Executor start process failed, reason: A specified logon session does not exist. It may already have been terminated
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 mstsc command-line function. If the 60 seconds timeout period expires, the error is displayed.
I confirmed that there we no users running on the machine and retested without and benefit. (this was happening every time.
I did look at that forum post and that did not resolve the issue.
What has appeared to fix the issue:
Restarted the UiPath Robot Service: ( Run -> Type Services.msc -> UiPath Robot (restart) )
Created a sample project on the unattended bot machine (using the bot user) and publishing the project.
I am unsure which of the 2 steps fixed the issue, but after I did that the UiPath Robot downloading all the project files it was missing. I was able to run the bot through the UiPath Robot Tray and the Orchestrator Successfully.