There have been numerous OPC UA fixes since that old and buggy and officially unsupported version was released. Yes, you may have to pay to upgrade, but you probably will not get a satisfactory solution to any problems with v8.0.x.
So the problem most probably would be at the old server? Not the new client connecting to hundreds of OPC-UA servers and reading data? That gives me a gasp of air because I was afraid the 8.1.45 is the problem where suddenly some TagGroups start to fail.
Consider the possibility that the new client is using modern features/methods that the old server doesn't handle properly. Or the new workload just pushed it over the edge.
OK, but the client where the tag group fails for this OPC-UA connection tags is on the 8.1.45 machine that is an OPC-UA client for the 8.0.17
I'm a bit confused:
Does Tag Groups propagate to the server via OPC-UA?
I have a few identical tag Groups from where one fails, but if I change to other group it works instantly.
On Ignition 8.1.45, tags fail for tags from a single OPC-UA connection where they transition from Uncertain_InitialValue to Bad_Failure only when assigned to specific Tag Group that works for all other 70000+ tags from other 250+ OPC-UA conncections
The same tags immediately begin working when assigned to any other Tag Group, including a newly created one with identical settings.
Even Newly randomly added tags to the tag browser from this OPC-UA connection behave the same.
The OPC-UA connection has been recreated, connection specific certificate was deleted and reTrusted during reconnect, and both gateways restarted without changing the behavior.
This connection and the tags from it was working for at least two years and no version updates were made on the client since 8.1.45 was released.
Using this 8.1.45 gateway I have more than 300+ OPC-UA connections to all over the county and another 8.1.45 gateway with another 250+ connections working. (split in two to ease the load, and separate FrontEnd gateway, Distinct database, ...)
I even have connections to version 7 that works fine. or other old SCADA softwares, but most of the OPC-UA connections are directly to PLC's, most of them newer.
All others except this one work fine in this sense or at lest until now.
I strongly hope the problem is isolated to this single connection.
Sorry if maybe I should have opened a new dedicated thead to this if it does not meet this topic.
You're going to have to open a support ticket, this isn't likely to get diagnosed in the forum because it's going to need logs, troubleshooting, possibly wireshark captures, etc.
OK, thanks for the advice,
Based on what was mentioned, can we estimate where the problem seems to lie?
On the 8.1.45 client ? or the old obsolete 7.0.17 server ? Or it's too weird.