Provisioning Unattended Runtimes

Help Orchestrator
,
1

Hey Peeps!
I have a doubt regarding the Orchestrator and Runtimes. So, I have a runtime setup for my local pc with a machine template, where I run everything what I build for testing purposes. Now I am using the same credentials in a VM where UiPath Studio is installed. When I am trying to run this process using a trigger, it is failing every time. I did some brainstorming and something flashed me like how will a process which was built on VM, even though the package is published to Orchestrator, run on a different machine? Is there any solution for this? I thought of removing the local machine template from the Orchestrator, but rather than this is there any way to tackle this issue?

2

Hi @Charan_Kalyankar

Below Youtube video link should help.

Regards

3

how will a process which was built on VM, even though the package is published to Orchestrator, run on a different machine?

This is not a problem, and it’s exactly how it’s done in enterprise setting: robot is built on one machine with RPA Dev license, then it’s published to Orchestrator and run on different machine, may be Test od PROD machine. Part of setting this up (let’s call it deployment) is making sure that other machine has all necessary dependencies, like libraries*, applications and their settings, screen resolution, network/firewall setup etc. If you have taken care of that then robot should run on different machine without issues.

Is robot even starting execution on that desired machine? Are you getting any errors? Is trigger executing and job is stuck on pending?

* Regarding libraries this is taken care by Orchestrator, but even though it’s happening automatically, it’s also part of deployment.

4

The robot is running fine when ran from Studio, but getting faulted when triggered through Orchestrator.

We tried out a solution. We set up a new account for the VM and published whatever the processes we built from Studio to the new Orchestrator license. It is working now.

But as you said, this should be the exact process that should be followed. Going forward we can’t keep using the same VM to develop workflows and deploy them. So should figure out the core issue why is it happening.

Everything including dependencies, firewall, libs, all are well setup.

Thank you for responding :smile:,
Regards,
Charan.

1 Like
5

Hey @Parvathy,

Thank you but I have referred to the same video setting up the unattended robot provision and machine licenses. We figured out the problem was the processes being published to a different machine wasn’t working.
So, we setup a whole new account with a new license and it worked.

Thanks and Regards :D,
Charan.

2 Likes