What is solution for this? I have the same problem 
Hi,
I am getting same error did it get resolve
This happens when I try to run job from task scheduler with “Run whether user is logged on or not”. If I change that to “Run only when user is logged in”, the job completes.
My robot service is running as “Local Administrator”, but my schedule job is ran by domain user (test_user).
If I change my Robot service log in as this same user (test_user), I get the same error from Studio too.
It seems that the service doesn’t have access to start interactive remote desktop session?
I don’t have Orchestrator license, just one unattended robot.
I still have this error message: Executor start process failed, reason System.UnauthorizedAccessException: access Denied.
I have used the same combination of password and username in both windows (My computer login credentials) and Orchestrator. But I still have the same error message
Current version of UiPath studio: Enterprise Edition 2018.1.4
Current version of Orchestrator: UiPath 2018 Orchestrator Community 2018.2.0
Please Help me
@badita @Gabriel_Tatu
what is your exact problem?
I can’t run my robot from the orchestrator. Here are some screenshots. while running this process via studio it works fine but when i start running the job from the orchestrator i got the error message above. I have already provisioned the robot to the orchestrator
1 Like
You have an issue with user/password…
What OS is the robot runnig on? Can you try switching between console true/false for this robot?
I was facing the same issue, but then I tried giving my machine password in the Robot which I was running. Earlier I left the password field blank as it is not mandatory and I was able to run my process using system Tray uipath robot. Now I can run my robot from orchestrator.
Attached is the screenshot where I entered the password.
I am using windows 8 . Can a firewall or an antivirus blocks the connection between my robot and the orchestrator? I am using the company laptop, i will try with my own computer to see whether i have the same problem.
Thanks
Thanks for the input but it didn’t work for me
Hi All,
I had a similar isssue - “Executor start process failed, reason System.Runtime.InteropServices.COMException uipath”
I did the following which resolved the issue
- Validated the User ID and Password in UiPath Orchestrator Robot setting is correct
- Validated in Computer Management the user is added with correct permissions
- Logged in once with the user and validated the profile is able to log into the machine/session/vm
- Ran the job from orchestrator and it worked fine.
Hope it helps.
1 Like
Hi All,
I have a similar issue but the difference is job triggers from orchestrator and it runs fine but there is a point where admin rights is required for an application LPbut that step fails when I try running it from systems tray it works fine. I have used the same user on robot as well as on orchestrator. I guess the uipath.executor is not taking local admin rights while executing from orchestrator.
User which is configured on the robot has admin rights could you please let me know on what can be done.Any help would be highly appreciated.
Thanks
Vinod
Please let me know on how will the robot run with local admin rights when triggered from orchestrator.
Thanks
Vinod
Did anyone figured out the solution for this error? @ddpadil @badita @vinodcrimson @tass @Gabriel_Tatu @firdoscts @Prakitk
"Executor start process failed, reason System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))\r\n at UiPath.UiSystemClass.OpenInteractiveWindowsSession(String bstrUser, String bstrPassword, UiOpenSessionFlags nFlags, String bstrApplication, String bstrAppArguments, Int32 nDelayMs, Int32 userToken, UiGenericOptions options)\r\n at UiPath.Core.Setup.OpenInteractiveWindowsSession(String username, String password, OpenSessionFlags flags, String application, String arguments, Int32 userToken, Int32 preferredWidth, Int32 preferredHeight, Int32 preferredDepth, Boolean fontSmoothing)\r\n at UiPath.Service.Impl.Executor.StartProcessInSession(Guid executorInstanceId, String username, String password, SettingsDictionary execSettings, IntPtr userToken)\r\n at UiPath.Service.Impl.Executor.<>c__DisplayClass17_1.<<Start>b__0>d.MoveNext()"
@srinucslt this is totally because of access related issues, what i did was from Orchestrator we have an option to disable login to console. This started working but this is just a workaround still in search of the permanent fix.
@vinodcrimson But If you set 'login to console ’ as false, then how bot would run uninterruptedly irrespective of RDP minimization or disconnections?
@srinucslt login and close the VM, then trigger it from Orchestrator it will work.
Hi,
I know the post is obsolete but I have just resolved similar issue by adding manually the user to the users who can access the machine by RDP.
To achieve this, open the machine → go to Remote Desktop Setting → scroll down and open “Select users that can remotely access this PC”
Then click Add and put the email or user id to the text box. Click Check Names and select the correct user. After that Sign off from the machine and now bot Login to Console options should work.
Regards,
Kamil
1 Like