Native Messaging Host (Blueprism.MessagingHost.exe) launch delay (Edge Chromium)

[flavio.lara]

Hello All,

We are upgrading from Blue Prism 6.10.2 to 7.3.1, but We've encountered an issue with Microsoft Edge Chromium and the Native Messaging Host (Blueprism.MessagingHost.exe).

Automation that normally worked in 6.10.2 generates an exception when launching in 7.3.1 in Studio Mode. The exception is: Could not open target process. I've checked this article, but in our case, the problem has a different cause: BPE error: "Could not open target process" when launching or attaching to an application in the Object Studio : (blueprism.com)

I noticed it's caused by the fact that BluePrism.MessagingHost.exe takes a long time to load. Under my account, it's about 20 seconds. I've tried changing the Messaging Host Detection timeout parameter inside extension options, to 30 or 60 seconds, without success.

If I start MS Edge using a "Utility Environment::Start Process" action, wait for BluePrism.MessagingHost.exe process, and then attach my object to the website, everything works fine.

I've checked the Troubleshooting browser integration (blueprism.com). No item suits my case.

I've checked the BPE error "The browser extension was not detected" when attempting to launch a browser based (Chrome, Firefox or Edge Chromium) application : (blueprism.com) trying to find some clue. Without success here.

Changing this parameter in Automate.exe.config didn't work as well.

Has anyone else come across this and found a solution? 

Thanks in advance,

[stepher]

@maneesh.vemula1 ,

I might have a lead on that for you.

For context, all of our Runtime machines use the same 'Profile' in MS Edge, based on the fact that we use one login/credential for our Runtimes.  Additionally, I have a fairly extensive set of changes that I and my Operations team makes to the default MS Edge settings.  Specific to your question is Settings/Profile/Synch.  By default, all Synch options are selected, but, historically, we deselected all options except 'Settings' and 'Extensions'.  The problem came when we started are initial deployment of 7.3 Runtimes--suddenly machines had both the 6.10 and the 7.3 extension, with one deactivated (usually the 7.3 version).  Needless to say, we have deactivated the 'Extensions' synch since we cleaned everything up.

Good luck,

Red

[maneesh.vemula1]

Thanks @stepher - Our machines also had both extensions due to some chrome settings which led to the old extension still being active. We removed the old one and installed the new one which seemed to have resolved the issue. 

However, we came across a new issue this while upgrading our test environment, the below popup seems to appear when I try to run a process on a machine. Once i click Ok, I am able to see the pending session and run the process after another appearance by the same pop-up. Any thoughts @John__Carter  or others in this chat. 

[flavio.lara]

Hello @maneesh.vemula1 .

on your application server, call bpserver.exe and change the hostname from "localhost" to the complete FQDN (host + DNS domain).