Skip to content
Ask A Question
  • There are no suggestions because the search field is empty.

OPC Router Redundancy not working as expected in versions 5.1 & 5.2 (Resolved)

I am running version (5.1 or 5.2) and my secondary OPC Router is not taking over when the primary instance goes down. How can I resolve this issue to prevent production downtime?

Due to an adjustment in Microsoft .NET 8, the redundancy functionality of the OPC Router is not working as expected in versions 5.1 & 5.2. Consequently, the secondary OPC Router fails to take over when it should, potentially leading to production downtime.

There are two viable solutions to resolve this problem. Please note that one of these solutions must be applied to both the primary and secondary OPC Router instances as well as a application restart is required:

1. Install a Maintenance Release


Install the maintenance release that is now available on both OPC Router instances. You can obtain the updates via the following links:

2. Edit a Configuration File

If your company requires vetting and testing of all new software downloads or updates, you can resolve this issue by editing a configuration file in the installation directory on both the primary and secondary instances.

Edit the file inray.OPCRouter.Service.runtimeconfig.json in the installation directory of both OPC Router instances (primary and secondary) and make sure that this parameter is set to true:

[...]
“runtimeOptions”: {
    [...]
    “configProperties”: {
        “System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization”: true
Then restart the OPC Router service.
 

To avoid production downtime, we strongly recommend that you implement one of the two solutions immediately. Should you require assistance or have any questions, please do not hesitate to contact our support team!