- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities packages and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Chrome Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Edge Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
Common Installation Errors
This page documents errors you may encounter when running the Studio MSI installer to perform an installation or an update.
To get more information about the cause of the error, locate the installation log and check for a more specific message (for example, the installation disk is full, or a specific location cannot be accessed).
The path of the log file is:
- For manual installations and updates:
%TEMP%\MSI*.log
(where*
represents a random set of alphanumeric characters) - For Automatic updates, per-user installation:
%LOCALAPPDATA%\UiPath\UpdateService\Logs\
- For Automatic updates, per-machine installation:
%PROGRAMDATA%\UiPath\UpdateService\Logs\
- For Community Edition automatic updates from versions prior to 2021.10:
%USERPROFILE%\AppData\Local\UiPath\Logs\install_error_log.txt
A policy set on the machine does not allow installing applications using MSI files. This error usually applies to Windows Server machines that forbid MSI installations through policies.
Follow the steps below to add a registry key that allows running MSI installers.
- Open the Registry Editor on the machine.
- Navigate to the registry key HKLM\Software\Policies\Microsoft\Windows\Installer.
-
Create or edit the value named DisableMSI of type REG_DWORD and set its Value data to
0
.Note: You may need to restart the machine for the registry changes to apply.
Free up the minimum disk space required for the Studio installation. For more information, see Hardware Requirements.
There are two concurrent installations on the machine, one for the current user and the other for the entire machine. This might result in unexpected behavior of the UiPath products and requires uninstalling one of them.
Close all instances of Studio, and then go to Add or remove programs in the Windows settings to remove one of the installations:
- To keep the per-user installation - Uninstall the older UiPath Studio version. After you open Studio again, your per-user installation will be automatically updated to the latest version.
- To keep the per-machine installation - Uninstall the newer UiPath Studio version. You can then manually download the latest version from the Resource Center in Automation Cloud and install it to upgrade to the latest version. After installing the latest version, Studio will receive automatic updates when they are available.
There are two concurrent installations for the current user on the machine. This might result in unexpected behavior of the UiPath products and requires a clean installation.
- Go to Add or remove programs in the Windows settings and uninstall both UiPath Studio applications.
- Download the latest UiPath Studio version from the Resource Center in Automation Cloud and install it. After installing the latest version, Studio will receive automatic updates when they are available.
Multiple installations (one per-machine and at least one per-user) exist at the same time and interfere with an upgrade or change of the installation. Usually, you'll find an older version (2019.10, 2020.10) installed per machine and a newer one installed per user.
Go to Add or remove programs in the Windows settings and uninstall all the UiPath Studio applications except for one. In most cases, you should leave the oldest one, as it's probably installed via corporate policy and it would appear again if removed. If you are the sole administrator on the machine, you can stick to the latest version, removing the older ones.
- Error 1603
- Cause
- Solution
- Error 1625
- Cause
- Solution
- Error 4000 - Full Disk
- Cause
- Solution
- Error 4001 - Unauthorized to Create Scheduled Task
- Cause
- Solution
- Error 4003 - Two Per-user and Per-machine Installations Were Detected
- Cause
- Solution
- Error 4004 - Two Concurrent UiPath Studio Installations Were Detected
- Cause
- Solution
- Error 4012 - Two Concurrent UiPath Studio Installations Were Detected
- Cause
- Solution
- Error 1921 - UiPath.UpdateService could not be stopped
- Cause
- Solution