- 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
- Variables
- Arguments
- Imported Namespaces
- 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
- Silverlight Extension troubleshooting
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Silverlight Extension troubleshooting
Silverlight browser applications can be opened only in Internet Explorer because all the other major browsers discontinued NPAPI - an API used by the Silverlight browser plugin. There are also standalone Silverlight applications that can be used outside of the browser.
A major Windows update, which changes the Windows version to 20H2 can break Silverlight interactions. To fix this issue, you must:
- Uninstall Silverlight Developer Runtime and the UiPath Extension for Silverlight.
- Install Silverlight Developer Runtime version 5.1.50918.0.
- Install the UiPath Extension for Silverlight.
<object>
HTML tag which can specify a windowless parameter. If the Silverlight target app has the
parameter windowless=false (which is the default) then there is no need to
activate the UiPath Extension for Silverlight because Active Accessibility and
UIA are already available. This also applies to out-of-browser Silverlight
applications.
You can check the windowless parameter as follows:
- For Internet Explorer Silverlight
applications - Use the DOM Explorer in Internet Explorer to search for the
<param name=”windowless” />tag under the corresponding<object />element. -
For out-of-browser Silverlight applications - Use UIExplorer to search for the
<param name=”windowless” />tag under the corresponding<object />element.Note: Silverlight automation only works with the Developer Runtime version installed.
If you’re having problems automating with the extension for Silverlight it is recommended to try the following:
-
Make sure you have Silverlight Developer Runtime and not the regular non-developer version. You have the developer runtime if one of the following files are present:
C:\Program Files (x86)\Microsoft Silverlight\5.1.50918.0\agcore.debug.dllC:\Program Files (x86)\Microsoft Silverlight\5.1.50918.0\dbgshim.dll
-
Check the Silverlight runtime version. The version needs to be 5.1.50918.0 and you can find it at the following locations:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlight(64bit) - in the Windows Registry Editor;HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Silverlight(32bit) - in the Windows Registry Editor;- The Settings > Apps & features window;
- The Details tab of the Silverlight installer file Properties.
- Go to the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Deskover\UiPathand look for the SLInstalled value, which is used by UiPath to keep track of the installation. If the value is 0, then the extension for Silverlight is disabled. -
Check if the
slinject.exe /installcommand created the required config file:C:\Program Files (x86)\Microsoft Silverlight\5.1.50918.0\System.Windows.ini. It needs to contain the following settings:GenerateTrackingInfo=1andAllowOptimize=0 -
At least one instance of the
sllauncher.exe /overwrite /emulate:"SLBroker.xap" /origin:"https://www.uipath.com/SLBroker.xap"process needs to exist at Silverlight apps automation startups. You can find the process using the Process Explorer tool. - If any of the previous steps did not pass automatically when installing the extension, you can try to complete them manually.
-
Collect traces while trying to select controls inside the Silverlight app as explained on this link. For regular ETL traces you can also set the
UIPATH_SLHOOK_CONSOLE_LOGGINGenvironment variable to 1 or true (case insensitive). This enables log messages and other debugging info in the browser console window (F12 to open). These messages are generated by the target Silverlight application and they are logged only in the browser console because of technical and performance limitations.Note: You have to set the environment variable before performing any UI automation. Make sure to restart UiPath and the Silverlight target application.
