I’am executing a process launched by the Orchestrator. The robot is on a server. I have defined the connection to the robot via RDP.
I need to disconnect the RDP session to maintain opened the Uipath Assistant. When the porcess is executed I have an error message (the title of the issue). Otherwwise, if I close the RDP connection, the Uipath Assitant is closed also and the process lanched by the Orchestrator doesn’t work.
I’am not able to select the service mode, because when I want to change the installation of Studio, The window doesn’t appear.
I have an eterprise version, correctly licensed. I remenber that the first time I installed Studio, it was a Community version. But I uninstalled it to install the enterprise version.
Today, I’ve uninstalled Studio and I’ve installed again, but I can’t change from UserMode to ServiceMode.
Someone has logged into the VM with the robot account and then just closed the RDP window without signing out.
Humans shouldn’t be logging in with the robot accounts. But if they do, they have to SIGN OUT from the start menu. You can’t just close the RDP window - it leaves the session open and locked.
This is irrelevant to unattended automations. You don’t even have to install Assistant on servers where unattended jobs will run. Assistant is just a UI interface for humans to run attended jobs.
For unattended, all that has to be installed is Robot(.exe) on the server. It connects to Orchestrator.
If it’s not staying connected when you log out then make sure you have installed it in service mode, not user mode.
What happens if you sign out from the server then try to start a Job in Orchestrator?
FYI you don’t need to install Studio. The only thing that needs to be installed on a server that runs unattended jobs is Robot. But having Studio won’t hurt. Glad you got it fixed. The installer should give more info about what should be selected and why, IMO. “If you are installing on a server to run unintended jobs, select service mode” for example.