error internal could not identify process owning the current foreground window

#1
We automated one web based process. We have used surface automation as well in some of the obejcts.

The issue is that whenever we are running the process in the VM from the control room, without viewing it on a monitor, it is throwing the following exception for all the items in the Queue:

“error internal could not identify process owning the current foreground window”

But if we open the VM and view it on a monitor, it is working perfectly fine, without any exceptions.

Can somebody please help and guide how to resolve it on an urgent basis?
 
#4
hi all,
Anyone has solved this issue 'error internal could not identify process owning the current foreground window” ?
we have same issue . BP process via scheduler runs fine on RR if we monitor it or do "run now"
but it fails via scheduler .
 
#5
Hi ,

Anyone has solution for this issue 'error internal could not identify process owning the current foreground window” ?
I am facing same issue . BP process via scheduler runs fine on RR if we monitor it or do "run now"
but it fails via scheduler (Login agent) . And its sporadic in behavior . Reply if any one has solution for this , thank you
 
Top