Hi Dojo,
I occasionally bump into this kind of system notice where an exception is triggered,
with the following stack trace: any hint, please?
Thanks
(I've changed the actual server name into DMA01 before sharing this)
* Notice Alarm: 'DataMiner run-time' is 'Unexpected Exception [Exception from HRESULT: 0x8004028A]: The client is unknown.
(Element Subscription)
Server stack trace:
at Interop.SLDataMiner.IDataMiner.NotifyDataMiner(String bstrUser, Int32 iType, Object varValue, Object varValue2, Object& pvarReturnValue)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.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 Interop.SLDataMiner.IDataMiner.NotifyDataMiner(String bstrUser, Int32 iType, Object varValue, Object varValue2, Object& pvarReturnValue)
at Skyline.DataMiner.Net.DataMiner.SubscribeOnSLDataMinerElementInner(SubscribeInfo info))' on 'DMA01'.
This is apparently an error that's been around for a while. It tends to happen when a DM is starting up (not sure if that's your experience) and an old element subscription is tried rather than initiating a new one.
Harmless apparently but it would be nice to see it handled more gracefully so we can avoid further questions or concerns about it.
I see, thanks for the explanation Simon
I’ll submit a feature suggestion so that it can be handled differently.