Unattended Robot Freezes in VM Windows Server

Help Robot
1

The robot suddenly freezes, but as soon as I connect to the machine using RDP, it resumes processing without any manual intervention. Everything was working normally until that day, and there were no Windows updates or UiPath updates at that time.

Forum Engagement Daily Reports
2

Hi @zxclyde

  1. Is it installed in service mode?
  2. and when you it resumes normally when logged in , are you getting the next logs or is it stuck ?
3

@zxclyde

on what step did it get stuck?

are there other users on same machine?if yes and if it is pused on excel then mostly it might be that the excel from others users locked processing..

also is it only one time? can you check the event viewer logs using timestamp so that we can see if there are any errors

cheers

4

Hi,

  1. Yes
  2. Yes, and the processing continued.
5

Hi,

It suddenly started getting stuck after two simulated clicks before a Type Into activity. This began unexpectedly after running 24/7 for a year without any known issues. I’ve already verified the development environment, and everything there is working as expected. I also confirmed that the elements used for the simulated clicks haven’t changed and are working properly in Development without any modifications.

6

UI may be blocked due to a disconnected or corrupted session state (May be in last connect, it was not properly signed out).
Reconnecting via RDP reinitializes the desktop, allowing execution to resume. recommended fix is to run the robot using LoginToConsole = True

image
image615Ă—430 36.8 KB

Robot - Windows sessions

7

@zxclyde

  1. Are there any delays or retry around them?
  2. Can you check event viewer logs
  3. If wait for load is present as complete and if the page is still loading it might happen but generally very less chance

cheers

8

Hi @Anil_G ,

  1. Yes there is a 1000ms delay.
  2. UiPath.Executor 22.4.3.0

UiPath.Core.ImageOperationException: System.ComponentModel.Win32Exception (6): The handle is invalid.
at System.Drawing.Graphics.CopyFromScreen(Int32 sourceX, Int32 sourceY, Int32 destinationX, Int32 destinationY, Size blockRegionSize, CopyPixelOperation copyPixelOperation)
at UiPath.Vision.UiImage.FromScreenRegion(Rectangle region)
at UiPath.Core.Image..ctor(Region screenRegion)
—> System.ComponentModel.Win32Exception (6): The handle is invalid.
at System.Drawing.Graphics.CopyFromScreen(Int32 sourceX, Int32 sourceY, Int32 destinationX, Int32 destinationY, Size blockRegionSize, CopyPixelOperation copyPixelOperation)
at UiPath.Vision.UiImage.FromScreenRegion(Rectangle region)
at UiPath.Core.Image..ctor(Region screenRegion)
— End of inner exception stack trace —
at UiPath.Core.Image..ctor(Region screenRegion)
at UiPath.Core.Image..ctor(Rectangle screenRegion)
at UiPath.Core.UiElement.ScreenshotUnsafe() this is what I found in the recent event viewer.

  1. Yes, generally this is very less likely to happen.

I already tried to create a new user account in the VM Server, but still issue persist.

9

Hi @MohammedShabbir ,

Thank you for your reply, but error still occurring. I haven’t find any solution yet. I already tried to create a new user account in the VM Server.

10

@zxclyde

I would suggest to upgrade your UIAutomation package to latest possible version.

11

@zxclyde

  1. Are you using any cv activities?
  2. 22.4 is a little older version also..are your processes also built on old ones?
  3. So its happening for all users and VMs now?

cheers

12

Hi @Anil_G ,

  1. No.
  2. Unfortunately, Yes the process has been designed using the Classic Automation process.
  3. Yes, it is happening for all users and VMs.
13

@zxclyde

Did you use any image based selectors or so?

as per exception in event viewer looks like the image based or cv based selector would have failed

or a take screenshot…

recently were there any sleep time changes on machines?

or we robots upgraded to latest version or so?

cheers

14

Hi @Anil_G @ashokkarale @MohammedShabbir ,

The issue has been resolved. Our team identified that the default RDP screen resolution had changed. To address this, we defined the resolution in the Robot Settings. As a result, the robot process now behaves correctly, even when interacting with the same element.

Thank you all for your support.

2 Likes
15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.