Are you sure your username is same as the one you get when you run the command
whoami in the command prompt?
and the machine should be copied from the robot tray.
Kindly check with these stuffs that would surely resolve your issue
— first create a machine in orchestrator and that machine name should be same as in your system
To get that name go to start-> search as robot-> settings and get the machine name from there and paste the same while creating machine in orchestrator and copy the machine key after this from orchestrator and paste it in your system robot tray and mention the orchestrator url as well
— the. Make sure that we have a robot created in the orchestra with the same machine name and while entering the detail for username and password go to cmd window and type as whoami which will give use domain and username, enter the same in the orchestrator while creating robot
— create a environment now In the robot tab and tag the robot created in the previous step to this environment
— now back to our system in robot tray we have machine key, and orchestrator url mentioned readily and now we can connect
even after that if you are getting this error
here is the troubleshoot on this
Since you have only one Robot, it’s mostly the details provided during provision is incorrect.
Please reapply, the issue will be solved.
Same issue when I connect my robot in tray, at that time in orchestrator robot is active but within a minute robot turns to unresponsive mode
We’ve experienced this issue after updating from version 2018.4.3 to 2019.10.16.
The behavior is as follows:
All robots appear as un responsive in the dashboard.
However, all robots are available on the robot list. All of the robots continue to perform work according to their schedules or when a job is manually assigned to them.
When a robot is working, it turns blue “busy” in the dashboard.
When the robot has completed it’s task it appears green in the dashboard “available”.
However, after a period of time, presumably after four minutes, the robot returns to red “unresponsive”.
Additionally, if you log into the robot, disconnect it and then reconnect it, it will appear green in the dashboard until it again times out.
We’ve also noted that the transactions feed no longer returns information, regardless of time span selected.
So, is this a heartbeat issue? Or is it a dashboard issue? Or both?
I have the same problem.
But I found after reinstall ,UiPath Agent Desktop need to resetting.
The solution to my problem was to enable “DatabaseMigrations” = true in the web config and also setting the “ERROR” Quartz triggers to “WAITING”. Then restart the orchestrator app service. It seems to have been an incomplete migration during the update.