Service connection for On-Premise Orchestrator


In my Pipeline created in Azure DevOps, I am using the the tasks UiPath Pack and UiPath Deploy.
I have added the UiPath Orchestrator connection as my Service connection in Azure DevOps.
I have an on-premise Orchestrator.
On running the pipeline, the UiPath Pack job runs but fails in the job UiPath Deploy and states the below:
**Failed to run the command. Could not connect to Cloud Orchestrator, Refresh Token: ***, Tenant: ***, Account Name: ***, OrganizationUnit: *.
This was using Basic Authentication and I used my Orchestrator credentials and tried the same with Admin credentials as well.
In order to use the Token Based Authentication, I need the Account Logical Name and Tenant Logical Name. From where can I fetch this in case of on Premise?
Or is there some other issue due to which I am unable to Deploy?

Hello @Sohana_Dinesh_Kamat_DK!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly

I am facing the same issue.

Did find how to fix that ?

**2021-08-12T13:06:07.2701201Z Failed to run the command. Could not connect to Orchestrator: https://my-orchcestrator-URL/ , Tenant: ***, Username: ***, Password: ***, OrganizationUnit: *, UseWindowsCredentials: False.
2021-08-12T13:06:07.2703035Z Please make sure that the provided URL (my-orchcestrator-URL) is correct, available from your build agent, and not blocked by a firewall.
2021-08-12T13:06:07.2704100Z If the Orchestrator is using a self-signed SSL certificate, make sure that the build agent trusts it. Ensure that all the steps at Self-Signed Certificates were correctly followed when creating the certificate.

It was related to the access level issue. I did the setup under my user, then I was able to implement the same

1 Like

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