Robot could not run properly on VM

Help
, , ,
1

HI there. I have deployed an unattended robot on a virtual machine. It ran properly when I logged on (remote desktop connection) and clicked run at the robot tray, but when I disconnected the VM and tried to run the robot from the Orchestrator (Run Job), seemed like there were some errors on activities like Type Into, Click (Timeout reached) and also Take Screenshot didn’t work. Looked like it could not detect elements on the screen.

Things I’ve tried:

  • Specify the VM’s screen resolution on robot setting (in Orchestrator).
  • Use ‘Invoke Workflow Interactive’ and specify the resolution.
  • Set ‘Login To Console’ to false.
  • Restart the robot.

Anyone has solutions? Please help.

Thank you.

2

Hi.

I had the same issue very recently and tried the same things as you. I was doing a lot of work, inside a Java application, and many of my Click actions failed / timed out.

I assume the robot is licensed with an Unattended License (if not, that would be why…)

I then launched Remote Desktop with the same screen resolution as my robot settings in Orchestrator.

When running the process from Studio in the resolution, it noticed some things were different from when I normally ran my RDP in full screen. Clicks were not accurate, and I managed to adjust the X and Y offset and get things to work this way.
image

Not sure if this applies to your issue, but it could be worth checking…

Another thought is about security. Are the credentials you are using for running the unattended robot the same or different from the ones you use when running from the tray? If you have a service account, there are some things that need to be setup for it to work. Please see this for more info: Installing the Robot

Hope it helps :slight_smile:

Best regards,
Michael

1 Like
3

You could try Robot Streaming - RPA Component | UiPath Marketplace
It “broadcasts” the robot’s screen so you could watch what’s going on in the unattended session.

Cheers

4

Hi @SuprajaReddy

Try to follow some of the suggestions mentioned in: [Screen resolution issue](Screen resolution issue when running process in production environment - Help - UiPath Community Forum)

In our company we had a similar problem, and I solved it by changing the required screen resolution in the Azure VM (windows), in the Registry Editor:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration\XXXXXX\XX\XX

See:
How to change Azure VM (Windows) resolution - Microsoft Q&A