Assistant not able to initiate the process when job initiated from Orchestrator

Help Assistant
,
1

Assistant not able to initiate the process when job initiated from Orchestrator.

Assistant is connected to Orchestrator and orchestrator does list the robots as available during initiating the jobs.

The job is left in" …pending state " with the Orchestrator after showing “command sent successfully” message.

Can anybody help me with the steps to resolve?

2

@Lakshmi_Malla

Welcome to our UiPath community.

Can you please disconnect the bot machine from Orchestrator and then reconnect it again.

3

I have tried multiple times , but still is not able to resolve the issue.

Let me know is there anything i am missing with configuration of Bot/Machine with Orchestrator or other.

4

@Lakshmi_Rani

Are you able to run the process from UiPath Assistant ?

5

Yes I am able to run it from UiPath Assistant

6

@Lakshmi_Malla

May I know what type of license did you select for that BOT in Orchestrator ? And also can you please show the screenshot of how you provided the credentials to it.

7

Img1
Img11421×630 71.8 KB

I have not set any credentials for this bot…
Can you help me step by step configuration credentials with latest version of Cloud orchestrator
(any document)?

8

Img4
Img4743×176 14 KB

9

Img3
Img32256×250 24 KB

10

@Lakshmi_Malla

Use Standard Template instead of Machine Template and then check it once.

11

Hello @Lakshmi_Malla,

Are you using Community or Enterprise edition?

12

First, create the machine in Orchestrator.

image
image1474×764 59.1 KB

After that, in users, your user shoud be Automation Developer and assign the user and the machine to the folder. Then you must use this kind of connection from UiPath Assistant:

image

After that, check in License tab in Orchestrator that your machine is connected for the unattended license:

image
image1478×192 14.2 KB

I hope it helps :slight_smile:

13

Hi

Welcome to UiPath forum

Please have a look on this doc on how to connect robot to orchestrator

Cheers @Lakshmi_Malla

14

Enterprise edition.

15

Assistant has nothing to do with Orchestrator running jobs on your servers.

If your job is stuck in pending, it’s probably because you don’t have an available unattended Robot on that server.

16

Whenever i see this above text, there’s 99% chance the windows password was updated but not in the robot setting in orchestrator.

Can you just enter correct password in the orchestrator for that robot and try again?

17

If I am not wrong there is some configuration credentials settings.
Plz check below screenshot.

If this error comes means what to do?

Img4
Img41468×923 51.3 KB

18

InkedImg6
InkedImg62097×359 93.6 KB

Configured robot - still some issue which I am getting confused.

19

InkedImg7
InkedImg72255×525 88.3 KB

Looks like I have configured everything but something is missing - Please can anybody help me to resolve this…

20

Have you put in the username and password for each Robot? The error message says it can’t find one with credentials configured. Listen to the error message.