Unable to identify the process owning the foreground window.

[nirmishra]

Hi,

I am facing issue while interacting with UIA elements, getting system Exception saying “Unable to identify the process owning the foreground window.”

Resolutions tried so far:

1. Added “Activate application” spying Chrome in Windows Mode
2. Added “Attach”
3. Used browser mode with focus and Global Send Keys with Enter

Has anyone faced similar issue(s) or suggest how can we tackle this scenario

[steven.boggs]

Some context and environmental information would be useful for others to provide a recommendation here:

- Is this a new Process that has never been run successfully, or was it working previously without issue? 

     - If working previously, what has recently changed in the environment (e.g. Chrome version upgrade, O/S patching, development updates to the Process, etc.)? 
          - When was this Process last run successfully without issue?

- Can you identify a specific stage (or UIA element) at which the Process reliably fails with this error, or does the issue seem to occur at different points each time?

- What is the version of Chrome in use (i.e. the details from the chrome://version page)?

- What is the specific version of the Blue Prism browser extension in use?

- What is the Blue Prism version in use in this environment (e.g. v6.10.6, v7.4.1, etc.)?

[naveed_raza]

we are also facing this issue from last couple of weeks , we are on version 6.10.5.

Its weird when we are keeping the bot in open mode and running the process its running perfectly fine and when we are running the process without opening the bot then its failing with foreground error.

We fixed this ,by identifying one of the label on the page and pressing the tab using global sendkeys and entering the user id and password and we are facing this only on login page.

probably you can try this..

[nirmishra]

- Is this a new Process that has never been run successfully, or was it working previously without issue? 

Process running fine in Production previously

- If working previously, what has recently changed in the environment (e.g. Chrome version upgrade, O/S patching, development updates to the Process, etc.)?

Nothing has changed

- When was this Process last run successfully without issue?

a week ago

- Can you identify a specific stage (or UIA element) at which the Process reliably fails with this error, or does the issue seem to occur at different points each time?

currently failing at one element but when I skip it, BOT tend to fail for next UIA spied element

- What is the version of Chrome in use (i.e. the details from the chrome://version page)?

- What is the specific version of the Blue Prism browser extension in use?

6.10.4 BluePrism Version and Browser Automation Agent replacing Manifest v2 extension(implemented months ago)

- What is the Blue Prism version in use in this environment (e.g. v6.10.6, v7.4.1, etc.)?

Production environment - 6.10.4

[nirmishra]

Thanks Naveed, will try to implement this approach and inform back if it resolves the issue.

[naveed_raza]

sure.. let me know . i hope it should work