Managing Nuget Packages

We are running on cloud environment using virtual machines to run bots and on version 2019.10.5
Description # We have 3 Terminal Server’s and 14 robots (terminal server accounts) on each Server (Total 42 Unattended BOT’s).

• Currently, we are seeing that each robot (terminal Server Account) has their own copy of the various nuget packages pushed down from Orchestrator to run the desired workflow.

• Question is – Can we maintain “nuget packages” centrally at one location per server and point each robot session to the one common/shared location? Or is it mandatory that each unattended bot should have its own copy of all of the “nuget packages”.

We have seen few packages where we never used (for example: uipath.vision, etc) this one package is itself close to 1GB, like that we have other packages taking up the space.

These packages are taking maximum space on the hard drives. Could you please let us know the better way on how to manage these packages centrally, so that it is not occupying the space on the hard drives for every terminal server & session.

There are so many logs getting created when the BOTs are running. This is also one of our major concerns which is occupying the space on the hard drives. Is there a way to avoid the logs using minimum space, so that we do not need to clear the logs every fortnight.

Also the packages are in different drives on each terminal servers. Do we need to maintain uniformity across.
Terminal Server # 1 on C:
Terminal Server # 2 on D:
Terminal Server # 3 on E:\

For Example: When one workflow is scheduled on one unattended BOT (Terminal Server 2) it pulls all the required packages required and runs the BOT.
But when we try to deploy the same workflow on another unattended BOT (Terminal Server 1), then it is trying to search for the packages if found then it is working, if not found then it is failing.

Also yet times, the workflow is not running on the “Current Version” and using the previous versions while running on different unattended bots.

We tried to go through the Community Forum and UiPath documentation, but could not find a proper/right solution for all our issues.

Could you please help us in resolving our space issues & package issues. We are also open for a zoom call, so that it will be better explained by showing our systems.

Help is appreciated !

Hi,

Did you find any solution for this ?

This is incorrect. The Robot.exe process downloads and installs them from the online feed (ie nuget.org)

Nuget.org IS that central location. If you want it to be local, you can go through the arduous process of adding them to Orchestrator, but this creates a lot of unnecessary work for you. No matter where you store the packages, each Robot will always download and install them locally.

You use it, you just don’t realize you use it. Packages have sub-packages. Go to your Project pane and start expanding the packages and you’ll see.

It uses standard NLog functionality, which you can modify the configuration for.

This is likely due to how you installed UiPath on each server.

They explicitly use the version that you have installed to the project. They don’t, and you wouldn’t want them to, automatically try to use a higher nor lower version.

1 Like

Hi,

We are having this same issue. I think what he is asking for is that can we somehow define that robot accounts use the same shared folder where they download packages from Nuget.org or from Orchestrator.

For example, we are running our robots also on a virtual machine that allows multiple concurrent user sessions. I have currently 7 robot accounts using the same machine, and each of them are downloading their own package copies to the same machine. So now I have 7 accounts that each are taking so much space, when they could just use the same files from a centralized local folder.

edit. I think this is possible in On-Prem Orchestrator, but we are in UiPath Cloud so can not access orchestrator settings files the same way.