Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Error "Could not identify process owning the current foreground window" for elements spied in AA mode

Anonymous
Not applicable

‎08-04-16 06:42 AM

We have some elements that are spied in Active Accessibility mode. When the process is executed in resourcePC from Client's control room, the software fails to sense those elements. It throws "Could not identify process owning the current foreground window" error at those stages. Do we have any workaround for this? We are running on 4.2.47 version.
0 Likes
1 REPLY 1

Denis__Dennehy
Level 15

‎16-04-16 08:14 PM

Foreground window errors are often related to screen lock being on, especially if global clicks are required (which is usually the case with Active Accessibility). Also, where you are using global clicks, are you first activating the application main window - with a tiny wait to give the window time to become active? Are your virtual pc's set up in accordance with the Blue Prism infastructure guides (you should not be using rdp to connect/disconnect as the screen will not exist after you disconnect) and Is the screenlock on your virtual PC disabled?
0 Likes