After UiPath upgrade packages not available under %ProgramFiles%\UiPath\Studio\Packages

We recently upgraded UiPath Orchestrator and Robot. Robot is installed in service mode. After the upgrade we had to upgrade system.activities package to a recent version in one of the existing automation. The process is working fine from studio, published the package and ran it from Orchestrator. But the process was throwing some random error, turns out the nuget package corresponding to the new version of system.activities was not available at %ProgramFiles%\UiPath\Studio\Packages. When I manually copied the same, the issue got resolved. Anyone got any idea how to fix this without copying the file manually? The UiPath.settings file and config file all are same as that of previous bot version.

The packages go to c:\users\*username*\.nuget\packages

If your robot is not able to download packages, then check with your security/network team to find out what’s blocking it.

I understand that the packages are downloaded in the %userprofile%\.nuget\packages folder by default. I might be wrong, don’t have a strong understanding of these things, this is high density robot. Have 10+ bots, so instead of copying package to each userprofile I pasted just the nuget file to %ProgramFiles%\UiPath\Studio\Packages folder and it worked.
followed below instruction from UiPath guide for managing-activities-packages
“Transfer the NUPKG file to the Studio computer in a folder defined as a package source in Studio. To add the package to the default local feed, copy the file to %ProgramFiles%\UiPath\Studio\Packages for per-machine installations or %localappdata%\Programs\UiPath\Studio\Packages for per-user installations.”

To your question about asking network team, this was working fine before upgrade no other firewall/ security changes were made right after upgrade.

Thanks!

You mentioned upgrading. Depending on which version you went from/to the official source changes. The current source is:

https://pkgs.dev.azure.com/uipath/Public.Feeds/_packaging/UiPath-Official/nuget/v3/index.json

The previous official source was:

https://www.myget.org/F/workflow

You might try adding that older source back in under “User defined package sources” - maybe your project uses an older package that isn’t available on the new source.

I didn’t realize this could be an issue, thanks for sharing this. Just curious is there a way to understand the versions available in each source?

Not really. I would expect they migrated everything from the old to the new but it’s possible they missed things.

Thanks! I think source difference is not the issue here. Because I updated the package after the UiPath upgrade only. So I reckon the package should be available for the robot also.

If the robot can’t download the package then check with your network/security team. It’s common for internet access to servers to be restricted.

Just wanted to leave an update. Your suggestion helped a lot.

Even after the upgrade the Robot was still trying to download the packages from old source don’t know why, then I updated the nuget config file to use the new source. After that BOT started using new source, this time firewall was blocking it. I was able to identify it from logs and fixed that and finally everything is resolved. Another thing I noticed was for one of our developer’s manage package settings was still pointing to old source so many package versions were missing and we had to manually make it point to new one.

Thanks for your help!

1 Like

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