Do I understand it right that it appears to be a problem/problems in older Kepware servers, and there is no need to further investigate on our side?

Thank you

Actually, after thinking it over, you proposal might be better, especially if in order to reproduce the issue a specific target OPC server (to which the Kepware server is connected) is needed.

If you simply follow the steps that you described in the beginning of this forum topic, then it *might* be enough just to capture the Wireshark log and send it to us. The enhanced logging etc. would be useful too, but it is possible that just Wireshark would be sufficent.

The instructions for all these troubleshooting procedures are here: kb.opclabs.com/Collecting_information_for_troubleshooting .

Regards

I have hoped they would actually analyze the problem, and not just reject it outright.

In that case I would rather first try to reproduce it myself here and analyze. Can you send me you Kepware configuration, and/or any other file needed to set it up?

Regards

Actually, the word "crash" isn't used in this sense. That's why I asked about it, because I suspected that you are not describing the observed behavior well, and I needed to understand the nature of the problem. "Crash" is normally used for situations when the application unexpectedly terminates.

We test with KEPServerEx from time to time. But normally not with specific drivers (just the simulation), and we have not tested with the OPC UA driver.

I still suggest that you first contact Kepware about this, because it is far more likely the issue is on their side. The fact that other clients work does not have much significance, because different clients do different things.

Can you also please elaborate on what you have meant by "subscribe go in bad ". What specific message are you receiving?

I am absolutely willing to help you out and resolve issues that are on our side, but you need to give me the information I need. Without that, it cannot be done.

Can you please describe the symptoms of your problem in detail. I have already asked you twice what do you mean by "crash". I received no answer. You can take screenshots and post them here, if words are not enough.

Regards

I need to understand first what you are reporting. Only then can I decide about the proper way to handle it.

What do you mean by "crash"? A specific error box/message from the app? If so, please provide details (minimum: what is the error text).