I faced a similar issue when trying to launch a job from Orchestrator.
The issue was with the username. Please retrieve the username using “whoami” command and use it for login.
In my case, I used the display name of my user account which was incorrect. For example, if the display name was “My User” and the actual username was just “User”, using the display name would cause the login to fail.
There are many steps like this in Orchestrator setup that require deeper investigation to fix.
I tried with such command and introducing the correct User and Password but now pops up a different Robot Tray Error. Here I attach a screenshot of it:
Looks like a permission issue when trying to access files or folders.
Are you running UiPath Robot as an Administrator?.
I do so and I don’t see such permission issues.
I have a similar problem. I can execute a job “Job A” successfully on my PC from Orchestrator or launch it from Studio, but when I try to run the same job from my system tray I get the Login Failure.
This is puzzling, because if I’m able to invoke it from Orchestrator, my credentials should be correct right?
Thanks @marinabir94. My solution also was in the Credential Manager but slightly different. My password had to be changed per company policy. I had to update credential manager with the new password.
Previously, you could do this right through the local bot. I’m not sure why the feature changed. It was a very good feature.