FAQ: What is the procedure to restore the default logging level of the Software Platform components?

The logging level of Software Platform components can be changed using the Diagnosis Viewer Tool that can be found in Tools section.

In detail, in Diagnosis Viewer Settings menu in Client configuration it is shown a list of the current running COPA-DATA processes (Software Platform components) - these processes are also known as COPA-DATA logging clients. Only processes currently active are shown in the list and logging level can be changed. The list of the processes also includes the information about the computer name (FQDN) and the local TCP port used by the process to connect and generate log-messages to the zenLogSrv (zenon Logging Service), by default, listening on the TCP 50870 port.

​

When double-clicking on a process, a List of (logging) parameters will be displayed for that process only. To revert to default logging values, select the option "Default values" and "Message level for all modules" in this exact sequence. After click Accept and OK buttons.

You can confirm the changes were applied when opening again the List of parameters of the same process. In this case, only Message Level = Errors should be shown in all Modules listed of that process. This is the default logging level of the Software Platform component: only errors are shown to all modules of a process.

To revert the logging parameters to default of zenon Logging Service (zenLogSrv) - acts as logging server and client simultaneously - it should be used the option Server configuration in Settings menu. In this dialog, click on "Default values", Accept and OK buttons in this exact sequence. Reopen the same dialog to confirm the changes: only Message Level = Errors should be shown in all Modules listed and LOG-parameters values are revert to default (right-side of the dialog below).

It is very unlikely to be needed to change the zenon logging Service configuration while troubleshooting a process or the system as, most frequently, only the logging level of Software Platform components is sufficient.

1. Alternative method using zenon Configuration file

Alternatively, it is possible to amend the logging level of COPA-DATA processes directly in zenon6.ini file (zenon Configuration file) of the target computer (path: %CD_SYSTEM%). In this case, navigate in this file to the respective logging section of the process(es) you wish to modify the logging level (revert to default). The respective logging section of a process can be easily identified by the [process name + _project name_driver identification (if applicable, e.g. zenon driver)] and when the next line includes the parameter LOGMaxBufferedRecs=...

As soon you identify the respective section, you can delete it completely until the next section is started. You can repeat the same proceedure to all COPA-DATA processes that you wish to revert to default logging settings. Doing this changes in zenon6.ini allows to apply the changes to multiple processes faster.

To revert the zenLogSrv logging parameters to default via zenon6.ini, you can look for the respective section in zenon6.ini file too: [LOGGING_SYSTEM]. Deleting this section completely will revert the zenLogSrv settings to default.

Backup first zenon6.ini file before doing any changes to the system.

As final note, changes in the logging level of COPA-DATA processes are only applied once the respective process has been restated.

If you have any question, doubt or suggestion about this FAQ please contact your local COPA-DATA Representative.

• Related Articles

• Checklist: Step-by-Step guide - How to create a remote logging

  Time estimate: 10 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. For the purpose of this ...

• Checklist: Software-dongle is broken

  Time estimate: 15 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] ...

• FAQ: CD_SVA_2022_1: Vulnerability in zenon Software platform

  Summary  COPA-DATA received a report from Security Researcher Ruben Santamarta detailing a security vulnerability for the zenon Logging Service which is part of the zenon platform standard deployment. Based on this vulnerability additional ...

• FAQ: After which hardware changes I must expect to have to renew the software license?

  The Algorithms used to calculate the license key are based on the Technology from Wibukey, various hardware and software components are considered. Which ones in detail is explicit Wibukey knowledge and not public information. In other words after a ...

• FAQ: Soft Dongle breaks upon virtual machine snapshot restore in CodeMeter Version 7.10 or higher. This results in a loss of license.

  This only affects licenses activated on soft dongles (aka: CmAct licenses). CodeMeter in version 7.10 detects if a snapshot to the machine was applied and invalidates the soft dongle. This results in invalid or not found licenses.  The solution is to ...