Kepware OPC UA tags going bad automatically. Turns good after reinitializing

[SV_10197221]

Hi,

I have two Kepware Servers(lets say Kep-1 and Kep-2) connected to common edge, with modbus and OPC UA tags. The devices addresses and connection are exactly same in both the Kepservers(Kep-1 and Kep-2).

There are around 300 energy meter OPC UA tags that are connected to FactoryTalkLinxGatewayOPCUA Server in each of these Kepservers. 

We are facing a scenario, where all of a sudden some of the tag's quality in the second kepserver Kep-2 becomes bad even though the quality of the same tags are good in the Kep-1. After we reinitialize the Kep-2 all the tags quality become good again.

We stopped the kepware service at Kep-1 for some days for testing purpose, and didn't face any problem in Kep-2. But once we start the Kep-1 service again, the issue occurs unexpectedly again after few hours or few days in Kep-2.

What is the cause of this issue?

Best Regards,

Thanks

[rjanardan]

1. Do you see any error in Kep-2 event logs when this occurs?
2. Could the OPC UA server be having performance issues processing so many read requests?
3. Probably you could get a clue from OPC UA diagnostic logs
   1. Change persistence mode of OPC diagnostics to Extended Data Storage(Kepware Administration -> Settings -> Event Log -> OPC Diagnostics log settings)
   2. Enable OPC UA diagnostics(Project Properties > OPC UA > Log Diagnostics = Yes)
4. Could this be an intermittent network issue? What do you see in a wireshark capture from the machine running Kep2?
   1. In Wireshark Click Edit->Preferences->Protocols->OpcUa and add your port
   2. Now you could even add a filter as opcua to just see opcua traffic in the capture