Unable to install package / run automation

Help Orchestrator
, , , ,
1

Every time I try to run an automation through orchestrator or install it manually through UiPath Assistant I get the following error message:

Could not load file or assembly 'System.IO.FileSystem, Version=5.0.0.0, Culture=neutral,…

This happens with all my automation and started happening suddenly because this is the machine I usually use.

Does anyone know what could be the reason of this issue?

2

@JavXult,

Normally the dependency packages gets download automatically to user Nuget folder but check it once if it’s there.

You can manually try to copy this package to Nuget folders from your development machine.

Thanks,
Ashok :slightly_smiling_face:

1 Like
3

Hello @JavXult

Can you please try and compare this file from your development machine, with the one on your production machine?

C:\Program Files\UiPath\Studio\NuGet.config

If the 2 files differ, then please try this:

  1. Take a backup of the file on your production machine
  2. Replace the file on your production machine with the file from your development machine

Please let me know if it helps.

I have created a case at UiPath Customer Support about this NuGet.config file that doesn’t get updated automatically when updating Studio.
The case got declined as a single problem, but we are seeing it more and more.
The NuGet.config file contains URL for package sources.

Regards
Soren

1 Like
4

@JavXult

  1. Generally the packages could not be downloaded if there are any firewall blocks check if there is any policy change and revert it or disable
  2. Also sometimes this might be triggered due to the robot upgrades
  3. Alternately for a immediate resolution we can copy the .nuget folder or required package folder from dev machine to the target machine. Location is C:\users\username\.nuget

Cheers

1 Like
5

Thank you everyone for your suggestions, as you all said it worked by replacing the NuGet file. It was strange that it started happening in the first place, however now I have a workaround in case it happens again.

6

Hello @JavXult

Can you please clarify if you replaced the NuGet.config file like I suggested?
Or if you copied the NuGet file for the library as @ashokkarale suggested?

The suggested actions are not the same.

Just so others who might find this post knows what to do :slight_smile:

Regards
Soren

1 Like
7

You are right, my bad I did it in the way you suggested, I just updated the solution. Thank you!

1 Like
8

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