Service engine crashes when removing columns in AML or CEL
Description
If in the Service Engine
in the AML or CEL screen columns are removed from the list while
the filter row is active, the Service Engine is
closed unexpectedly.
This bug has been fixed. Columns can be removed from AML
and CEL again as expected.
To benefit from this
fix:
- Update your zenon Software Platform to the latest build of zenon 14
or higher.
Item ID: 281749
Version: 14.00 Build: 237866
Version: 14.00 Build: 239777
Related Articles
FAQ: How can I backup the Service Engine data, the data created during Service Engine?
The path of the Service Engine folder can be amended in the project properties and it is set into zenon6.ini (VBF30=) when the start project is set in Engineering Studio or in zenon Startup Tool. In the Service Engine folder, there is the subfolder ...
Checklist: Data Missing in Service Engine
Time estimate: 60 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] ...
Sporadic crashes and freezes of service engine displaying AML or CEL list when AD users are used
Summary Service Engine sporadically crashes or freezes acknowledging alarms in AML list when AD users are used Description Service Engine sporadically crashes or freezes acknowledging alarms in AML list when AD users are used Issue Number: 246421 ...
FAQ: How, where, why and when does zenon Service Engine save data?
zenon Disk Space Handling: The zenon Service Engine, by default, stores process data on the hard disk. This is true for a standalone zenon project, as well as the zenon Service Engine server(s) in the zenon network topology. This data consists of ...
FAQ: Delayed variable updates on Terminal Server Service Engine Clients occur in some scenarios.
In some cases, Service Engine Clients on a Terminal Server might have delayed variable updates. Depending on the system those delays can be about 2 seconds. A reason for this can be a hostname resolution procedure, which is needed to determine ...