<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Native Messaging Host launch delay in Chrome in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/97184#M45257</link>
    <description>Hello All,&lt;BR /&gt;&lt;BR /&gt;We are in the process of moving automations from Blue Prism 6.6 to 7.1.2, but I've come across an issue with Chrome and the Native Messaging Host.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Automations that normally worked in 6.6 generate an exception when launching in 7.1.2 in Studio Mode. I have not gotten any further yet. The exception is generated because Blue Prism cannot connect with the browser extension, and after a bit of troubleshooting I noticed it's caused by the fact that&amp;nbsp;&lt;EM&gt;BluePrism.MessagingHost.exe&amp;nbsp;&lt;/EM&gt;takes a very long time to load. Under my own account it's ~20 seconds, and after changing the &lt;EM&gt;Messaging Host Detection&amp;nbsp;&lt;/EM&gt;timeout to 25 seconds, launches started working.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Then I tried it in the Digital Worker account, and for some reason the Messaging Host executable pops up in Task Manager more than 50 seconds after launch.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I am about to resort to starting Chrome via the Utility - Environment Business Object with an Exception-Timeout loop as it's the easiest solution, but I feel that Launch should be doing what it's designed for.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It worked just fine in 6.6, so I don't understand why it is broken in 7.1.2.&lt;BR /&gt;&lt;BR /&gt;Has anyone else come across this and found a solution?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;&lt;BR /&gt;Pawel</description>
    <pubDate>Wed, 01 Feb 2023 14:49:44 GMT</pubDate>
    <dc:creator>PawelMrozik</dc:creator>
    <dc:date>2023-02-01T14:49:44Z</dc:date>
    <item>
      <title>Native Messaging Host launch delay in Chrome</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/97184#M45257</link>
      <description>Hello All,&lt;BR /&gt;&lt;BR /&gt;We are in the process of moving automations from Blue Prism 6.6 to 7.1.2, but I've come across an issue with Chrome and the Native Messaging Host.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Automations that normally worked in 6.6 generate an exception when launching in 7.1.2 in Studio Mode. I have not gotten any further yet. The exception is generated because Blue Prism cannot connect with the browser extension, and after a bit of troubleshooting I noticed it's caused by the fact that&amp;nbsp;&lt;EM&gt;BluePrism.MessagingHost.exe&amp;nbsp;&lt;/EM&gt;takes a very long time to load. Under my own account it's ~20 seconds, and after changing the &lt;EM&gt;Messaging Host Detection&amp;nbsp;&lt;/EM&gt;timeout to 25 seconds, launches started working.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Then I tried it in the Digital Worker account, and for some reason the Messaging Host executable pops up in Task Manager more than 50 seconds after launch.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I am about to resort to starting Chrome via the Utility - Environment Business Object with an Exception-Timeout loop as it's the easiest solution, but I feel that Launch should be doing what it's designed for.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It worked just fine in 6.6, so I don't understand why it is broken in 7.1.2.&lt;BR /&gt;&lt;BR /&gt;Has anyone else come across this and found a solution?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;&lt;BR /&gt;Pawel</description>
      <pubDate>Wed, 01 Feb 2023 14:49:44 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/97184#M45257</guid>
      <dc:creator>PawelMrozik</dc:creator>
      <dc:date>2023-02-01T14:49:44Z</dc:date>
    </item>
    <item>
      <title>Re: Native Messaging Host launch delay in Chrome</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/97185#M45258</link>
      <description>Try resetting the browser extension options in chrome to their defaults. it's a new addition to 7.1.2 chrome extension.</description>
      <pubDate>Wed, 01 Feb 2023 17:08:02 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/97185#M45258</guid>
      <dc:creator>PhilipDeveau</dc:creator>
      <dc:date>2023-02-01T17:08:02Z</dc:date>
    </item>
    <item>
      <title>Re: Native Messaging Host launch delay in Chrome</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/97186#M45259</link>
      <description>Hi Phil,&lt;BR /&gt;&lt;BR /&gt;Resetting the browser extension options did not work.&lt;BR /&gt;&lt;BR /&gt;Here's what I ended up doing:&lt;BR /&gt;&lt;BR /&gt;
&lt;OL&gt;
&lt;LI&gt;Launch Chrome manually via Utility - Environment - Start Process&lt;/LI&gt;
&lt;LI&gt;Wait for "BluePrism.MessagingHost" via Utility - Environment - Wait for Process&lt;/LI&gt;
&lt;LI&gt;Attach&lt;/LI&gt;
&lt;/OL&gt;
&lt;BR /&gt;It still takes about 50+ seconds before the process is found, but at least it will attach.&lt;BR /&gt;&lt;BR /&gt;Take care,&lt;BR /&gt;&lt;BR /&gt;Pawel</description>
      <pubDate>Thu, 02 Feb 2023 12:56:32 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/97186#M45259</guid>
      <dc:creator>PawelMrozik</dc:creator>
      <dc:date>2023-02-02T12:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: Native Messaging Host launch delay in Chrome</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/110854#M49955</link>
      <description>&lt;P&gt;Hi Pavel,&lt;/P&gt;&lt;P&gt;I am facing same issue but the delay is nearly 8 mn. Did you find any other solution?&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2024 11:46:32 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/110854#M49955</guid>
      <dc:creator>VinodKumar5003</dc:creator>
      <dc:date>2024-05-24T11:46:32Z</dc:date>
    </item>
    <item>
      <title>Re: Native Messaging Host launch delay in Chrome</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/116265#M52135</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/1585"&gt;@PawelMrozik&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;I'm facing an issue similar to yours... the&amp;nbsp;Native Messaging Host is affecting "Launch" actions, but for me, it's a lack of waiting in the internal "Launch" code (if I wait for the process to start, the following actions work normally).&lt;/P&gt;&lt;P&gt;Changing the Extension parameters didn't work for me (if you have any tips), the behavior is the same. We are using BP v7.3.1 (migrating from v6.10.2).&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;Did you find another solution besides calling MS Edge using "Utility - Environment: Start process"?&lt;BR /&gt;&lt;BR /&gt;All documentation I've found on Blue Prism website doesn't fit our scenario.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 14 Oct 2024 19:01:07 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-launch-delay-in-Chrome/m-p/116265#M52135</guid>
      <dc:creator>flavio.lara</dc:creator>
      <dc:date>2024-10-14T19:01:07Z</dc:date>
    </item>
  </channel>
</rss>

