Hi,
I need help with the below error.
Could not start executor. An internal error occurred. (0x8007054F)
RemoteException wrapping System.Exception: Could not start executor. An internal error occurred. (0x8007054F)
The bot has not been executed on the production server for the last five days. I don’t know why this error occurred or how to resolve it.
Anyone can help me.
Thanks
Gopal
Hi @gopal.thakare
In Orchestrator, edit your robot settings and enable the LoginToConsole to active and set its value to No, and make sure that the Robot machine is signed out (in a cmd.exe type logoff) before running the job from the Orchestrator
Also check
This issue may happen when MFA (multi-factor authentication) is turned ON for the robot machine. Having MFA enabled on the machine doesn’t let the robot login into the machine and run workflows in Unattended mode.
To resolve the issue you may try these:
Remove the group policy that enforces MFA on the machine.
Check internally with your Network team to see why is taking so much time to connect your Robot to the Orchestrator server.
Increase the UIPATH_SESSION_TIMEOUT system variable to…
Hope this helps
I have tried this but not works
Hello @gopal.thakare ,
You have to login in prod server with the help of support team and check if you are able to open the studio.
By the looks of it , this might be due to 3 things off the top of my head
The bot is misconfigured or not provisioned with a license.
There is some issue in installed UiPath in the environment
Downtime in orchestrator, retry to trigger the process once it is up.
By trying to open studio in the targeted environment you can rule out the first 2 from the above list.
Thanks,
Gautham.
Try Reinstalling the UiPath Assistant, Is the robot configured correctly? If not working then i guess you can raise ticket to UiPath support.