OPCUA32: driver crashes on driver start command under specific circumstances

• Related Articles

• OPCUA32: driver crashes on driver start command under specific circumstances

  Description When stopping and starting the OPCUA32 driver via driver command functions, the driver is closed unexpectedly if the commands are executed in a fast time sequence. This behavior has been fixed.  To take advantage of this fix: Upgrade to ...

• OPCUA32: driver crashes on driver start command under specific circumstances

  Description When stopping and starting the OPCUA32 driver via driver command functions, the driver is closed unexpectedly if the commands are executed in a fast time sequence. This behavior has been fixed. To take advantage of this fix: Update to the ...

• Checklist: Engineering Studio cannot start or closes unexpectedly

  Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• 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 ...

• AddIn does not start

  Check the Logs in DiagViewer. If it shows an ERROR in the GENERAL module which shows the exception: Scada.Internal.DotNetAddInExtension.AddInIntegration.Startup Cannot startup Add-In .NET Extension for instance id 'e1d3....'. Exception ...