AccessOPCUA: process gateway does not start on a specific system with an error that the hostname cannot be resolved
AccessOPCUA: process gateway does not start on a specific system with an error that the hostname cannot be resolved
Description
The OPCUA Process Gateway fails to start in a specific configuration where a DNS suffix is used and the resolving the hostname with the DNS suffix results in an error.
The issue has been addressed and the communication is now initialized as expected.
To benefit from this fix:
Update your zenon Software Platform to the latest build of zenon 10 or higher.
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] ...
Time estimate: 45 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] ...
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] ...
This issue may occur due to missing digital certificates on the system where the error appears. Microsoft Windows implements a mechanism that automatically downloads, over the internet, trusted root certificate authorities, which are not installed ...
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 ...