Ranorex technology limitation Technology WPF

Ask general questions here.
[email protected]
Posts: 3
Joined: Fri Mar 22, 2019 5:57 am

Ranorex technology limitation Technology WPF

Post by [email protected] » Mon Mar 25, 2019 11:09 am


I am getting below warning.
Failed to instrument WPF process. UI element identification capabilities for this window are limited.

Exception while setting-up managed injection endpoint: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Proxies.RemotingProxy.CallProcessMessage(IMessageSink ms, IMessage reqMsg, ArrayWithSize proxySinks, Thread currentThread, Context currentContext, Boolean bSkippingContextChain)
at System.Runtime.Remoting.Proxies.RemotingProxy.InternalInvoke(IMethodCallMessage reqMcmMsg, Boolean useDispatchMessage, Int32 callType)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(IMessage reqMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Ranorex.Core.IpcRemotingService.IPingable.Ping()
at Ranorex.Core.Injection.DotNetThingy.GetInstance(Int32 pid)
at Ranorex.Core.Injection.DotNetThingy.TryGetInstance(Int32 pid, Int32 tryCount)
at Ranorex.Core.Injection.Injector.InjectManagedEndpoint(IntPtr targetWindow, HackSelection activeHacks)
at Ranorex.Plugin.LocalCommonControls.Ranorex.Plugin.ICommonControls.InjectManagedEndpoint(IntPtr targetWindow, HackSelection activeHacks)
at Ranorex.Plugin.WpfFlavor.InjectWpf(IntPtr hwnd, Int32 pid)

What is solution for this. Pl help


User avatar
Ranorex Guru
Ranorex Guru
Posts: 6553
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Ranorex technology limitation Technology WPF

Post by odklizec » Mon Mar 25, 2019 1:40 pm


Unfortunately, there is too little information about the AUT, used Ranorex version and overall test suite setup.
Please answer below questions...
Ranorex version? From your previous post, I remmeber you are using 8.1.something? But this is too old an no longer supported version. Have you tied to reproduce the problem with most recent 8.3.3 or 9.0?
Have you examined Ranorex instrumentation process troubleshoting guide?
https://www.ranorex.com/help/latest/int ... eshooting/
Have you tried to run Ranorex as administrator? This often helps with similar problems.
Could you please upload a Ranorex snapshot (NOT screenshot) of the problematic element/dialog?
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration