Closing the Service Engine Client causes crashes and generates dump files on a specific Workspace/Project that utilize a custom AddIn
Description
Under certain timing conditions Service Engine can
crash during shutdown if a customer specific Add-In has accessed AlarmMessageList
object in zenon API.
This behavior has been modified. The Service Engine
will no longer crash under these conditions.
To benefit from this fix:
- Update your zenon Software Platform to the latest build of zenon 11 or
higher.
Item ID: 273129
Version: 12.00 Build: 206562
Version: 11.00 Build: 193390
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] ...
Checklist: Workspace/Project cannot be created, loaded or backed up
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] ...
FAQ: When I start my zenon project on a Service Engine client, my AUTOSTART script is not executed. What is the problem?
A "script" in zenon is not a snippet of code as you may think in the traditional sense, but rather a configured collection of zenon functions, executed in order. A common use of a zenon script is to load several screens at project startup, for ...
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] ...