Could not start executor. The requested resource is in use. (Exception from HRESULT: 0x800700AA) RemoteException wrapping System.Exception: Could not start executor. The requested resource is in use. (Exception from HRESULT: 0x800700AA)

Help Orchestrator
,
1

Hi All,

Im getting this error >>Could not start executor. The requested resource is in use. (Exception from HRESULT: 0x800700AA)

RemoteException wrapping System.Exception: Could not start executor. The requested resource is in use. (Exception from HRESULT: 0x800700AA) , My process is already set in the orchestrator with set (4am 5am and 5pm) schedule ,every time it will run on its schedule of (5am) it got faulted without any logs just this error on the description.
Then I will just try to retry or rerun it then it will work again,

2

Hi, sorry for the delayed response:

When the robot runs on the desktop version of Windows (Windows 7/8/10)

In this case, the robot cannot be started if another user’s active session already exists. The following error occurs.

Could not start executor. The requested resource is in use. (Exception from HRESULT: 0x800700AA)

This is because in the desktop version of Windows, only one active session can exist at a time. All cases are summarized below. (This is the result of Windows 10.)

3

@ivonamaesurita pay attention to all the unattended robot settings.
All the robot must have same Setting.
Login to Console settings> Enable toggle > Set to No
Disable any resolution settings.

4

I found no documentation that can confirm this. On the contrary, UiPath allows for different robots to run different resolutions.
Regarding the Logon to Console set to No, I don’t see how that should help with this error.

I believe it is a timing issue that can occur if 2 jobs are queued for the same Robot. Some times the UiPath agent is not prepared for the next job, even though Orchestrator thinks it is.
In any case, this same error randomly happens in our environment, if one job takes much longer than anticipated, and following jobs are pending hours on end afterwards. When it is finally their turn to run, this error will come.
OP: Did your 4AM job finish before the 5AM job?

5

I’m getting the same issue as well. 2 different jobs were dynamically allocated. first one started on 1 of 3 available robot, another started 1 second later and caused the error.

In my case, my Login to Console setting in Orchestrator is set to No. but I’ve just found the Login to Console setting in UiPath.Settings on the robot itself was set to true. I’ll made the changes there as well maybe it’ll resolve the issue.

6

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