https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86643#M37468 Any solution to this? Bump Wed, 28 Mar 2018 07:19:00 GMT ZaidRab 2018-03-28T07:19:00Z https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86641#M37466 We are running two RPAs on one runtime (scheduled). The first process is completing 12 mins before next starts. e.g P1 completes at 11:48 and P2 Starts at 12:00 Problem: when scheduler runs P2 BP gives 'Could not identify process owning the current foreground window' error and terminates. When we login to runtime resource and start the process manually everything works fine.   Runtime resources are configured as per BP recommendations like there is no lock and local security policy are set as per recommendations   Tue, 13 Mar 2018 09:43:00 GMT https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86641#M37466 M_Zubair 2018-03-13T09:43:00Z https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86642#M37467 If you are using RDP to connect to the resource machines, this could produce the effect you describe. RDP is specifically not recommended because the desktop of the remote machine is destroyed once the connection is closed and recreated only when you reconnect. One answer is to use Login Agent to lout and back in after you have disconnected RDP, but the best option is to use a non-invasive remote access tool. Tue, 13 Mar 2018 12:57:00 GMT https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86642#M37467 John__Carter 2018-03-13T12:57:00Z https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86643#M37468 Any solution to this? Bump Wed, 28 Mar 2018 07:19:00 GMT https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86643#M37468 ZaidRab 2018-03-28T07:19:00Z https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86644#M37469 To my knowledge, that error is basically saying that the session window is locked or not exists. Please follow BP recommendations and configure persistent runtime resource (RDP should not be used). Another tip is to also check the GLOBAL security policies of the robots group, avoiding any potential overwrite. Login Agent can be a workaround to tackle this problem, but not resolving it. Tue, 24 Apr 2018 13:32:00 GMT https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86644#M37469 TengWang 2018-04-24T13:32:00Z https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86645#M37470 We are also facing the same issue 'Could not identify process owning the current foreground window' error when we schedule the application through LoginAgent in RDP machines. Out of 10 times one or two times is recognizing the window and rest it is failing.   May I know non-intrusive console? Is it VNC viewer? If yes, how to install this ? As per my understanding VNC server would be installed into BOT machines(Resource PC) and VNC client would be installed in App server. Am I right? Pls clarify on it. thanks in Advance. Wed, 26 Sep 2018 10:53:00 GMT https://community.blueprism.com/t5/Product-Forum/Could-not-identify-process-owning-the-current-foreground-window/m-p/86645#M37470 GuptaKancharla1 2018-09-26T10:53:00Z