VDI Issues

[Ansar_AhmedAtta]

Hi Everyone, We are facing issues when we switch VDIs. Basically when we are running a process on the same VDI the process is running fine but when we make one VDI as control room and run the process on some other VDI(UNATTENDED RUN)  it just can't find that spied field, the error says unable to match any active accessibility elements. The spied field is a textbox in login window in a M4A excel workbook. Any suggestions.?

[John__Carter]

Sounds like there is something in the application model specific to the previous environment. I'd suggest experimenting with the element attributes in the new environment to see what is causing the mismatch. The error message is BP telling you 'there is no element matching the attributes you have specified'.

[Ansar_AhmedAtta]

Thanks John, Yes exactly the same error but we have checked the app model and there is nothing as such attribute, still we are facing the issue when the run is unattended.

[John__Carter]

When the process runs on the local machine, is it via the diagram? If it is, then the problem in running the process on the other machine is likely to be due the fact that a process runs much faster in control room. The fastest process studio speed is slower than control room, and if the object synchronisation logic is weak, often it's the slow speed of the diagram that is enabling it to work. The weakness is exposed when the process tries to run at high speed via control room.

[Ansar_AhmedAtta]

In both runs, attended as well as unattended, the process is running via control room. it is the same error every time,unable to match any AA terms.

[John__Carter]

OK, are you using RDP to access the resource machine? RDP is not a remote access tool we recommend, partly because it destroys the remote desktop once you disconnect the session, and this has a negative effect on certain aspects of BP like global mouse click and surface automation. I've not heard of it affecting AA before, but it might. If BP is saying 'cannot match any element' it must mean that 1) the element is really not there at that moment in time, or 2) the element is there but the selection of attributes in the application model are not a match.