[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 Platform to the latest build of zenon 11 or
higher.
Item ID: 269871
Version: 12.00 Build: 180966
Version: 11.00 Build: 176384
Related Articles
[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 ...
zenon Changesets Excel
Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...
zenon Changesets CSV
Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ...
[MSI Interface] Deleting an Alarm Event Group prevents sending of Exception Messages
Summary In the Werum MSI Interface, deleting an alarm/event group leads to an error under certain conditions. This has been fixed. Description In the MSI configuration an alarm/event group is used to define an exception message. Later, a group is ...
[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: ...