October 2025
- Last UpdatedOct 08, 2025
- 2 minute read
Application Server 2023 R2 SP1 Patch 03 includes the resolved issues listed below.
|
Originating Issue |
Related Issues |
Case/SR Number |
Description |
|
3333465 |
3946841 |
960410523 960605244 |
In a System Platform 2023 multi-galaxy environment, memory consumption of the active MxDataProvider in one primary galaxy GR node kept increasing. |
|
3844432 |
960551165 |
The IDE stopped responding when there were two IDEs (RDP sessions) open on the GR. |
|
|
3851390 |
960577482 |
When an instance was opened for the first time, it applied the selected default, even if it was not included. |
|
|
3907421 |
4105889 |
960592600 |
The graphic displayed in runtime looked different from the graphic displayed during configuration. |
|
3942065 |
960594920 |
AlarmShelving warnings appeared in the standby engine. |
|
|
3951200 |
960605256 |
Changes to a master template removed some I/O scaling information. |
|
|
3966348 |
960613637 |
InTouch WindowMaker sometimes took a lot of time to open, or stopped responding when trying to save a minor modification. |
|
|
3971383 |
960615527 |
Errors in the logger on validation of objects resulted in memory growth of the aaGR.exe process. |
|
|
3976719 |
960616756 |
When importing an aapkg file, the parent node was not included and was not added to the navigation tree. |
|
|
3983948 |
960540570 |
An object's hierarchal name was not resolved in runtime. |
|
|
3998140 |
960595699 |
Translating alarm messages took a very long time. |
|
|
4003650 |
960618360 |
Dependent DLLs were not imported into a custom client control. |
|
|
4026669 |
960578111 |
An AlarmAck request was not processed from the AlarmProvider because the LMX version of remote platform was not received. |
|
|
4029751 |
960608348 |
Deploying a managed InTouch application took too long. |
|
|
4064188 |
960636887 |
A state alarm was not triggered when the attribute was a Boolean and used buffered communication via the Telemetry Server. |
Resolved OMI issues for Patch 03 are separated into the following tables, one for OMI desktop issues and one for OMI web client issues. Some issues that have been fixed in this release may not be listed.
OMI desktop issues
|
Originating Issue |
Related Issues |
Case/SR Number |
Description |
|
3917272 |
960596611 |
After using the IDE for awhile (minutes to hours), Layouts and ViewApp templates would not open properly. |
|
|
3919650 |
960595907 |
The Layout Editor opened multiple windows with the same identity. |
|
|
3940646 |
4078295 4078285 3878000 |
960604042 |
The Embed function did not resolve in runtime and was shown as ###. Also, random blackouts occurred on the opening of runtime. |
|
3966657 |
960601835 |
An OMI application stopped responding when a List Box AddItem script called for 400 items. |
|
|
3990065 |
960601097 |
String attribute values containing '\r\n' characters caused the script execution to hang, resulting in the UI becoming unresponsive. |
|
|
4070109 |
960636729 |
The AVEVA OMI Application Manager GUI did not follow the regional time format. |
OMI web client issues
|
Originating Issue |
Related Issues |
Case/SR Number |
Description |
|
3924629 |
960598222 |
Using the Title Bar app in OMI, the Title Bar home button had a different color in the OMI web client compared to the deployed or Preview mode. |
|
|
3978121 |
3961562 |
960617279 |
Elements configured with gradients were rendered with solid colors despite functioning as expected in the OMI desktop application. |
|
3996762 |
960623839 |
The transparency property did not work on group elements. |
|
|
4042760 |
960625117 |
A custom property expression that was overridden in the template could not be compiled in runtime. |
|
|
4055729 |
960640441 |
Application became unresponsive or crashed after initially loading, and data stopped loading. |