[Ranorex 5.4] Failed to instrument WPF process.

[AnaSal]

Hello,

I am using Ranorex 5.4 for the automated testing of a WPF desktop application. Under the Settings of Ranorex Spy, I have selected:

Plugins -> WPF -> WPF Legacy/UIA Interaction: WpfOnly

Nevertheless, whenever I try to track an element of the application, Ranorex shows the following error and only the UIA tree is shown.
"Failed to instrument WPF process. UI element identification capabilities for this window are limited."

My system, where Ranorex is installed, runs:
Windows 7 SP1
.NET 4.5.2, .NET 4.5.1 developer pack

So far, I tried to uninstall Ranorex and all my .NET installations and then install the again. But the Ranorex WPF error still occurs. Is this a known bug? How can it be solved?

Thank you for your support.

[Support Team]

Hello AnaSal,

Which version of Ranorex are you exactly using?
There was a bug in Ranorex 5.4.2 which should be fixed in 5.4.3.
Please download 5.4.3 and check if the issue still persists.

Regards,
Bernhard

[AnaSal]

Hello,

I upgraded to Ranorex 5.4.3 and now WPF plugin works again.
Thanks for the support.

[SPluemper]

Hello,
now I get the error at 6.0 again.
I have tried your solution for this, setting "WPF Legacy/UIA Interaction" to "WpfOnly", but the message occurs every start.
And I don't know what you mean with "WpfElement" window at Spy, there is no such window - it is a Qt5 application, could that be the problem ?

[Support Team]

Hello SPluemper,

Unfortunately, there is a bug in Ranorex 6.0 that shows the instrumentation warning for Ranorex Studio itself.

As a workaround, you could disable the WPF plug-in for the Ranorex Studio process.
Please open the WPF plugin settings and add 'RanorexStudio' to the list of disabled processes.

WPF_settings.png

add_process_name.png

Alternatively, you could start Ranorex Studio explicitly as administrator.

Currently, we do not know when this issue will be fixed. This depends on various factors. Nevertheless, all reported bugs and feature requests are documented in the release notes, with every new version release of Ranorex.

I hope this information will help you.

Sincerely,
Johannes

[haniball]

I have this problem on execution. Could you explain how to solve this issue on the target machine that just executes the tests please?

[Support Team]

Hello haniball,

In order to analyze the issue, we would need more detailed information. Please upload the compressed Ranorex Report of the failed test execution and a Ranorex Snapshot of the application under test.

Thank you in advance.

Sincerely,
Johannes