Requested resource in use Exception - Orchestrator

[himavad (HimG)]

Hi All,

I am having a similar issue. I have looked through the above replies and tried the suggestions such as toggling the “login to console” setting, but doesn’t help.

To describe my issue specifically,
SITUATION: I am having 20+ processes deployed on orchestrator now on various schedules and they are all deployed using different user credentials (high density?). The jobs are dynamically allocated to environment containing 3 VMs with unattended licenses and the overall utilization is at ~60% so most of the time there are jobs queuing up waiting to run.
PROBLEM: Intermittently (I counted that it is on average 1-2 times every 50 jobs), the job doesn’t start at all and faults with this error - Info: Could not start executor. The requested resource is in use. (Exception from HRESULT: 0x800700AA). There are no logs for these faults.
REQUEST: Any suggestions on what else I can try to prevent this from happening? Since this is a long time issue I understand that there may not be a solution yet. In that case, is there any way I can trigger an event from this type of error so that I can use that to automatically re-trigger the job?

Thanks in advance!

[Saravanaraj]

Hello to every one, i have tried as said in this forum but the same error occurs. And even i tried in bottom of tray its working fine while connecting through Orchestrator getting error like " Could not start executor. The requested resource is in use. (Exception from HRESULT: 0x800700AA)".
Looking forward your support to solve this issue.

[Roshello_Relos]

Hi i tried also all the above instructions, but same error occurs when one of our bot is already login in our High Density Server. But when i tried to enable the “Login To Console” and set to "NO"on one of the ROBOT settings, the issue was now resolved. Hope this may help.

[rachelwalker907]

This worked for me too

[bradford.rust (Brad R)]

None of this solved my issue. I ended up restarting the bot services on the server. This released the account and allowed it to log in.