Orchestrator does not interact with robot machine as intended, but automation runs when executed via assistant

[abhishek.kunte]

I have created automation on new enterprise version on UiPath Orchestrator but now the problem I am facing is when i run the automation via assistant from my robot machine it runs as intended but when i log out of rdp and give automation command from orchestrator i get below error

when i checked loggin into servers after triggering he automation from orchestrator i found out that it ooen the application but doesnt interact with it.

[prashant1603765 (Prashant Kumar)]

Hi @abhishek.kunte

check this same,

Cannot run any process throw orchestrator

It seems your robot machine connected to the orchestrator there are some communication issues. Try creating the new machine template and get the client ID and Client secret using that connect your robot machine with orchestrator.

If you found helpful please mark as a solution. Thanks
Happy Automation with UiPath

[sppal.c]

@abhishek.kunte

I have created automation on new enterprise version on UiPath Orchestrator but now the problem I am facing is when i run the automation via assistant from my robot machine it runs as intended but when i log out of rdp and give automation command from orchestrator i get below error

1. Make sure there are no group policies that are blocking the rdp session for robot.
2. Make the login to console as No in the robot settings.
3. If you are directly closed the RDP session manually make sure to logout it properly instead of directly closing the rdp window.

[singh_sumit (Sumit Singh Tariyal)]

Hey @abhishek.kunte kindly read the below solution .

Then your robot is installed in usermode…you would see uipathuserhost.exe that means it cannot run ui automation in background or u attended…so please reinstall the robot in service mode

Uipath help needed-Cannot bring the target application in foreground because the Windows session is locked

@Mohamed_Salman I guess you are running the robot while the system is locked and if so yes this error would be thrown… And while installing community edition by default the robot would be of user mode which supports attended only and for unattended we need a service mode installation Cheers

Robot - Robot Service

Click 'LABEL': Cannot bring the target application in foreground because the Windows session is locked

Make sure the robot is installed in Service Mode. Note: If you cannot find the UiPath Robot service in Start → services.msc, that means you installed the robot in User Mode. [image] To install the robot in Service Mode via the GUI installer UiPathStudio.msi, you will need to select Custom → Install for all users on this computer → Unattended Robot Reference: Robot - Installing the Robot To install via command lines, you will need to adapt the example commands which mentions Robot as a Win…

cheers

[abhishek.kunte]

I am currently using trial version of the enterprise edition setup.

when i tried reinstalling it doesnt show me the option to select service mode.

[singh_sumit (Sumit Singh Tariyal)]

Hey @abhishek.kunte kindly read the official docs from UiPath

Robot - Installing the Robot

cheers

[Anil_G (Anil Gorthi)]

@abhishek.kunte

Welcome to the community

1. Which machine are you using as unattended?
2. are you locking the machine and running it? if yes then it would not work
3. installing robot in service mode is mandatory

cheers

[abhishek.kunte]

Thank you for your support it worked correctly after reinstalling UiPath as mentioned in the provided article and the issue is now resolved.

[abhishek.kunte]

Thank you for your comment, I managed to resolve the issue by reinstalling the UiPath robot as for unattended service.

[singh_sumit (Sumit Singh Tariyal)]

@abhishek.kunte Glad to see it worked now kindly close this thread by marking this as solution.

cheers