Extension:
Extension Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Edge\Extensions
ID Active Version Correct Location Path
iodegoagldeabbkcidchfdifcghijihb No 2.13.0 No C:\Program Files (x86)\Pegasystems\Pega Browser Extension\BrowserExtensions\Edge\iodegoagldeabbkcidchfdifcghijihb_main.crx
@JeanChristopheD17042937 This is generally a symptom of not having the browser extension enabled. Are you using the old extension (which you should not be at this point) or have you installed PBE (Pega Browser Extension). PBE will show up in Add/Remove programs whereas the old extension will not. To enable PBE, you must follow the instructions and enable the extension via group policy.
@JeanChristopheD17042937 Note that you need to install the Pega Browser Extension (PBE) to avoid MV2 support issues. As has been noted in several client mailings, Google and Microsoft will begin disabling Manifest version 2 (MV2) browser extensions in June 2024. Once this occurs, you will no longer be able to automate Chrome and Edge using the MV2 extension that was originally released in Pega Robotic Automation 19.1.
Installing PBE will avoid this issue. You can download PBE and other Robotic Automation components from the My Software portal. For more information, see Downloading Pega Robotic Automation.
@MichaelNortonPega Robotic Automation for Browsers is activated on Edge to start interrogating web pages. PDF files are displayed correctly and recognized by PEGA but XML files are not readable without IE mode activated. How is it possible to have both ?
The error message you encountered, “Failed to connect to MessagingHost within the given timeframe of 20 seconds”, when interrogating a site in Microsoft Edge using Pega Robot Studio, usually indicates a problem with the browser extension or its communication with Pega’s messaging host.
Based on the details you provided, here are some areas to check and steps to troubleshoot:
Analysis of the Information Provided
The OpenSpan.WebExtensionInstaller status shows that the extension ID is defaulting to a private ID: lajjpilliikppcbaghjehndpfdiiphbe.
Messaging Host is correctly located and registered.
There are issues with the Extension:
The extension with ID iodegoagldeabbkcidchfdifcghijihb is not active and not in the correct location.
It indicates “Valid Extension Id: Fail” and “Valid Extension File: Fail”.
This suggests that the extension required for Pega’s integration with Edge is not correctly installed or registered.
Troubleshooting Steps
Reinstall the Edge Extension:
Uninstall the existing Pega Robot Studio extension from Microsoft Edge.
Manually reinstall the extension using the OpenSpan Web Extension Installer.
Open a Command Prompt as an administrator and run:
This command should install the necessary extension files correctly and ensure they are properly registered.
Check the Extension Installation:
After reinstalling the extension, open Edge and go to edge://extensions/.
Verify that the Pega Robot Studio extension is listed, enabled, and has the correct version.
Verify the Extension’s ID and Location:
Make sure the extension ID in the Edge browser matches the expected ID iodegoagldeabbkcidchfdifcghijihb.
Check the path specified for the extension file (C:\Program Files (x86)\Pegasystems\Pega Browser Extension\BrowserExtensions\Edge\iodegoagldeabbkcidchfdifcghijihb_main.crx) to confirm it exists.
Update Edge to the Latest Version:
Although it says that your Edge version is supported, ensure that your Edge browser is up-to-date. Compatibility issues can arise with older versions.
Restart the Machine:
After performing the steps above, restart your computer to ensure that all changes are properly applied.
Check Security and Permissions:
Ensure that you have administrative privileges on your machine when installing the extension.
Some antivirus or security software might block or interfere with the installation process. If you have such software, consider temporarily disabling it while you install the extension.
Run Pega Robot Studio as Administrator:
Sometimes, running Pega Robot Studio with elevated permissions can resolve issues related to browser extension communication.
Review Event Logs:
Check the Windows Event Viewer logs for any errors or warnings related to Pega Robot Studio or Edge. This can provide more information about why the messaging host failed to connect.
Additional Considerations
If the issue persists, try uninstalling and reinstalling Pega Robot Studio itself, as there might be corrupted files that need to be refreshed.
Make sure that there are no group policies or settings in your environment that might block third-party extensions in Edge.
These steps should help you resolve the issues with the Messaging Host connection when interrogating the browser site in Edge with Pega Robot Studio.
@MuhammadN17294368
Thanks for sharing these data, but still happening this kinda error.
I’d like to schedule an meeting and I hope you check this on meeting.
@JeanChristopheD17042937 It looks like everything is installed correctly, but the error suggests the MessagingHost isn’t responding in time. Try restarting Edge and Robot Studio, and make sure no security software is blocking the MessagingHost process. A system reboot can also help clear up the timeout issue.
@JeanChristopheD17042937 The Pega Browser Extension installer is bundled with either Studio or Runtime. Download the latest version of either to get the latest version of PBE (its version is independent of Runtime and Studio and is designed like Pega Native Foundation to be updated without having to update Runtime and Studio).
Chrome and Edge have restrictions on accessing files in the browser. They only allow accessing the files if enabled manually in the extension details page. You can find info in the link below.
It might be easier to download the file locally and read it some other way.
Have you tried to increase the StartTimeout on the Adapter? It might be taking more time for application to fully start and connect. If you’d like to have a meeting, definitely open an Incident with Pega Support to investigate it further.
