- 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
Errors When Running as Administrator
Starting with the v2020.4 release, running the UiPath Assistant or Studio as Administrator, they are not going to be able to communicate with the Robot Service, which can throw the following errors:
The Robot Status displays a "Robot Error" message, and when trying to run or debug a process, an "Access Denied" error is displayed.
The connection status in the Assistant is incorrectly reported offline and the process list is not available.
UiPath Assistant and Studio (clients) require communication with Robot Service. This is a separate Windows process, which is automatically started by the client if it is not already running, with the same elevation level as the client.
- If Assistant was started with a privilege level (which automatically started the Robot Service with the same privilege level) and then Studio is started with a different privilege level, the Robot Service can communicate only with the one on the same privilege level (Assistant).
- If Assistant was started normally, then closed, then started as Administrator, communication will be broken because the Robot Service was initially started with normal privileges.
Since the Robot Service has a different permission level than the Assistant, or Studio, they are not able to communicate and the errors presented above are seen.
To avoid this, make sure that Assistant, Studio and the Robot Service always run with the same privilege level.