When investigating the issue with Process monitor open for ARD Desktop client, we could see that two DLLs from Microfocus UFT software are conflicting with ARD.
Release : 3.1
Component : Microsoft TFS Integration
This is not a product defect and is specific to customer environment where ARD and Microfocus products are running together.
It cannot be fixed from Broadcom ARD side as we have not have licenses or support agreement with MicroFocus to contact and discuss such issues.
However, looking at the issue, below inputs are shared which may help customer team(s) to get it fixed from MF-UFT side.
- UFT appears to be a windows application UI testing tool which works by intercepting interaction events (i.e. clicks, key strokes, drags, drops etc.) through a series of injected DLLs. ARD has been built by using the third party QT library. QT library does not fully conform with the general Windows event architecture. Because of this, UFT ends up "poisoning" the event loop of ARD, instead of just quietly intercepting it. This cannot be fixed in ARD.
- It is "expected" that UFT has a method of whitelisting/exempting applications from monitoring and that might be the key in making them work together. Customer can work with UFT SMEs and UFT support that would be able to do that.