Skip to main content
Solved

BotLauncher: Could not connect to browser agent through named pipe- HRESULT: 2-2147024894

  • May 19, 2025
  • 2 replies
  • 98 views

Forum|alt.badge.img+1

Hello,

my bot is unable to use the chrome browser objects after a machine restart.

It can start the browser and active the window, but it will not interact with any objects on the webpage.
The Botluncher log on the machine contain this error:

ERROR [BotRunner-c7dc9735-0323-4faa-b765-1b9eeb186bc9_e21e0d997223043d] - com.automationanywhere.webbrowser.adapter.ChromiumBrowserAdapter {deploymentId=c7dc9735-0323-4faa-b765-1b9eeb186bc9_e21e0d997223043d, traceId=e21e0d997223043d} - executeBrowserRequest(ChromiumBrowserAdapter.java:357) - Error occurred while executing Chrome browser request. Retrying... java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Could not connect to browser agent through named pipe- HRESULT: 2-2147024894


Does anybody else has experienced this issue or had a similar problem with the named pipe and has an idea how to fix this?

Best answer by Aaron.Gleason

Chrome make a change recently. If you still had the old AA extension, it was unceremoniously removed by Chrome. This happened to me too!

If so, reinstall the extension here:

https://chromewebstore.google.com/detail/automation-360/bboccnojhhoegfffpcllbeigipedjedf

If not, try removing and reinstalling the extension manually.

2 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+14
  • Automation Anywhere Team
  • Answer
  • May 19, 2025

Chrome make a change recently. If you still had the old AA extension, it was unceremoniously removed by Chrome. This happened to me too!

If so, reinstall the extension here:

https://chromewebstore.google.com/detail/automation-360/bboccnojhhoegfffpcllbeigipedjedf

If not, try removing and reinstalling the extension manually.


Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • May 19, 2025

Thank you, ​@Aaron.Gleason 
I was using the new version of the chrome plugin, but good point.
Meanwhile I reinstalled the plugin and the bot agent (completly wiped it). Now it is working again.