- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Networking troubleshooting
Occassionally, robots cannot find a mapped network drive when running an unattended automation.
headless
mode. This can be done by remapping the drive for every job the robot starts. The remapping also applies when the machine
is restarted.
net use Z: \\unc\path
command before accessing the shared drive.
The robot logs the following error message: "System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework."
The Robot machine might not trust the web address for the Azure File Share, where the package is located. Alternatively, the account the robot uses might lack permissions for that specific location.
The Robot machine becomes unresponsive and shows high CPU usage at some point after starting the automation. It occurs on Windows 10 v1903 machines.
DWM.exe
file, leading to high CPU usage upon completion of a Remote Desktop session.
Apply the KB4522355 update on the faulty Windows machine.