Skip to main content
udayabhaskard0583
udayabhaskard0583
February 21, 2024
Question

Robotic task is not opening browser with the message DevToolsActivePort file doesn't exist

  • February 21, 2024
  • 6 replies
  • 0 views

Hi All,

We are trying to build new RPA use case to open browser and download file and bringing back to Appian.

Earlier the robitc task was working fine with below browser and driver versions. 

Browser: Chrome  (121.0.6167.161)

Driver Version: 121.0.6167.85

After the chrome got upgraded the robotic task is not able to launch brower with the below browser & driver version: 

Browser: Chrome  (121.0.6167.185)

Driver Version: 121.0.6167.184

Robotic task is failing with below error:

[INFO] 2024-02-21 05:23:03 03s (0h) - Browser version: 121.0.6167.185, Driver version: 121.0.6167.184
[INFO] 2024-02-21 05:23:03 03s (0h) - WebDriver file is out of date. Attempting to auto resolve it from the console...
[INFO] 2024-02-21 05:23:06 07s (0h) - Successfully auto resolved webDriver from RPA console
[DEBUG] 2024-02-21 05:23:06 07s (0h) - Using default module Chrome options
[WARN] 2024-02-21 05:23:09 10s (0h) - Driver could not be initialized: session not created: Chrome failed to start: exited normally.
(session not created: DevToolsActivePort file doesn't exist)
(The process started from chrome location C:\Program Files\Google\Chrome\Application\chrome.exe is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'XXX-XXXX-XXXXX', ip: 'XX.XX.XX.XXX', os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '21.0.2'
Driver info: driver.version: ChromeDriver

Regards,

Udaya Dumpa

6 replies

T
tien.bui
February 21, 2024

Could you try clearing your webdriver cache on your machine and try again? You'll find your cached webdrivers in the workspace folder where you installed your agent, somewhere like \AppData\Local\Appian RPA\Jidoka-workspace. 

udayabhaskard0583
udayabhaskard0583Author
February 22, 2024

Hi Tien,

We have cleared the webdriver cache and the issue still persist.  

Regards,

Udaya Dumpa

kishorej1999
kishorej1999
March 6, 2024

Hii [mention:f7b0aed71378480cb43583e21aefbc51:e9ed411860ed4f2ba0265705b8793d05] ,

The more you can do is to follow the certain steps:

Go to Appian RPA from the Navigation Tiles > Select the Setting tab > Select configuration > check the "select Allow Appian to provide selenium web drivers" in the security policy section.

So what we are doing is if the Chrome driver is not working then this will automatically pick you current chrome version and will help to run the robot. 

i hope this will going work. let me know if it's not.

Thanks

udayabhaskard0583
udayabhaskard0583Author
March 6, 2024

Hi [mention:2fd5a06d969042519af3b5b1c9018e0f:e9ed411860ed4f2ba0265705b8793d05] ,

The checkbox was already checked. When robot is executing it was able to load the correct driver version based on the chrome version. On the next step it's failing to open the browser session.

Regards,

Udaya Dumpa

kishorej1999
kishorej1999
March 6, 2024

Hii [mention:f7b0aed71378480cb43583e21aefbc51:e9ed411860ed4f2ba0265705b8793d05] ,

In that case you can reinstall the chrome to resolve this issue.

Thanks!!

Terms & ConditionsAccessibility statement