Replies: 1 comment
-
This probably means the Subscription has timed out on the Server side for some reason. It's usually sent when either a PublishRequest is received but there is no Subscription. Do your MonitoredItems stop updating after receiving this? Are you able to get a Wireshark capture of traffic leading up to one of these ServiceFaults? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
ServiceFault(responseHeader=ResponseHeader(timestamp=DateTime{utcTime=133989367892190000, javaDate=Wed Aug 06 14:53:09 CST 2025}, requestHandle=33925, serviceResult=StatusCode{name=Bad_NoSubscription, value=0x80790000, quality=bad}, serviceDiagnostics=null, stringTable=null, additionalHeader=ExtensionObject{encoded=ByteString{bytes=null}, encodingId=NodeId{ns=0, id=0}})
I need to collect 100000 points, I collect them through subscription. When I keep reporting this exception, how should I handle it
Beta Was this translation helpful? Give feedback.
All reactions