Unable start a Job using Orchestrator on my Local Machine

Help
21

Even I have the same Issue. From Agent it works fine but not with a Manul running from Orchestrator

22

I can start jobs from orchestrator CE no problem just a few hours…

1 Like
23

@dlucas85 and @Ganesh_Hegde,

This is known issue follow the below steps and you will be able to run the jobs

The job goes in pending state because while provisioning the robot you would have given only username, you have to give Domain\username.

You can get the domain information through command prompt

whoami or set user

If this part is done, then you can refer the above post.

Please refer the below post

Using CE with a two robots but one robot is acting weird RPA Developers

Hi @soneill437, The job goes in pending state because while provisioning the robot you would have given only username, you have to give Domain\username. You can get the domain information through command prompt whoami or set user Refer the below post.

5 Likes
24

Thanks I have tried this and my issue has been solved.

1 Like
25

Thank you. The problem is resolved for me too by applying the above solution.

26

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