High-density feature not working

Help
1

Scenario:

Testing High-desity feature by triggering from rest api through script with 2 different users, but showing following error:

Executor start process failed, reason System.Runtime.InteropServices.COMException (0x800700AA): The requested resource is in use

Some addition settings:

Studio/Robot/Orchestrator Version: 2017.1.6434

OS Version: Windows Server 2016 Datacenter ( Microsoft Azure )

Access can be granted to this server in test environment, if interested ones wants to troubleshoot.

Thanks in advance

guling

2

bump

3

Not sure if it helps, but check to which location your license file is pointed in Uipath settings file.

This was in 2016.2.

This didn’t work, used to get “Robot already in Use” pop up message.

%localappdata%\UiPath\License
%localappdata%\UiPath\License

This worked

%ProgramData%\UiPath\License
%ProgramData%\UiPath\License

4

Hi vvaidya

Could be that the 2017 version of uipath studio is looking for license somewhere, which triggers this issue when more than 1 session is using uipath service. However, regarding UiPath it is Orchestrator that controls this. I am only triggering workflows through rest API.

Best regards
guling

5

Hi Extinguir,

Came across the same issue :“Executor start process failed, reason System.Runtime.InteropServices.COMException (0x800700AA): The requested resource is in use”, I also dont have a orchestrator and set the logintoconsole as false. Did you resolve that issue?

Thanks

6

Hi @tengteng.zhao

Please contact our Technical Support for assistance on this issue.

They will help you debug it.

7

Hey Vaidya, one more quick question I am using 2012 R2 server in High Density- i have two robots running and accessing Excel - one process/robot trying to kill the application ? what will be the impact of this action on another robot…
when i tried it my first bot which is trying to kill excel is facing the error?

8 
taskkill /F /T /IM foo.exe /FI "USERNAME eq target_user"

should do it. /IM specifies the image name, and the /FI option specifies a filter to use, in this case, a user with the username “target_user”.

In any case, you’ll need to be an Administrator on the local system to forcefully terminate processes in another users security context

9

Have you test trigger the same process with 2 HD robots from orchestrator web interface? If this works?