Problem setting up an unattended robot in Orchestrator

Help Orchestrator
,
1

Hi community! I am a relatively new UiPath user but I am making great strides with attended robots. I am now trying to create a unattended bot using my community access. I have followed the course instructions and read the manual but it isn’t work and any job I run remains pending.

The robot is present in the folder Manage Access and the template is present in Machines.

However, when I try and run a process from the folder I select the account and the machine but nothing is present in Hostname (screenshot)

2
21251×716 44.7 KB

.
I have been trying to debug this for hours with no success.

Things that might help with this:

  • I am using a community license

  • Looking at the Admin, Tenant Licensing, I can see that I have 1 of 1 unattended robot with 300 robot units

  • If I look at License under Tenant in Orchestrator it shows 0% 0 Runtimes of 1 - I assume this is because nothing has successfully run

  • For the Windows password for the bot I have used the pin on my laptop given I do not use a password

  • No Machines are showing under the folder → Monitoring → Machines

Any help would be appreciated!

Thanks community!

2

You wouldn’t run an unattended Robot on your machine with your username. Unattended jobs should be run on a RDP server that humans don’t use.

3

Can you check if you have registered your machine with a host name under Machines in Orchestrator.

4

Agreed - but as part of the certification that is what you are asked to follow.

5

Hi - thanks for your response. I don’t think I have done this and can’t see where to add.

If I got to Tenant - > Machines and review view installed versions there is nothing in that section but I am in a loss how to add it there.

Any further help appreciated!

4
41712×453 16.8 KB

6

Goto Tenant machines and Add machine from there

I dont see that blue button to Add Machines, maybe you donot have access, make your account as Tenant administrator, and also add Robot as role in there too,

7

Hi - thanks for taking the time to respond.

I resolved this myself late last night. The challenge was that when I tried connecting to the machine using the command prompt : UiRobot.exe --connect -url “UiPath” -key I was receiving the message that Orchestrator was already connected, which it was but not to the machine with that key. What I did was deleted the machine created by Assistant and then reran and the command and the machine was added. I them reconnected Assistant and now I see both machines.

Thanks again! Hopefully if someone else comes across the challenge this will help them.

Mark

8

@Mark007

Please check this

cheers

9

Thanks, this is certainly a helpful walk through. The challenge I had was that I had already connected Assistant to an attended Robot and so your approach wouldn’t have worked until I disconnected Orchestrator first.

10

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.