robot
2023.10
false
- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Restarting Robot Components
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Robot Citrix Apps Virtualization
- Troubleshooting
- Common Connection Errors
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET required during installation
- Assembly Cannot Be Loaded From Network Or Azure File Share
- Activities cannot find .NET Runtime
Robot User Guide
Last updated Oct 25, 2024
Custom Package Folders and Network Paths
A Package combines all parts used in an automation and it can include: Activities, Workflows, Files, Data Sources, and other components needed for running the automation. A project created in Studio is published as a Package to a location/feed from where it is later downloaded by the Robot and used to run an automation.
The following locations/feeds are configured by default in Studio:
- Orchestrator Tenant and Orchestrator Host
- Local
- Official
- Marketplace
Custom feeds can be used as well, but before setting up a custom location to publish a Package, make sure that Robots have access to it.
Important: For Packages Location, absolute paths need to be used. Relative paths are not supported.
For more information on how feeds work and how to change them, see the Managing Activities Packages document which goes in more details on this subject.
Fallback packages folders can be configured by adding the
NUGET_FALLBACK_PACKAGES environment variable on the robot machine. This contains the absolute paths to fallback folders separated by semicolon ;. If the environment variable does not exist, the robot tries to read the Nuget packages fallback folders from the Nuget.config file.
More information can be found in the fallback folders documentation.
Important: Processes deployed in fallback folders are not supported, only dependencies.
The Package Location can be changed via Setup Command Line using the
PACKAGES_FOLDER parameter or by editing the uipath.config file. This enables you to change the download location of your workflows and their dependencies for Studio and/or Robot.
When installing the Robot via command line, if you do not provide this parameter the default folder is
%userProfile%\.nuget\packages.
It is possible to use environment variables such as
%USERNAME% or %USERPROFILE% but needs to be escaped as follows:
-
When the setup is invoked from Command Prompt - use -
UiPathStudio.msi PACKAGES_FOLDER=C:\Some\Path\^%USERNAME^%.
-
Batch scripts - use
%-UiPathStudio.msi PACKAGES_FOLDER=C:\Some\Path\^%USERNAME^%.
-
PowerShell console or scripts - no escaping is needed.
-
When using Active Directory domain accounts, it is recommended to specify the domain name in the folder structure too, such as
C:\packages\^%UserDomain^%.^%Username^%.
- No restrictions when a local path is used by multiple service mode robots on the same machine.
- When the robot is deployed in service mode and Secure XAML is used, network paths are not supported.
- Service mode robots installed on separate machines cannot connect to the same folder on a network. Each machine must have its own folder.
- Only non-mapped paths are supported, e.g.
\\server\Packages. Mapped network paths such asZ:\Packagesis not supported. The reasoning consists in how the mappings are being resolved per user. In this situation, the owner of the installed files is the computer account and thus, it will not have access to the per-user network mappings.
If the same local path is used by multiple user mode robots on the same machine, you must add the
NUGET_SCRATCH machine environment variable on the robot machine. The value has to be a path to a folder other than the actual NuGet installation
one. The folder set for the environment variable is used as a temporary folder for NuGet.
For example:
If the
packagesInstallationFolder parameter in the uipath.config file is C:\UiPath\Packages, to allow multiple user mode robots to use the same local path for packages, create a new folder (e.g. NuGetScratch) and add the NUGET_SCRATCH machine environment variable with the C:\NuGetScratch value.
Note:
- The NuGetScratch folder should only be used by the
NUGET_SCRATCHvariable as a temporary folder. - The user accounts under which robots run must have read and write access to both folders on the machine.
-
When network paths are used, the path must include the machine name and username.
Example:
<packageSettings>
<add key="packagesInstallationFolder" value="\\NetworkServer\SharedFolder\UiPath\Packages\" />
</packageSettings><packageSettings>
<add key="packagesInstallationFolder" value="\\NetworkServer\SharedFolder\UiPath\Packages\" />
</packageSettings>
