• Cannot communicate with Internet Explorer browser

Help Activities
, ,
1

hello dears,

my problem as below,
we have an process on prod with no issues until we do the windows update,
the process start getting some failed transactions with below error: Open Browser: Cannot communicate with Internet Explorer browser.

after that we uninstall all the updated tools on this server and still getting this error on some transaction and I’m wondering why some of them work successfully and some of them gets this error.

appreciate your support

2

Check the internet explorer setting. Also check UiPath extension.

3

@Kismet_Tosun already checked

4

Try go to url

The image depicts a browser automation sequence where it first navigates to Google and then goes to the website "facebook.com.tr" using Google Chrome. (Captioned by AI)
The image depicts a browser automation sequence where it first navigates to Google and then goes to the website "facebook.com.tr" using Google Chrome. (Captioned by AI)610×484 14 KB

5

@Kismet_Tosun already used :sweat_smile:

6

@Yazan_Otaibi Kill before browser

7

@Kismet_Tosun
not understand what you say, please explain

8

Kill chrome before using open application browser activity

9

Hi @Yazan_Otaibi

UiPath browser extension may fail to launch on slow machines with high CPU usage

Description

The browser extension can fail to initialize on slow machines with high CPU usage. This issue can have one of two causes:

  • The Open Browser activity has an insufficient timeout.
  • In some cases, this Chromium bug can cause the extension to fail to initialize and the browser must be restarted. This issue affects all browser extensions.

Solution

Increase the Open Browser timeout. You can find more details on how to do that in the Known issues specific to MV3 extensions page under the Open Browser activity has insufficient timeout section.

If you’ve increased the timeout and the issue persists, set to True the Enable retry setting introduced with UI Automation version 2023.10 in Project Settings > UI Automation Classic > Browser > Enable retry for OpenBrowser Edge.

When this setting is enabled, the Open Browser logic restarts the browser several times if the Native Host failed to initialize within the given timeout.