- About UiPath Assistant
- UiPath Assistant on Mac
- Field Descriptions
- Automation Configuration
- Task Capture Launcher
- Assistant Governance
- UiPath Assistant for Excel add-in
- About Backward and Forward Compatibility
- Hardware and Software Requirements
- Updating the Robot
- Setting Up Windows Server for High-Density Robots
- Services the Robot Connects to
- UiPath.Settings File Description
- 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
- 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
Using Mapped Network Drives
To make your work easier with shared network folders, you can map network drives for quick access on your user account. However, if the processes you publish from Studio are located on that drive, the situation described below occurs.
Packages published from Studio are not visible in the UiPath Assistant.
The issue occurs when you use a mapped network drive for your packages. The location of the packages you publish to Orchestrator
can be seen in the
UiPath.settings file on the Robot machine, under the
NuGetServerUrl parameter. The mapped network drive is available to the user that created it, while the Robot Service runs system-wide.
One of the following methods can be used to solve this issue:
Converting the Robot to User-Mode
You can convert the Robot from Service-Mode to User-Mode by running the
.MSI installer and choosing the User-Mode during update.
Check out the Updating the Robot guide for more details.
Mapping a Network Drive for the Local System
- Download the Sysinternals Suite. It contains the
PsExec.exetool, which is required for this operation.
- Open an elevated Command Prompt instance.
- Use the
cdcommand to navigate to the location where you downloaded the Sysinternals Suite (such as
- Use the
PsExec -i -s cmd.execommand. A confirmation dialog appears.
- Click the Accept button to install the
PsExec.exeservice. This makes it possible to map a network drive for the Local System.
- Use the
net use z: \\ServerName\SharedFolder /persistent:yescommand to map the drive, where ServerName is your server and SharedFolder is the location of the drive you want to map.
If you want to remove the mapped network drive, you need to repeat the steps above, but using the
net use z: /delete command instead. You can find out more on this page.
Unattended robot cannot find mapped drive
Unattended robots cannot find a mapped shared drive when running a background process.
This is the behavior of non-interactive Windows logon sessions.
In order to use mapped share drives in
headless mode, the drive would need to be remapped for every job the robot starts. The remapping also applies to the scenario in which
the robot machine is restarted.
For example, by having an explicit invocation in the workflow of the
net use Z: \\unc\path command before using the shared drive.