Checklist: Client/Standby cannot establish a reliable connection with Service Engine Server

Checklist: Client/Standby cannot establish a reliable connection with Service Engine Server

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] (point refers specific module/product) Point description.
Terminology:
zenon network = All Service Engine computers in the network
Primary Server = Process Leading Service Engine computer
Client(s) = Standby + Client Service Engine computer(s)
  1. Screenshot and followed instructions of error/warning messages shown.
  2. Only zenon network is affected so that there is no reliable communication between Primary Server and all/some clients.
  3. Service Engine clients show blue-dots in the top right corner of screen elements (status N_UPDATE=1).
  4. Service Engine of computers in zenon network have the same main and build versions. Note that client computers must have the same or higher version of the Service Engine running in the server computer.
  5. Project Service Engine files in the target computers have been generated from the same project GUID and the Service Engine has been started from the correct start project Service Engine folder.
  6. zenon Drivers still communicate with field devices so that there are no red-dots shown in the top right corner of screen elements in the Primary Server (status INVALID=1).
  7. Network Service process (zenNetSrv.exe) is running with identical configuration (default: TCP Port = 1100 and IPv4) in all computers in zenon network.
    8. Network Service settings can be consulted or amended in  'zenon Startup Tool > Application > Listening ports >Services: Network Service'.
    All computers must have the same password when using encrypted network communication.
    You can insert the password in zenon Startup Tool > Application > Network configuration.
  8. Server names in Project > Network settings use computers hostname or FQDN (Fully Qualified Domain Name).
    9. Do not insert a computer IP address, localhost or 127.0.0.1 as server name.
  9. Network name resolution works between all computers in zenon network.
    10. Ping commands between Server and Clients are successful in both directions using computers hostname/FQDN.
    1. In domain networks, when executing the command 'ping -a [IP address] or [Hostname]' to query the pair and the local server, the reply includes the FQDN or the Hostname in all responses. The reply with FQDN or Hostname to ping commands must be consistent in both servers, so that it is used only FQDN or Hostnames.
      2. For example,
      In Server1 executing the command: ping -a IP_Server1
      In Server1 executing the command: ping -a IP_Server2

      In Server2 executing the command: ping -a IP_Server1
      In Server2 executing the command: ping -a IP_Server2


      In both zenon servers, the resolved name of the ping command always return the FQDN (as shown in the next figure) or the Hostname of the local and the pair Server. If not, as a quick fix, enter the IP address and the FQDN (or Hostname, depending on the case) of the pair server in Windows Hosts file so that all the resolved name use FQDN or Hostnames only.
  10. Primary Server and Client(s) network connection is established.
    11. You can use Windows Resource Monitor to know more details about running processes.
    In the Primary Server (and clients), open Windows Resource Monitor >  Network tab and select zenNetSrv.exe process.
    The TCP Connections window should give you a clear picture about the connections established between Primary Server and Client computers.
    The Listening Ports output should match the configuration of the Network Service in zenon Startup Tool and be identical in all computers in zenon network.
    Alternatively, you can execute the command in Command Prompt (run as administrator) ‘netstat -a -b | findstr :1100’.
  11. Searched and followed error instructions in LOGs related with Network Service (zenNetSrv.exe) in Primary Server and in Clients with communication problems.
    12. All zenon components write in the background messages to joint log file(s) saved in '%programdata%\COPA-DATA\LOG' folder.
    These files can be read and configured with Diagnosis Viewer.

    You can modify the logging level of a component by clicking 'Client Configuration' in 'Settings' menu and after select the respective process name.
    Attention:  Set the logging parameters wisely as the time-frame of the LOGs decrease when increasing the detail of the logs written.

    You can also find LOG files in SIC in 'Platform > Versions > Version XXXX > Directories > LogDirectory' folder.
  12. Time synchronization is configured and working.
    1. All devices in the system use the same time source (external or zenon).
    2. Time difference between computers is shorter than five seconds.
    By default, zenon Time Synchronization is enabled in all computers in zenon network.
    zenon Time Synchronization can be disabled w hen using an external time source.
    For this, in [NETZ] section in zenon configuration file (zenon6.ini) (path: %CD_SYSTEM) add the line 'TIMESYNCH=0' .
    The same configuration must be applied to all zenon computers in the network.
  13. [Event Viewer] Operating System event-logs do not report any problem related with hardware, network or time synchronization at the time of the problem.
  14. [zenon Startup Tool -> Applications -> Network configuration] Increased zenon ‘Network Timeout’ if the number of files to synchronize between Primary and Standby servers is large.
    15. It will take longer the standby to recognize a server failure and upgrade himself to primary. It is also required more memory in the standby to buffer data.
  15. Searched in Knowledge Base if a previous issue has been addressed.

If the problem persists after completing this checklist and followed corrective actions, please contact your local COPA-DATA Representative providing a SIC-Reduced Report from the target computer(s) and the result of this checklist – please include any additional information or comments related with the points addressed you find relevant.

System Information Collector is a standalone COPA-DATA application that collects relevant data about the Operating System and zenon Software Platform for troubleshooting purposes. SIC is installed with zenon and can be started from zenon Startup Tool (Tools).