Application Server 2023 R2 SP2 release notes

Originating Issue

Case/SR Number

Description

3353370

962783582

Object comments could be partially logged when updates were performed using the Secure Write function.

4099325

The performance of the following Foxboro CS objects was degraded when comparing the performance of System Platform 2023 R2 SP1 P02 with CS 8.0 and System Platform 2023 P02 with CS 8.1:

• Strategy Object

• FBM object

• Device object

4288870

960670774

In redundant DI object configurations, switchover operations did not properly unsubscribe inactive DI objects from the OI Gateway when attributes were configured with different input and output addresses.

4340728

962634481

Sustained memory and thread increases in the aaUserValidator process could cause valid Access Level values in InTouch Web Client to be reset to -1.

4361309

962613502

A while true script that compared two different values was not triggered regardless of any difference in values.

4386007

962649264

In multi-session RDS environments, OMI runtime views intermittently stopped updating displayed values and animations, causing stale data to be shown until users navigated away from the view and then returned.

4388066

962615289

After an AppEngine failover in warm-redundant configurations, .Msg tags could display incorrect OnMsg or OffMsg text despite the associated Boolean attribute retaining the correct value. The displayed message did not update until the attribute value changed.

4394626

962664908

In redundant multi-galaxy configurations, failover between active and standby galaxies could result in delayed reconnection of monitored data items, causing a noticeable delay before normal data updates resumed.

4395822

962664908

OPC Client–based objects could experience intermittent initialization failures following a platform upgrade, causing affected objects to remain in the Initializing state until they were redeployed.

4407929

962669690

Following an Application Engine failover in a redundant configuration, Redundant DI objects could fail to recover correctly. In addition, the configured failover delay was not applied consistently during subsequent switchovers.

4411557

962666486

Importing large numbers of object instances from CSV files was significantly slower in System Platform 2023 R2 SP1 P03 and SP 2023 R2 SP1 P04 than in earlier releases.

4422067

962624011

RDI objects could unexpectedly enter a quarantine state during normal operation, resulting in loss of communications and requiring operator intervention to restore service.

4426837

962684724

Standby nodes in warm-redundant environments could log repeated "ProcessSerializedAttributesOnWarm - Failed to serialize attributes to the remote partner" warnings during transient network interruptions.

4427599

960645186

In redundant Application Engine configurations using DI and RDI objects, attribute quality could transition to Initializing after a failover and remain in that state indefinitely, preventing attribute data from returning to normal operation after the standby Application Engine became active.

4454612

962533566

Invalid items in DDESuiteLink configurations could cause sustained memory growth in AppEngines hosting a single DDESuiteLink object.

4471355

962704156

After a primary node restart in warm-redundant environments, a secondary AppEngine could fail to start correctly and prevent hosted objects from resuming normal operation.

4499696

962674559

During template check-in, IO overrides on instances were sometimes removed unexpectedly due to synchronization issues, resulting in inconsistent instance configuration.

4500950

962665251

Importing templates into large Galaxies could take an excessive amount of time to complete, particularly when importing templates with higher object versions. In some cases, the import operation required several hours to finish, resulting in significantly reduced galaxy management performance.

4502609

962709670

Migration of CAB files from System Platform 2020 R2 SP1 P01 to System Platform 2023 R2 SP1 P03 could fail when symbol overrides contained custom properties with duplicate names. In some cases, the migration failure caused the Galaxy Repository process to restart.

4513729

962724160

When localization data was exported for large object selections, the export operation could time out before processing completed. The export failed and generated an incomplete output file that contained only header information and no localization content.

4517577

962712335

During galaxy migration, instance-level script references could be lost as cross references were resolved, resulting in missing external script references after the migration completed.

4523737

962733984

Intermittent data update failures could prevent runtime data from refreshing correctly, causing the OMI application to become unresponsive and generate read operation failures in the Runtime Data Provider.

4549772

962739614

Saving object instances created through GRAccess using the .Container property could generate exceptions in AttributesTab.dll and prevent the save operation from completing successfully.

4560183

962749341

After upgrading to System Platform 2023 R2 SP1, new graphics and galaxy objects with duplicate names could not be created, even when existing graphics and objects with the same names had been retained during galaxy migration. This behavior affected applications that relied on matching graphic and object naming conventions.

4561143

962750311

Opening or closing HMI applications, or activating and suspending attributes in the Object Viewer watch window, could generate unnecessary warning messages in the Application Server logs.

4561535

962751664

Temporary files generated during Industrial Graphics data retrieval were not removed after processing. As the number of accumulated files increased, Application Server startup performance degraded and the aaGR service could fail to start within the expected timeout period.

4572908

962741628

Opening the Operations Control Platform Manager and subsequently closing it sometimes caused mmc.exe to terminate unexpectedly.

4574992

962757936

Template check-in caused extended blocking behavior, impacting IDE usability and InTouch runtime despite having sufficient server resources available.

4609760

962772161

Object deployment intermittently failed for objects with scripts, requiring manual validation and redeployment to complete successfully.

4663483

962783582

AppEngines could become unresponsive during runtime operation, causing application objects to report "Unknown: Comm Error (DISource not accessible)" and interrupting data communication.

4638031

962765906

In galaxies with large numbers of security groups, opening the Galaxy Security view could cause prolonged load times and make the IDE appear unresponsive.

4695276

962765906

When selected areas and objects were validated, some objects could incorrectly enter the Updates Pending Deployment state even though no configuration changes had been made. As a result, the objects required redeployment to clear the status, and the condition could reoccur during subsequent validation operations.

4730839

962742363

Importing alarm translation files could result in significant performance degradation and excessive processing times, even when importing a small number of translation entries.

4748940

962724812

After a redundancy switchover, alarms sourced from PLC-driven attributes were not generated as expected.

4765588

962822697

In warm-redundant environments, the Redundancy.FailoverOccurred attribute was not updated correctly following a failover back to the primary AppEngine, causing the attribute to report an incorrect failover status.

4799652

962807273

Object Viewer searches using the All option in the Platform or Engine filters could fail with a "Configuration error: Invalid reference" message and prevent object information from being retrieved.

4830685

962749192

For some domain users, System Platform displayed only the username and did not populate the corresponding Full Name field.

4831996

962850609

In distributed OMI environments, alarm notifications could fail to appear in Alarm Clients on some OMI nodes even though the underlying alarm conditions were active and graphics continued to display current runtime data correctly.

4832120

962850895

Exporting alarm translations at the galaxy level could take an excessive amount of time to complete and, in some cases, fail to finish within an acceptable timeframe.

4847304

962854377

After a graphic was linked to a template, the template could not be checked in.

4929879

962866290

In System Platform 2023 R2 SP1, connecting to a second Galaxy Repository could fail after successfully connecting to another Galaxy Repository, preventing users from switching between Galaxies in the IDE.

Issue ID

Description

5045344

After upgrading the GR node from SP 2023 R2 SP1 P04 to SP 2023 R2 SP2, data updates freeze, or object references in the runtime nodes (OMI or Intouch WindowViewer) that have not yet been upgraded do not resolve references from the upgraded GR node.

Workaround

If data updates in the client node are frozen, or object references fail to resolve from the upgraded node on the non-upgraded client node, restart the AVEVA Watchdog service to reinitialize the MxDataProvider service.