We have licenses for Orchestrator and 3 unattended robots. (Orchestrator 2017.1.6547)
We have a Server for Orchestrator, another SQL Server for the db, and 3 other 2012 Servers for each of the robots.
A single instance of the robot works fine when launched from Studio. But, won’t work when a job is started from Orchestrator.
The logic is supposed to start a process, get the element that pops up, and click in an option. However, it starts the process and then throws the following exception:
Cannot find UI element coresponding to this selector
What we have tried:
truein the Uipath.settings file. Either way does not work. However, when setting it to
false, we check that the robot logs in first as RDP-TCP session and then suddenly changes to console on runtime.
We tried wrapping the logic and using Launch Interactive Workflow with the values: Width: 1920, Height: 1080, Depth: 32, loginToConsole: false (or true) without success either.
We tried changing the registry as the following article suggests: http://www.networkautomation.com/urc/knowledgebase/running-interactive-tasks-in-minimized-remote-desktop-windows/4ecdf43e03470/
What can we do?