- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- 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-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- 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
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- 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 VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- Troubleshooting
Studio Executables
If you plan to use Studio, Robot, and the Assistant on machines that have strict rules related to executable files, the following executable files need to be allowed:
The following executables related to Studio, Robot, and UiPath Assistant are found in the Studio installation folder:
|
Executable name |
Description |
|---|---|
|
dotnet.exe |
Used to run the .NET Runtime. |
|
ngenr2r.exe |
Used for the ready to run feature in Studio. |
|
testhost.exe |
Helper process for test cases. |
|
SetupExtensions.exe |
The SetupExtensions.exe tool is a command line utility used to install or remove the UiPath extensions. |
|
slinject.exe |
Used in the Silverlight extension install. |
|
UiPath.ActivityCompiler.CommandLine.exe |
Helper process for compiling activities. |
|
UiPath.ActivityPreprocessor.CommandLine.exe |
Used to modify files before compilation. |
|
UiPath.Assistant.exe |
Used to launch the main UiPath Assistant desktop application. |
|
UiPath.ChildSession.Service.exe |
PiP - Child Session helper process. |
|
UiPath.DiagnosticTool.exe |
Used to run the UiPath Diagnostic Tool. |
|
UiPath.Executor.exe |
The main robot executor, used to run Windows - Legacy automations. More details can be found in the robot executor documentation. |
|
UiPath.Executor.NetCore.exe |
The main robot executor, used to run Windows and Cross-Platform automations. More details can be found in the robot executor documentation. |
|
UiPath.Explorer.Launcher.exe |
UIAutomation helper process. |
|
UiPath.LicenseTool.exe |
Used to handle the licensing of UiPath products such as Robot, Studio, or Assistant. |
|
UiPath.MicrosoftOffice.Tools.exe |
Used to add, remove, or repaire Office add-in. |
|
UiPath.Oidc.exe |
Used to connect the robot to Orchestrator using an OIDC connection. |
|
UiPath.RemoteDebugging.Agent.exe |
Used for the Remote Debugging feature. |
|
UiPathRemoteRuntime.exe |
Helper process used by the UiPath Remote Runtime feature. |
|
UiPath.RobotJS.ProtocolHandler.exe |
Used by Robot JS to handle requests from and towards the Robot. |
|
UiPath.RobotJS.ServiceHost.exe |
Used to handle the communication between applications and the actual robot on the machine when the robot is installed in service-mode. |
|
UiPath.RobotJS.UserHost.exe |
Used to handle the communication between applications and the actual robot on the machine when the robot is installed in user-mode. |
|
UiPath.SAP.SolutionManager.CommandLine.exe |
Used for the Test Suite integration with SAP. |
|
UiPath.Service.UserHost.exe and UiPath.Service.Host.exe |
The actual robot, it is used to facilitate the communication with other applications, such as Orchestrator, Studio, Assistant, or robot executor. * When the robot is installed in user-mode, only the UiPath.Service.UserHost.exe is added on the machine.
|
|
UiPath.Studio.Analyzer.exe |
Helper process used by the Workflow Analyzer feature. |
|
UiPath.Studio.CommandLine.exe |
Used to handle commands sent for Studio and Robot through the command line interface. |
|
UiPath.Studio.DataBaseServer.exe |
Studio process for indexing workflows. |
|
UiPath.Studio.exe |
Used to launch the main Studio desktop application. |
|
UiPath.Studio.Project.exe |
Studio process for each open project plus another one ready to open a new project. |
|
UiPath.Studio.Plugin.Tfs.Host.exe |
Helper process for the TFS client. |
|
UiPath.Studio.WebServiceRepair.exe |
Webservice client generator. |
|
UiPath.TestCaseGenerator.CommandLine.exe |
Test case generator. |
|
UiPath.UpdateService.Agent.exe |
Helper process used by the Auto-Update feature. |
|
UiPath.UpdateService.Launcher.exe |
Helper process for the Auto-Update feature. |
|
UiPath.UpdateService.Worker.exe |
Helper process used by the Auto-Update feature. |
|
UiRobot.exe |
The actual robot, it is used to facilitate the communication with other applications, such as Orchestrator, Studio, Assistant, or robot executor. |
Executables specific to each activity package are found in the activity package installation folder in the user profile.
%USERPROFILE%\.nuget\packages\<activity package name>\<package version>\build\.
The following executables related to the browser extension are found in the Studio installation folder:
|
Executable name |
Description |
|---|---|
|
ChromeNativeMessaging.exe |
Helper process for the browser extensions. |
|
createdump.exe |
Helper process for the browser extensions. |
|
UiPath.BrowserBridge.Portable.exe |
Helper process for the browser extensions. |
