https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55747#M10037 Blue Prism virtualisation guides strongly recommend against the use of RDP something that uses a VNC connection would be far better. There is a remote access tools data sheet in the product documentation area of this Portal. Wed, 29 Mar 2017 18:45:00 GMT Denis__Dennehy 2017-03-29T18:45:00Z https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55744#M10034 We get an error message when running the robot via a VDI in a java application €œCould not identify process owning the current foreground window€. We use a stage with €œActivate application€ (AA window) and then €œfocus€ on a java element within the window before sending global keys events to that application. The error message occurs on step 1 Activate application. The error is not frequent but still occurs at random intervals. Any suggestions on how to solve this issue? Tue, 29 Nov 2016 19:57:00 GMT https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55744#M10034 SimonAlopaeus 2016-11-29T19:57:00Z https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55745#M10035 Peter is correct. Please follow the advice given in the Product guides and datasheets regarding the Virtualisation tools that are used in your organisation. With RDP the desktop does not actually exist when no one is connected to it - so activates/global clicks/global send keys etc will all stop working. Thu, 15 Dec 2016 15:30:00 GMT https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55745#M10035 Denis__Dennehy 2016-12-15T15:30:00Z https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55746#M10036 I have also this issue and we are using the RD to connect to the robot. When running via RD the process works fine, but when closing the RD (log off and reboot since Login Agent will not work with out reboot...) and trying to run it via control room on a different BP we are getting this error on 'activate' step. Now does this mean that the fact the MS RD is installed does mess things up? since I'm not connected via RD on that robot while running process on that. So would disabling the MS RD and running something like VNC fix the issue? Tue, 28 Mar 2017 21:11:00 GMT https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55746#M10036 Anonymous 2017-03-28T21:11:00Z https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55747#M10037 Blue Prism virtualisation guides strongly recommend against the use of RDP something that uses a VNC connection would be far better. There is a remote access tools data sheet in the product documentation area of this Portal. Wed, 29 Mar 2017 18:45:00 GMT https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55747#M10037 Denis__Dennehy 2017-03-29T18:45:00Z https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55748#M10038 Hi everyone, We recently getting this issue when we run the automation remotely on a runtime resource. The automation fails whenever there is a stage like global send keys, clicks and Activate stage. We are using Citrix to access the VDE. I see there are lot of posts in the forum with the same problem. But I could not find a proper solution. I was just wondering if Is there step by step guide to resolve this issue. Thanks, Sai Wed, 15 Nov 2017 03:21:00 GMT https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55748#M10038 SaiGajjala_Venk 2017-11-15T03:21:00Z https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55749#M10039 Hi everyone, We recently getting this issue when we run the automation remotely on a runtime resource. The automation fails whenever there is a stage like global send keys, clicks and Activate stage. We are using Citrix to access the VDE. I see there are lot of posts in the forum with the same problem. But I could not find a proper solution. I was just wondering if there is a step by step guide to resolve this issue. Thanks, Sai Wed, 15 Nov 2017 03:21:00 GMT https://community.blueprism.com/t5/Product-Forum/Error-%C3%A2-%C5%93Could-not-identify-process-owning-the-current/m-p/55749#M10039 SaiGajjala_Venk 2017-11-15T03:21:00Z