cancel
Showing results for 
Search instead for 
Did you mean: 

Active Accessibility on Citrix

Louis-JulienGoo
Level 3
Hello, Our automated process are expected to run on VDIs trough Citrix. When connected to the vdi, the process run correctly but when we close it the process is not able to perform any action where the element have been spied with active accessibility. It just doesn't seem to do anything at these moments but the process does not crash. We expect to do clicks (with or without coordinates) and other regular actions. We already try to do a "Maximize" of the application before executing the action. We already try to do an "Activate" of the application but here we receive an error ("Could not identify process owning the current foreground window") Do you have any idea to fix this ? Note : The process is working fine for actions using W32 spying mode but we are forced to use AA in some cases. For Win32 application developed in vb.net (but any other applications suffer from the same). We already disabled screensaver, sleep / hibernation modes and screen lock. Thanks
3 REPLIES 3

Denis__Dennehy
Level 15
Stop using RDP - as mentioned in the Blue Prism product guides/datasheets - and engage with your technical architect/lead to provision a virtualised environment and way of connecting to that environment, that adheres to the Blue Prism reference and and virtualisation guides. You are getting your errors because your virtual invironment is not persistent and/or consistent - so the desktop effectively does not exist when you are not connected to it.

Louis-JulienGoo
Level 3
Hello, In this case we are not using RDP but the protocol ICA with XenDesktop inside Citrix. When we make some tests, like getting the button or window positions with Get Bounds and Get Screen Bounds, we see that the positions are the same with the Citrix window open or closed giving me the hint that the virtual environment is still there. Thanks

Denis__Dennehy
Level 15
There is a knowledgebase article on this error: https://blueprism.knowledgeowl.com/help/error-could-not-identify-proces I would still suggest the issue will be with the virtualised environment - ask your technical architect to ensure the requirements outlined in the BP virtualisation guide and product data sheets have all been kept to.