studio
2023.10
false
- 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
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- About the ScreenScrapeJavaSupport Tool
- Argument Descriptions for 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 package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- 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
- 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 User Guide
Last updated Dec 19, 2024
About the ScreenScrapeJavaSupport Tool
A machine can have different Java versions installed (such as 32-bit and 64-bit), and in different locations, so you need the Java extension to be able to help you build automations regardless of the version. This is where the ScreenScrapeJavaSupport tool comes in handy. It is meant to help you install and uninstall the Java extension, but also to give you info about the installed Java versions and what processes have the extension loaded. Moreover, you can especially benefit from this tool if you have Java installed in custom locations.
The ScreenScrapeJavaSupport tool is installed with Studio, and can be found in the
C:\Program Files\UiPath\Studio\UiPath\JavaSupport folder.
Note: The ScrenScrapeJavaSupport tool requires administrator privileges.
The Java extension can be installed in the default location of 32-bit an 64-bit versions of Java, on all drives, or in a custom location.
ScreenScrapeJavaSupport.exe /install /jrepath "<path>"- Installs the Java extension for the specified path. The path is the folder path containing thejava.dllfile. If the Java extension is already installed then it reinstalls it.ScreenScrapeJavaSupport.exe /install /default- Searches for the default Java installation folder, Program Files or Program Files (x86), and installs the Java extension there. This is because both Java x86 and x64 can be installed on the same machine.ScreenScrapeJavaSupport.exe /install /allDrives- Recursively searches all fixed drives for Java versions, and installs the Java extension for each one.ScreenScrapeJavaSupport.exe /install- Reinstalls the Java extension for all the Java versions that are currently installed. The ScreenScrapeJavaSupport tool keeps a record of each version it installs.
Upon removal, the Java extension path is remembered, unless removed from the log with the
/forget argument.
ScreenScrapeJavaSupport.exe /uninstall /jrepath "<path>"- Uninstalls the Java extension from the specified path.ScreenScrapeJavaSupport.exe /uninstall- Uninstalls the Java extension from the system.ScreenScrapeJavaSupport.exe /uninstall /allDrives- Uninstalls the Java extension from all fixed drives.
