<?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 Could not identify process owning the current foreground window in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/80159#M31928</link>
    <description>Hi,

We are running a BOT on a Virtual Machine ( VM ) . While the BOT is running if we disconnect VM and login again we are seeing below error.

&amp;nbsp;

ERROR: Internal : Failed To perform Step 1 In Navigate Stage 'Activate' on page 'SetUpPayroll' - Could not identify process owning the current foreground window.

&amp;nbsp;

Regards,

Datasci9</description>
    <pubDate>Fri, 09 Feb 2018 11:09:00 GMT</pubDate>
    <dc:creator>Venkata_Subba_R</dc:creator>
    <dc:date>2018-02-09T11:09:00Z</dc:date>
    <item>
      <title>Could not identify process owning the current foreground window</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/80159#M31928</link>
      <description>Hi,

We are running a BOT on a Virtual Machine ( VM ) . While the BOT is running if we disconnect VM and login again we are seeing below error.

&amp;nbsp;

ERROR: Internal : Failed To perform Step 1 In Navigate Stage 'Activate' on page 'SetUpPayroll' - Could not identify process owning the current foreground window.

&amp;nbsp;

Regards,

Datasci9</description>
      <pubDate>Fri, 09 Feb 2018 11:09:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/80159#M31928</guid>
      <dc:creator>Venkata_Subba_R</dc:creator>
      <dc:date>2018-02-09T11:09:00Z</dc:date>
    </item>
    <item>
      <title>Are you using RDP to connect…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/80160#M31929</link>
      <description>Are you using RDP to connect to the VM? RDP is specifically not recommended by BP for a number of reasons, but mainly because the desktop does not persist when the connection is closed. &lt;A href="http://portal.blueprism.com/system/files/2017-11/v6%20Data%20Sheet%20-%20Remote%20Access%20Tools.pdf" target="test_blank"&gt;http://portal.blueprism.com/system/files/2017-11/v6%20Data%20Sheet%20-%20Remote%20Access%20Tools.pdf&lt;/A&gt;</description>
      <pubDate>Fri, 09 Feb 2018 14:25:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/80160#M31929</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2018-02-09T14:25:00Z</dc:date>
    </item>
    <item>
      <title>I would advise to restart…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/80161#M31930</link>
      <description>I would advise to restart the VM after any RDP connections. Only then can you know where you are with the window/screen automations.</description>
      <pubDate>Mon, 19 Feb 2018 20:01:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/80161#M31930</guid>
      <dc:creator>Anton__Hosang</dc:creator>
      <dc:date>2018-02-19T20:01:00Z</dc:date>
    </item>
  </channel>
</rss>

