- 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
NuGet Packages Not Accessible After Migration
After converting a Robot from Service-Mode to User-Mode , the XML files in the NuGet Packages aren't accessible after the migration is complete and the following error message is displayed:
C:\Users\john.doe\.nuget\packages\HelloWorld\1.0.0\lib\net45\Main.xaml
is denied".
.nuget\packages
) by the Local System user that the robot is running service under.
When converted to User Mode, NuGet packages from that folder are no longer accessible as the current user that runs the Robot does not have permissions to view or edit those files.
If you choose to delete packages from the original folder, the Robot reinstalls the processes in the configured folder under the user's permission. This way, the Robot has access to the files whenever it needs to run them.
%userprofile%\.nuget\packages
to a different path, like %userprofile%\.nuget\packages_new
.
.nuget\packages
folder and download the processes in it so they can later be used.
%userprofile%\.nuget\packages
folder. You can set a different folder in one of the following ways:
- During installation, by installing from the
command line
with the option
PACKAGES_FOLDER
. -
After installation, by manually editing the
uipath.config
file:- Open the
uipath.config
file in a text editor. By default, the file is located inC:\Program Files\UiPath\Studio
. - In the
packageSettings
node, add thepackagesInstallationFolder
key with the path to the new folder as its value. -
Save the changes and restart the robot.
For example, add the following touipath.config
to change the download location toC:\nuget
.<packageSettings> <add key="packagesInstallationFolder" value="C:\nuget" /> </packageSettings>
<packageSettings> <add key="packagesInstallationFolder" value="C:\nuget" /> </packageSettings>
- Open the
For more details around the differences between Service-Mode and User-Mode Robots, read the according to deployment document which provides a more detailed description of each type of Robot.