Not able to publish library from studio 2022.10.3 version to orchestrator

Help Orchestrator
,
1

Hello All,

I am not able to publish library from studio 2022.10.3 version to on-premise orchestrator.

But I am able to publish process.

Can anyone help in this case?

2

Hi @ishnarayan.pandey

Welcome to the community

Can you tell what error you are getting

cheers

3

@ishnarayan.pandey
welcome to the forum

Currently it is unclear what was done and what is failing in detail.

In general we we would also recommend:

  • publish the Library local
  • upload it manually to ORC (check for the right feeds) and select:

grafik

4

HI Anil,

Invalid package details!

This is the error. And if I am publishing it to local it is able to publish.
But when on orchestrator its giving the above error.

5

Hi @ishnarayan.pandey

Can you try what @ppr mentioned

And can you please send a screenshot of youe publish settings when you click on publish to orchestrator

Cheers

6

This i have done already.
Same issue : Invalid Package Details

7

Check this https://uipath-survey.secure.force.com/CaseView/articles/Knowledge/How-to-troubleshoot-error-Publish-of-workflow-Project-to-orchestrator-failed-Invalid-Package-details?lang=en_US

Extra steps that should be verified if the solution is not working:

  1. In Orchestrator → Tenant → Settings → Packages (Deployment: Internal; Security: Secure Deployment); Libraries (Feeds: Both host and tenant feeds, Deployment: Internal; Security: Internal)

  2. In UiPath Assistant verify if you are connected to your Orchestrator with a machine key

  3. In Studio, go to Settings → Manage Sources → Verify if your Orchestrator nuget sources details are in place

  4. If the package size is more than 28.6 MB, there is a limitation set by IIS. In order to increase the package size limitation, follow Increasing The Size Limit Of Package Files .

If any of the file in the project directory is corrupted. To identify the corrupted file we will have to use which Trial and Error method . This can involve File names with characters from unsupported language, File Extensions or actual corrupted files.
For instance, remove all the unwanted files and keep Xaml files and project.json file and try to publish the same. If the process is published, this indicates that one of the files that was removed from Project Folder is corrupted. Once the file/s are identified they can be recreated or corrected accordingly.

It is often observed that if the project Folder has any special Characters like % in Project directory, and REFramework. Delete the file or Rename the file to validate if this is applicable -ProjectName\Documentation\REFramework Documentation-EN

  1. In your package, in Studio, update the UiPath.System.Activities to the latest version.

  2. Try to publish the Studio process in your Orchestrator now.

8

Have done all the things which is mentioned above.
But still the same issue.

9

Archive the library project and attach it to see if we are facing the same issue.

10

Hi Marian,

If you have 22.10.3 version of studio installed, you can just create a library process and try to publish it. I am publishing a blank library only and hence there is no need of me sending zip file to you.

11

No issues on my On-Premise Orchestrator and Studio 2022.10.3.

Which is your error details?
Did you check the event viewer logs on the robot machine and on the Orchestrator machine?
Do you have access to publish libraries?
In Tenant → Settings → Deployment → how did you configure the settings?

Extra note: every customer is having a different setup and configuration, it is not a single solution/cause for everybody.

12

I’m facing the same issue.
Orchestrator version: On-premises Orchestrator 2020.10.3 ; UiPath Studio version: 2022.10.4

When publishing a blank project with Compatibility “Windows” I get the following error: “Error: Publish of Process project to Orchestrator failed. Invalid package details!”
On the Orchestrator side, no error appears.

When publishing a “Windows - Legacy” blank project, all is OK.

13

Hi @ishnarayan.pandey

There could be several reasons why you might not be able to publish a library from UiPath Studio to an on-premise orchestrator. Some possible causes and solutions include:

  1. Incorrect connection details: Make sure that you have entered the correct connection details for your on-premise orchestrator, including the URL, port number, and credentials.
  2. Network issues: Check if there are any network issues that might be preventing the library from being published. You can try pinging the orchestrator server to see if it is reachable.
  3. Permissions: Make sure that you have the necessary permissions to publish libraries to the on-premise orchestrator.
  4. Missing dependencies: If the library has dependencies on other libraries or packages, make sure that these dependencies are also available in the on-premise orchestrator.
  5. Compatibility issues: If you are using a newer version of UiPath Studio, make sure that it is compatible with the version of the on-premise orchestrator you are using.
  6. Firewall: Check if the firewall is blocking the connection to the on-premise orchestrator. You may need to add an exception for UiPath Studio in the firewall settings.

Thanks!!!

14

Hi @klaucs,

You probably need to upgrade your Orchestrator to 2021.10+ since the Windows / .NET 6 project compatibility was released in the 2021.10 version of the platform.

Try publishing your project to your hard drive, then manually uploading the .nupkg file via the Orchestrator web UI and you will probably observe the same error message.

Thanks

15

Hi @ishnarayan.pandey,

What version of Orchestrator do you have installed? Is it version 2021.10 or newer?

What happens if you publish the blank library to your hard drive, then try to upload the .nupkg file into your Orchestrator web UI?

Thanks

16

The issue is resolved now. But i think it was some issue with orchestrator itself.
I don’t know what exactly but its resolved now.

Thank You