Are you able to Remote into the Server using the same user id that is used for the Robot you were using to run the job on? If the user id does not have Remote authorization then that could cause problems.
Sorry, I mean the user id in the Robot that you provisioned in Orchestrator to run your job.
You can verify if the user id has Administrator or Remote Authorization by going to Control Panel > User Accounts > Manage User Accounts
If you receive a Credential screen, then your user id doesn’t have Admin rights and therefore that might be an issue for logging into your computer from Orchestrator.
It looks like possibly a TypeInto with Activate checkbox or similar activity failure. Weird that this part of the operation would fail, but doesn’t seem Orchestrator related at first glance, as it’s not related to job run per se.
Or I’m wrong of course.
i’m having the same Error with the Type into activity.
It works fine for a couple of times , and on other times it fails.
Is there a fix for this problem?
"UiPath.Core.ElementOperationException: Timeout reached. —> System.Runtime.InteropServices.COMException: Timeout reached.
— End of inner exception stack trace —
Unfortunaly it did not help, we tried all sollutions, and the problem is still occurring.
When we monitor the proces, the flow is going perfecly but when using the orchestrator, or minimalising the remote desktop connection, it fails. (but not all the time )
I also have build in a element exist to check if the selector is available, and it returns true
When using Orchestrator, you will first want to make sure “Logontoconsole” is turned off for the robot. You can change this setting while editing the Robot’s settings in Orchestrator. Secondly, you will want to change the resolution settings in the same place (ie 1920 w, 1080 h, 32 depth). The resolution will allow the screen to be ideal size so all your elements will be shown on the screen like when you were developing the project.
If that doesn’t help, then I suggest you use TakeScreenshot and Save Image, so you can see what the screen looks like before the error occurs. - you can see if any weird popups occured or anything else.