[MSI Interface] Exception Queue is not saved
Description
If a separate data folder was used, the Message Exception Queue was not saved and was not available after a restart.
The issue has been addressed and the Message Exception Queue will be saved now also, if a separate data folder is used. This is possible via the new properties Service Engine folder and Data folder.
To benefit from this fix:
- Update your zenon Software Platform to the latest build of zenon 12 or higher and update the MSI Interface AddIn in your project.
Item ID: 298175
Version: 14.00 Build: 393950
Version: 12.00 Build: 397336
Related Articles
MSI Interface: Extending Exception Messages
The graphical user interface of the configuration dialog for the configuration of exception messages has been revised. The Exception Message Configuration dialog can now be opened directly when selecting the Exception Message tab. The dialog is ...
Checklist: SAP Interface does not work
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 ...
[MSI Interface] Sending an Exception Message freezes the Service Engine
Description If an exception message is triggered in the Werum MSI Interface for which an identifier is defined, the Service Engine can freeze. Identifiers enable the correct assignment of the exception message to the linked property. This error has ...
[MSI Interface]Too many Exception Messages are sent
Description If the “Alarm acknowledged” option was used for alarm-based exception messages, a message was sent incorrectly when the alarm occurred. The issue has been addressed and wrong shipments are no longer executed. To benefit from this fix: ...
[MSI Interface] Sending a Exception Message leads to XML deserialize Error
Description Configured exception messages are not sent in the Werum MSI Interface. This was caused by an XML deserialization error. This error has been fixed. Exception messages are sent again. To benefit from this fix: Update your zenon Software ...