Exception while identifying ComponentOne WPF controls

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
kissKurisu
Posts: 7
Joined: Wed Oct 18, 2017 8:51 am

Exception while identifying ComponentOne WPF controls

Post by kissKurisu » Wed Oct 18, 2017 9:20 am

Hi,
Our application uses the ComponentOne WPF controls.When we idendify buttons or other controls(new solution), a popup message says that
"Failed to instrument WPF process. UI element identification capabilities for this window are limited.
Exception while initializing WPF proxy: System.Runtime.Remoting.RemotingException: Failed to write to an IPC Port: The pipe is being closed."

i am wondering that whether its the problem of the 3rd part control or not.

OS:Win10
Ranorex version:7.2

Thanks.

Code: Select all

Failed to instrument WPF process. UI element identification capabilities for this window are limited.

Exception while initializing WPF proxy: System.Runtime.Remoting.RemotingException: Failed to write to an IPC Port: The pipe is being closed.

Server stack trace: 
   at System.Runtime.Remoting.Channels.Ipc.IpcPort.Write(Byte[] data, Int32 offset, Int32 size)
   at System.Runtime.Remoting.Channels.Ipc.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at System.Runtime.Remoting.Channels.ChunkedMemoryStream.WriteTo(Stream stream)
   at System.Runtime.Remoting.Channels.Ipc.IpcClientHandler.SendRequest(IMessage msg, ITransportHeaders headers, Stream contentStream)
   at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Ranorex.Core.Injection.IDotNetThingy.GetAppDomainIds()
   at Ranorex.Plugin.WpfFlavor.InjectWpfAutomation(ProcessInfo proc, IDotNetThingy dnproxy)
20171018154020.png
20171018154020.png (4.28 KiB) Viewed 1030 times

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Exception while identifying ComponentOne WPF controls

Post by Support Team » Thu Oct 19, 2017 1:01 pm

Hello kissKurisu,

Thank you for posting your issue.

In order to analyze this issue a Ranorex Snapshot of the application under test would be very useful. Could you post the Ranorex Snapsot with your next reply?

Detailed instructions on how to create a Ranorex Snapshot can be found in our user guide under the following link: How to Create a Ranorex Snapshot

I am looking forward to your reply.

Sincerely,
Tomaž
.
Image

kissKurisu
Posts: 7
Joined: Wed Oct 18, 2017 8:51 am

Re: Exception while identifying ComponentOne WPF controls

Post by kissKurisu » Fri Oct 20, 2017 4:31 am

Hi,

Here is the Snapshot file,hope it will help.

Thanks.
Attachments
C1FlexGrid.rxsnp
(38.41 KiB) Downloaded 24 times
applicationsnapshot.rxsnp
autsnapshot
(34.18 KiB) Downloaded 25 times

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Exception while identifying ComponentOne WPF controls

Post by Support Team » Fri Oct 20, 2017 8:29 am

Hello kissKurisu,

Thank you for the snapshots.
This issue could be connected to a bug in Ranorex. We would prefer to handle this issue via a support ticket. Please do send us a support email to [email protected]. We would then be able to analyze this issue in more detail.

Please also send your customer ID and mention this forum post in the email.

We are looking forward to your email.

Regards,
Tomaž
.
Image