topic Have you figured out a… in Product Forum

Could not identify process owning the current foreground window - Alternate solutions?

IshaSingh — Tue, 16 Jan 2018 12:08:00 GMT

Hi Everyone, I am facing an issue while activating an excel window via my VM. I have used AA for spying the excel since it has customised tabs that need to be clicked. I am using the toolbar to activate the window. When I perform a check exists on it, it finds it but on using Activate it throws the error 'ERROR: Internal : Failed to perform step 1 in Navigate Stage 'Activate Excel' on page 'Supplier Search' - Could not identify process owning the current foreground window'. I have gone through the Knowledge Base article on this error but the solutions aren't suiting my process. The solution list is: Use the Activate Application function on a Win32 or AA element with the whole application selected: The error itself comes on Activating an application. Setting the Focus on an element within a window, if that action is applicable to the element: The same error comes when I try to focus same element. Immediately after a Launch action has been used, set a conditional Wait for an element of the application before attempting the next action: This is already in place and there are multiple element checks and interactions which come successful. Any help or ideas would help. Thanks, Isha.

Hi Isha - try spying the…

John__Carter — Tue, 16 Jan 2018 14:00:00 GMT

Hi Isha - try spying the main window as a Win32 element and use that to call Activate. I find this tends to be more reliable.

Hi John,…

IshaSingh — Tue, 16 Jan 2018 15:29:00 GMT

Hi John, The main window does not get spied. There's a small box that comes close to the boundaries if I try to spy the window. See attached image please.

This error comes only when I…

IshaSingh — Tue, 16 Jan 2018 15:31:00 GMT

This error comes only when I'm running this on a runtime VM. When I try to run it on my interactive client for testing, it runs perfectly.

I encountered the same error…

AndrzejKaczor — Thu, 18 Jan 2018 17:36:00 GMT

I encountered the same error, when there were multiple users logged in into the same system. That could also happen if the user has been connected to the machine using windows ""Remote Desktop Connection"". Id' try to restart machine and then log in into it using ""log in"" action for ""user Agent"" object.

Have you figured out a…

TomMaloney1 — Sat, 27 Jan 2018 23:30:00 GMT

Have you figured out a solution to this issue yet?

Hi Andrzej,…

IshaSingh — Sun, 28 Jan 2018 17:16:00 GMT

Hi Andrzej, Yes you're right. This was the problem. Thanks! @Tom: Yes this is solved 🙂

Sorry, but I am also facing…

RaviKumar3 — Tue, 06 Feb 2018 21:56:00 GMT

Sorry, but I am also facing the same issue and even I did not get what is the exact solution..Please elaborate in detail if you can?

I believe Isha was referring…

Nripa_KrishnaMa — Thu, 15 Feb 2018 23:42:00 GMT

I believe Isha was referring to Andrej's solution above. I'm facing the same problem. I have tried same solution. I'm yet to check the result of this though.

Update - I have tried the…

Nripa_KrishnaMa — Mon, 19 Feb 2018 09:49:00 GMT

Update - I have tried the solution and it did work for me.

Andrzej.Kaczor,…

gouthamedara — Fri, 20 Apr 2018 23:35:00 GMT

Andrzej.Kaczor, That is good for one instance. What if this is happening regularly? I believe we are following all the security policies as mentioned in the BP document. I am confused why this is still happening.