The OPCUA32 client driver may close unexpectedly under specific circumstances when CreateMonitoredItem fails due to an invalid persistent NodeId.

• Related Articles

• The OPCUA client driver may cause the runtime to stop responding under specific circumstances

  Summary The OPCUA client driver uses the due time for publish responses (keepalive) to check if the OPCUA server is still responding. Normally if the connection to the OPCUA server is lost, the connection is closed at the TCP level. If however no ...

• The OPCUA process gateway may close unexpectedly under specific circumstances when reloading the runtime

  Summary With an OPCUA process gateway with a larger number of variables cofigured and an OPCUA client connected to the OPCUA server having one or more subscriptions, the OPCUA server may close unexpectedly under specific timing conditions if the ...

• The OPCUA server process gateway may close unexpectedly with an unhandled exception when configuring the namespace index

  Summary When entering a value "0" for the namespace index in the OPCUA process gateway configuration, an error message is displayed noting that this namespace index is reserved for OPCUA itself. When the message is acknowledged using the enter key on ...

• The OPCUA client driver should increase the grace period to establish if a server is no longer responding

  Summary If under specific circumstances an OPCUA server is not capable of sending a publish response with a keep alive message in time the OPCUA client may assume that the OPCUA server is no longer available. A grace period is applied of 1000ms. ...

• The zenon OPC UA server in the process gateway may close unexpectedly with a specific configuration when browsed by an OPC UA client in a particular manner

  Summary The zenon OPC UA server in the process gateway may close unexpectedly with an unhandled exception when a specific zenon project is used and an OPC UA client browses the OPC UA server address space in a particular manner. One situation where ...