Using the enterprise edition and an unattended robot.
Just as the subject says, this is something totally new to me.
Activities that should throw timeout error does not throw errors until at least 25 minutes have passed.
The job should go to fault but never does. The longest it has kept running for is 4 hours and that is when I turned it off.
The sessions start and manage to take some screenshots and put out a few log messages for control. Then it manages to at least execute a start process activity (the application starts to load, got screenshot proof).
After that. Nothing works. No matter what I do, the robot just freezes there. It will not go any further, it will not produce any more logs and it won’t crash when the timeout should be reached by the attach window activity. I tried to remove the attach window activity, still does not move pass this point.
When I eventually get fed up with waiting I try to kill the job to try again. But it will not work and it gives the error message
- Could not start executor. A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520)
It will keep throwing this error until I try to log in to the RDP. When I do that, the screen is at first all black, then the login screen reaches the point when it shows the username and some white text flashes by underneath until it turns blue, showing an error message that says that someone else is probably logged in.
If I do not try to log in, the robot never leaves the session (waited for one hour, still logged in, would not start job from orchestrator, the scene described above happens every time).
Does anyone have any idea where I should look for answers?
And of course, it works perfectly when running it from the studio and when launching it from the orchestrator while being logged in to the RDP beforehand.