January 2026
- Last UpdatedFeb 02, 2026
- 6 minute read
The GetNamedCredentials() scripting method was added to the scripting reference, and the information about severity 5 alarms was updated.
2023 R2 SP1 P04 is a patch release. It includes the following new features and enhancements and the resolved issues listed below.
New features and enhancements
The following feature enhancements were added to AVEVA OMI:
-
Bit State Animations
Bit State animations let you add conditions to an animation based on bit values. You can add multiple conditions and for each condition you can select individual bits in any pattern up to 32 bits.
-
Extended Truth Table Animations
The Blink, Disable, Value Display, and Visibility animations have now been extended with the ability to configure animations with truth table conditions.
-
OMI web client support for load balancing
The OMI web client now supports the use of a load balancer to improve system security and performance.
Resolved issues
AVEVA Application Server resolved issues:
|
Originating Issue |
Related Issues |
Case/SR Number |
Description |
|
IMS 4042665 |
960637756 |
The override value entered for an attribute under Settings was not shown in the Mapping window. |
|
|
IMS 4062344 |
IMS 4090783 |
960641142 |
OMI nodes experienced data acquisition issues when the GR node was not available, such as slow graphic and reference updates, and the application not responding. |
|
IMS 4066664 |
960645186 |
If the primary AppEngine was stopped, attribute data remained in the "Initializing" state. |
|
|
IMS 4073595 |
960619908 |
Instances that were created through Galaxy dump/load reverted to the template attribute values after any template change, if the parent template had an object wizard configured. |
|
|
IMS 4081194 |
960624009 |
When a template with an object wizard configured to set an attribute's EngUnits was modifed, the instances sometimes lost the EngUnit value after the template was checked in. |
|
|
IMS 4090654 |
960648867 |
After an object-owned graphic was updated updated by removing an embedded graphic that it contained, the Intouch App displayed a "Graphic Not Available" message when it was redeployed. |
|
|
IMS 4105563 |
960656721 |
An invalid connection status was returned from the redundant DI object if any communication driver had an uncertain status during deployment or engine start up. |
|
|
IMS 4110012 |
960618188 |
After forced failover, an object was offscan. |
|
|
IMS 4111218 |
960656407 |
After migrating a galaxy or objects from System Platform 2020 to System Platform 2023 R2 SP1, discrete message labels were missing. |
|
|
IMS 4215957 |
960623631 |
After importing a template with an object wizard from CSV, the .Hist.DescAttrName was replaced with me.ShortDesc. |
|
|
IMS 4230175 |
IMS 4321101 |
960666386 962621524 |
Within WindowMaker, graphics were shown as "invisible" |
|
IMS 4262563 |
962467486 |
Change the object association loose the attr. inout source |
|
|
IMS 4267886 |
960652605 |
Alarm translations not working in SP2023 R2 SP1 P01 |
|
|
IMS 4290709 |
962478338 |
AOT - I/O primitives of type BigString do not work when instantiated within a composition of virtual primitives |
|
|
IMS 4315268 |
962612923 |
Template imports were failing, and the tempdb database expanded to larger size than expected. |
|
|
IMS 4318000 |
IMS 3993707 |
960617962 |
A script did not execute after a forced failover.. |
|
IMS 4319322 |
962617233 |
Migration failed with the error "there is already an an object named 'deployed_objects' in the database. |
|
|
IMS 4325079 |
960641142 |
Remote Object Viewer Fails after GRNode (WAN) Disconnect |
|
|
IMS 4327477 |
960641142 |
Reference Caching - Resolving References were stuck for to long, especially after WAN disconnect. |
|
|
IMS 4327600 |
IMS 4372944 |
962612765 |
Errors and Warnings during a Galaxy Migration from 2017U3SP1 to 2023 R2 SP1. |
|
IMS 4329368 |
962620132 |
Execution of the internal_get_io_point_count stored procedure took a long time to complete. |
|
|
IMS 4331217 |
960641142 |
Platform manager took a long time to load after WAN disconnect |
|
|
IMS 4342614 |
962479274 |
aaPkg file import took hours. |
|
|
IMS 4346243 |
962619930 |
HistoricalTrendApp Y-axis limit values were displayed incorrectly , after translation |
|
|
IMS 4347128 |
962636518 |
Deploying an InTouch application took more than 30 minutes. |
|
|
IMS 4351819 |
962640911 |
There were unexpected AppEngine terminations. |
|
|
IMS 4354942 |
962620099 |
Security access was very slow. |
|
|
IMS 4361536 |
962646416 |
The IDE got disconnected from the GR on check-in of a template followed by validation. |
|
|
IMS 4368785 |
962650819 |
Slow IDE behaviour after installing HotFixes and unable to check-in objects. |
|
|
IMS 4368826 |
962650830 |
Configuration errors occurred on OMI graphics after failover and incorrect platform status was shown in the Platform Manager. |
|
|
IMS 4370129 |
962651081 |
Values shown in an OMI ViewApp did not match the values shown in the Object Viewer. |
|
|
IMS 4372944 |
IMS 4327477 |
962632286 |
Trend Tail sources did not work consistently during a WAN disconnection. |
|
IMS 4381159 |
962654268 |
After migrating to System Platform 2023 R2 SP1 P02 from System Platform 2017, the Description data type for some attributes became “InternationalString”. This caused the script for updating the Description to stop working and generated lot of warning messages. |
|
|
IMS 4405343 |
962664097 |
Write attempts to UDO.Dest[] failed with an error. |
|
|
IMS 4426837 |
962684724 |
The following warning was logged multiple times on a redundant AOS node: "ProcessSerializedAttributesOnWarm - Failed to serialize attributes to the remote partner" |
AVEVA desktop OMI resolved issues:
|
Originating Issue |
Related Issues |
Case/SR Number |
Description |
|
IMS 3412300 |
960428886 |
DataGrid Widget filter issues occurred in both default and checklist modes. |
|
|
IMS 3874937 |
IMS 3933822 |
960584789 |
The OMI client failed to connect to the data provider due to port 808 being unreachable. |
|
IMS 4062344 |
960641142 |
Slow graphic and reference updates and application freeze occurred upon GR disconnect. |
|
|
IMS 4069064 |
960636091 |
Phantom scroll bars appeared in sections of a pane that should be blank. |
|
|
IMS 4078285 |
IMS 3940646 |
960648426 |
Latency issues occurred after applying HotFix 3940646, which addressed random issues. The Embed function did not resolve in runtime. |
|
IMS 4098470 |
960649939 |
After applying HotFix 3940646, latency times did not improve for non-embedded symbols. |
|
|
IMS 4053611 |
960641089 |
While launching the web client, the number of files being downloaded was displayed instead of progress indicator. |
|
|
IMS 4100285 |
960570825 |
NavBreadCrumb Apps Root Path was not applied intermittently at application start-up. |
|
|
IMS 4103780 |
IMS 4247550 |
960650798 |
An OMI ViewApp stopped responding after opening and closing popupss |
|
IMS 4111272 |
960657603 |
After upgrading from System Platform 2020 R2 to System Platform 2023 R2 SP1 P02 and converting an application from InTouch to AVEVA OMI, the OMI ViewApp intermittently briefly froze during certain operations. |
|
|
IMS 4218557 |
960663697 |
When using the arrow keys to navigate between active clickable fields, a .NET error occurred and view.exe crashed. |
|
|
IMS 4230949 |
960668047 |
An OMI deployed ViewApp did not show changes during a delta deployment. |
|
|
IMS 4266940 |
960639162 |
When a user input animation was used and the Min and Max values were identical, a warning popup was shown, and if an entry box of a user input was called, it remained stuck on the screen. |
|
|
IMS 4278159 |
962467994 |
After upgrading galaxy from SP 2023 R2S P1 P01 to P02, objects took significantly longer to load in the ViewApp runtime. |
|
|
IMS 4297697 |
960666368 |
An OMI application randomly stopped responding. |
|
|
IMS 4332940 |
962627383 |
An OMI ViewApp that included a graphic that invoked the LogOff() API would crash when a user logged off, due to duplicate LogOff calls. |
|
|
IMS 4355443 |
962643794 |
Read failures occurred when entering playback mode. |
AVEVA OMI web client resolved issues:
|
Originating Issue |
Related Issues |
Case/SR Number |
Description |
|
IMS 4053611 |
960641089 |
While launching the web client, the number of files being downloaded was displayed instead of progress indicator. |
|
|
IMS 4073783 |
960622027 |
The OMI web client showed bad quality without any warning/error message, even though the OMI desktop application showed all data. |
|
|
IMS 4281400 |
962480007 |
OMI Web access through the F5 Load Balancer was not available to ensure that users could connect to the solution via the designated Virtual IP (VIP). |
Known issues
The following known issues have been identified in this release:
|
Issue |
Description |
|
IMS 4249870 |
After applying a patch to SP 2023 R2 SP1 and issuing a ForceFailoverCmd, the GR node reported a number of warnings related to "unexpected packet from AOS node." Workaround: To avoid these warnings:
|
|
IMS 4416834 |
If a Web OMI node is deployed on SP2023R2SP1 and you do not have the SMS configured, a cascade deployment of the Web OMI node will fail after you apply SP2023 R2 SP1 Patch 04. To avoid deployment failures and platform recovery issues, use the following procedure:
GetOrCreateAsync Unable to connect to MXDataProvider service using RunTimeData Client. Ensure that MxDataProvider service is running and Endpoint is discoverable. During the patch process, the following warnings are logged by the component vcp.services.onprem.dataaccess.exe: GetOrCreateAsync Unable to connect to MXDataProvider service using RunTimeData Client. Ensure that MxDataProvider service is running and Endpoint is discoverable. CreateInitialRunTimeDataClient: Could not connect to MxDataProvider Service for galaxy: '<GalaxyName>'. Retrying Attempt: 1
|
|
IMS 4482903 |
As of System Platform 2023 R2, the Historian requires a trusted connection. The System Management Server is the default method for establishing trust between the Historian server and client nodes. Therefore, historization and playback may not work if SMS is not configured. Workaround: You can do any of the following to establish trust between the Historian and client nodes:
Refer to the Historian documentation for certificate installation instructions. |