Hi, tried to run a small prog by orchest, but it’s not running and the job showing failed.
@Palaniyappan
Did we check with the log for the exception message buddy
@balkishan
Kindly check whether the username and password is correctly mentioned in the robot tab
Sometimes if password is changed anytime we may get like this
And also check whether the right machine is connected
@balkishan
yes, I am testing on my machine only. If the username/password is wrong, it will show disconnect status of robo bro. I don’t think there is a issue in credentials.see the snapshot.
No no
If the username domain is wrong we will get that
But if the password alone is wrong we might get this sort of exception,
And also I can see from the image like the domain is not mentioned along the username, kindly include that, and mention the same from what get with command whoami from cmd window
Cheers @balkishan
Yah we need to mention both the username and domain while creating robot in robot tab @balkishan
I added, and run again, Again it’s failed.
Even there is nothing showing in the log also.
Restart once your uipath robot service in your machine
Go to start and search as services.msc and restart your robot service
@balkishan
not showing me any UiPath services running
Search as Uipath Robot… @balkishan
Is it coming after restarting @balkishan
Hmm
Fine check with your robot tray and see what is the robot status whether it is connected or I’m Unavailable state
To open robot tray
Go to start search as uipath robot
@balkishan
It’s connected bro.
I can see two robot on my system ??
How bro ? both showing connected and I can see the publish package there in Robot
kindly follow this troubleshoot method for robot service accessing
https://forum.uipath.com/t/could-not-connect-to-uipath-robot-service-make-sure-the-service-is-started-troubleshoot-steps/82653
cheers @balkishan
when run from the UiRobot it’s running successfully, when I ran from Orchestrator it’s got failed.
First Failed I ran by orchestrator, and second successfully I ran by UiRobot
Why it got failed when I run by orchestrator.
@Palaniyappan I tried all method, which you shared me the link, but none are work for me. Same issue I am getting while running a job from Orchestrator. kindly help .
Hmm
Fine let’s resolve this
Are we choosing the right robot while running the Job
@balkishan
Hi Palani, are you there ?
Yes, I have chosen the right robot. I am using a single robot bro.