Process fails when started from Orchestrator

Hey guys,

so I have a process that’s runs just smoothly if it’s started from Studio. However, when I start it from Orchestrator, it fails everytime. In the Initialise part of the process I close Chrome browser if it’s open. I get this error message:

Close Application: Cannot terminate the process which owns the current node.

However, my problem is not exclusively connected to this activity. If I remove this activity, the next activity is a Read Range activity that reads an xlsx file on my machine. But I get some kind of remote exception…

So it seems that only log message activiy isn’t crashing my process when starting from Orchestrator. Every activity that has to read or manipulate something on my local machine is faiing. Could there be a problem with authorization? I am the only user on my machine and I have admin rights…

Hi @Rajid,

Try this setting on orchestrator under the robot settings & report back :

image

Regards,
Nithin

1 Like

Can you provide some details on how you have your Robot configured in Orchestrator (Unattended/Non-Production or Attended/Studio)?

Is the UiRobot installed as a service or in user mode?

The credentials provided to the Robot in Orchestrator does it match the user of the remote host it is connecting to?

1 Like