Method invocation for method GetChildren to URI O=184|T=1|B=127D838|P=510C at endpoint HWND:00070C34 was not handled

Please suggest the solution for below issue.

Method invocation for method GetChildren to URI O=184|T=1|B=127D838|P=510C at endpoint HWND:00070C34 was not handled
Pega.Remoting.InvokeNotHandledException: Method invocation for method GetChildren to URI O=184|T=1|B=127D838|P=510C at endpoint HWND:00070C34 was not handled

Server stack trace:

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 OpenSpan.Virtual.Interfaces.IVirtualTreeView.GetChildren(ObjectUri& o, TreeNodeId& nodeId)
at OpenSpan.Adapters.Virtual.VirtualTargets.VirtualTreeView.RefreshNodes()
at OpenSpan.Adapters.Virtual.VirtualTargets.VirtualTreeView.SubscribeToEvents()
at OpenSpan.Adapters.Virtual.VirtualControlContainerHelper.CreateTarget(IpcUri uri, IpcUri parentUri, Type controlType, String interfaceTypeName, Boolean queueing)
at OpenSpan.Adapters.Virtual.VirtualControlContainerHelper.CreateTarget(IpcUri uri, IpcUri parentUri, String targetTypeName, String interfaceTypeName, String nativeType, String nativeVersion, Boolean queueing)
at OpenSpan.Adapters.Virtual.VirtualControlContainerHelper.ProcessMessage(Object customMessageData, Boolean queueing, Nullable`1 container, IdleChange& change)
at OpenSpan.Adapters.Virtual.VirtualControlContainerHelper.ParseMessage(Message& message, Boolean queueing, IdleChange& change)
at OpenSpan.Adapters.Windows.WindowsProcess.OnCustomMessageReceived(Message& m)
at OpenSpan.Adapters.Windows.WindowsProcess.WndProc(Message& m)


Context: facing issue when launching windows adapter from Pega runtime, but not from Pega studio. We never faced this issue in 19.1 version of Pega robotics. After updating to 22.1.39, we started to face this issue.

@AshKS Is this error appearing in a message, or is it simply appearing in the logs? If the latter, is there any other symptom that you notice (i.e. your automation is not working, or you are getting a timeout or some other issue)? In your log, is the thread this error is appearing om the same one as your automation, or is it the thread from your application? You can see the Thread ID in the third column in the Runtime logs.

@ThomasSasnett This message is from runtime logs. It is coming from application(windows adapter). I guess this is coming from from Factory files that adapter creates by itself. Like in my case (ActiveXFactory, WinInetFactory, JavaTargetFactory.)

@AshKS If there are no other symptoms, it is likely benign and can be ignored. It is likely that this is just a new log message that would help diagnose other issues.

@ThomasSasnett this shows as message too in the launch of application.Adapter crashes after clicking on yes button.

@AshKS If the message is showing and not simply being logged or is causing a noticeable effect (like a crash in this case), then it needs to be investigated. This would be best served by raising a support incident from https://msp.pega.com, as we will likely need access to your machine see how things are setup and working. If you do raise a support incident, please post the INC number here.

In touch with Pega support team

There was pega robotics translator.dll issue in Pega version-22.1.39 which fixed in later version. After upgrading to 22.1.49, issue is fixed.