SS&C Blue Prism Community

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

• SS&C Blue Prism Community
• Get Help
• Product Forum
• Solution: The port establishing the connection to .

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

I recently faced several issues regarding the extension and would like to share with you how it was resolved.

Objectively, here are the important points:

1. Can you verify the version of Chrome and the extension you are running? https://bpdocs.blueprism.com/ browser-compatibility.htm

2. Is this a newly built environment that has always had this issue, or was this working until recently?

3. Are you using Ephemeral or fixed ports? (This can be checked at the bottom of System> System > Settings> Browser Extension Connectivity)

4. Can you please ensure the Startup Boost and 'Continue running background extensions and app when Microsoft Edge is closed' are disabled? (We recommend this even when you are interacting with Chrome) To do this, open Edge and browse to edge://settings/system, and ensure that those are unchecked, as seen below:

To do this, open Chrome and browse to chrome://settings/system, and ensure that the 'Continue Running background apps when Google Chrome is closed' option is unchecked, as seen below:

6. I would recommend you read this articule and try some suggestions to help resolve this issue. Please see the link for this article below: [KB] What are the key considerations when working with Modern Browser Automations?

if the first step doesn't work:

Application manager mode

Application Manager can run in several different modes to allow separation of the target interface process from Blue Prism itself. This can be useful, for example, if Blue Prism is running as a 32 bit process and the target application is a 64 bit process, or vice versa.

The available modes are:

• Embedded (default) – This is the default mode, and was the only available mode of operation prior to Blue Prism version 4.2. In this mode, Application Manager runs in the same process as Blue Prism itself. There is no separation.
• External, 32 bit mode – Application Manager runs in a separate process when interfacing with the target application. The Application Manager process is always 32 bit.
• External, 64 bit mode – Application Manager runs in a separate process when interfacing with the target application. The Application Manager process is always 64 bit.
• External, OS address size – Application Manager runs in a separate process when interfacing with the target application. The Application Manager process matches the operation system address size. e.g. on 64 bit Windows, it will be a 64 bit process.
• External, Blue Prism address size – Application Manager runs in a separate process when interfacing with the target application. The Application Manager process matches Blue Prism's address size. e.g. if Blue Prism is running as a 64 bit process, the Application Manager process will also be 64 bit.

In my case it was as Embedded (default) and according to my settings I changed it to External, 64 bit mode. After this adjustment my biggest problem was solved! I had a huge process that went through the browser flows several times, opening, closing several tabs and at the beginning there was already the extension problem, in 24 hours after this adjustment I was able to perform more than 250x the flow without giving any extension problem.

I hope to contribute to the community and that this topic is a support for those who are going through this difficulty.