[Solved] the feed lists package but multiple attempts to download the nupkg have failed

Hello to all!

Days before today I had the following reported error in the PRODUCTION environment:

image

The procedure for the deployment of the robots in the Production environment are Upload the package to the Orchestrator, create the Process, Triggers and finally, we open the UiRobot, download the package in the Local and Execute the robot to discard any error of environment.
It is just in this last step that the error appeared (attached image).

We make multiple validations:

  • Validation of permissions in the VM where the robots are executed (everything was OK).
  • Validation of permissions at service level (everything was OK).
  • Validation of uipath ports (everything was OK).
  • Validation of the url: www.myget.org (everything was OK).
  • We detected that some packages were not downloaded in the path: C:\Users\XXX.nuget\packages. Specifically the package shown in the image (not found). The action we took was to copy packages from other environments and paste them but it still didn’t work. (Discard this action).

Successful solution:
Finally we validated that UiPath Studio was installed in the Production environment, so we performed the following successful steps that solved the problem:

  • The project folder (where Main.xalm is located) was copied to the Production environment.
  • The project was opened with UiPath Studio.
  • When opening UiPath Studio, it automatically downloaded the package and component updates.
  • We ran with the Studio and it worked.
  • We executed with UiRobot and it worked.

This problem, when it appeared, I looked for information in the forum and found only PROXY validation, port validation, internet, permissions, but I think there is very little information when something like this happens. That’s why I upload the following information.

I hope it helps you if you have a case similar to mine.

Greetings!

Hi @Jean_Piere_Ochoa,
Thank you for sharing such good detailed feedback and information. I will push it for further investigation. Maybe there is something we could do about it.

I consulter this case with our team and it looks like you were not able to download the package from Robot. Most likely due proxy/internet configuration. The workaround you have used works as the package might have been found by Studio on another feed and since the nuget folder is shared between Studio and Robot it will work. But this is not a proper solution as this can break if the nuget cache is cleaned.
You should download the specific package and place it on Orchestrator if you are not able to ensure proper connectivity to myget.org/F/workflow/

Hello @Pablito ,

Thank you very much for your response and support to this problem. Regarding the possible solution you mentioned, about the Internet /proxy configuration; we had no problem with those cases, since we had the network and support team that performed those validations and everything was correct.
Furthermore, I consider that this would not be the case, since the day before that problem, another robot was deployed in production and there was no problem.
It is worth mentioning that the package in the attached image was not used in the project (it was not downloaded from the package manager).

The last sentence actually tells me everything :slight_smile: This was the reason actually. For such situation it’s worth to have dedicated network location in the environment where all “standalone” packages will be deployed and then add this path as a resource point in the configurations so both Studio and Robot will have access to it and will be able to resolve the dependency.

Hi @Pablito, I have the same issue, with an excel activity. I could download it manually from myget.org, but the assistant is not able to do it. We don’t have studio in that environment as it is a VM only used as unattended robot. Following your suggest I’ve uploaded manually the activity to the orchestrator (as a package) but still can’t install the process with the assistant (it is just an excel wb creation, to test the newly deployed production environment). Do you have any recommendation about how to do it?

Hi @dgallucci,
Normally it should work as soon as the robot/assistant is connected to the orchestrator. But if issue still persist I think you should contact with our Technical Support.