stack is overwritten when executing function to set alarm group/class active

stack is overwritten when executing function to set alarm group/class active

Description

In specific situations a buffer overrun could occur on the stack in connection with actions in the screen of type AML.  
This had no effect on the functionality of the Service Engine and was not noticed by the user.

With zenon Software Platform Version 12 these buffer overruns no longer occur.


Item ID: 264600
Version: 11.00 Build: 157700
Version: 10.00 Build: 144352

    • Related Articles

    • 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 ...

    • Send Message function does not send messages when triggered by limit without alarm class/group/area

      Summary If a Send Message function is triggered by a limit violation which has no alarm group/class/area linked to it, the Send Message function is suppressed if another alarm group/class/area is suppressed. Description If a Send Message function is ...

    • [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 ...

    • zenon Service Engine freezes when process recorder is active

      Description The zenon Service Engine froze when the Process Recorder was active. The Service Engine froze because a Microsoft function runs in an endless loop. The issue has been addressed and an optimization call, which led to the issue, has been ...