Please use the Contact Form (www.opclabs.com/company/contact/form/3-contact-form ) and send us your serial number, or date of purchase, or licensee name, and/or other information that would allow us to identify the original license.

Note that version 5.40 is for .NET Framework 4.5.2 or later - I hope you can switch to that?

Regards

One would need at least several pages to explain the complexities related to this issue. So instead of explaining all of them, I will try to provide some actionable hints.

1) Version 5.35 (and earlier version) are kind of over-sensitive to the "publishing has stopped" issue. There is a kind of keep-alive mechanism built into OPC UA, and when an expected response does not come from the server in time, the client should detect it and react. We have made it more forgiving in version 5.40, and that is a recommended approach: upgrade to 5.40. If you have license for 5.3x and are not covered by a maintenance, we will give you a license free of charge for version 5.40.

2) It might be possible to improve the situation while staying with version 5.35 by tweaking various parameters, but it's not the recommended approach. With regard to RetrialDelay, there are actually *four* such parameters, depending on the level or "scope" of the problem: on the global ("engine") level, session level, subscription level, and monitored item level. They are placed in different objects, and their default values differ. When the "publishing has stopped" issue is detected, it affects the subscription level, so that's where the changes need to be made.

Best regards

As parts of the answer depend on the version and build you are using, please provide first the version and build you have (right-click on one of the OpcLabs.* assemblies, and take the version and build from the Details tab).

Thank you