Application Server 2023 R2 P01 release notes

Original Issue

Related Issues

Case/SR Number

Description

2985894

960354373

When using the warm redundancy option, the aaCALWrap.exe process consumed a great deal of memory.

3018396

960341870

In some cases, after failover from the primary server to the backup server, some shelved alarms did not show in the shelved alarm list. The status of these alarms was still "shelved," they just did not appear when listing shelved alarms.

3023716

960375402

In a Multi-Galaxy configuration, the warning message Asb.Configuration SystemAuthenticationService.GetServiceBusPlatformConfiguration : Error occurred while communicating with database... was logged continuously on the GR node. This happened because the passphrase solution could not be found.

3039913

960380498

When System Platform was installed in a non-default location, such as on the D: drive, deploying WinPlatforms caused errors and warnings in the log and the platforms were not available in the OCMC Platform Manager.

3040483

960381315

Importing objects via a package (.aaPKG) file incremented the objects' versions by two steps.

3046335

960376548

Alarms which did not return to normal for a very long time (approximately one month) appeared in Historian with a negative duration.

3067809

960390378

Improved performance when deleting objects.

3081734

960352243

Objects that were set to Scan on Demand were not always added to the list for OI Server. As a result, these items were sometimes not scanned.

3109688

960387634

GRAccess could not write to any attribute that had a description field. Therefore, it could not create any object that contained any attribute with a description field.

3166242

960392759

In a warm redundancy configuration, after failover occurred, the EngineObjects[] attribute no longer contained a list of deployed objects.

3198388

960395617

When deploying an OMI ViewApp that included object wizards, the PCS Framework used more than 90% of the server's CPU.

3201271

960390809

If a galaxy was backed up using the Operations Control Management Console (OCMC), then a new galaxy was created from the backup, you could no longer connect to the original galaxy.

3242289

960400382

Collecting diagnostic information using the default configuration could create an unlimited number of files in the ArchestrA temp folder.

3259264

960403401

If an exported CSV file contains two objects which have attributes with the same name but different types (for example, one is Boolean and the other is a string), trying to import the CSV file fails with an error message.

3260947

960396305

Low priority alarms were being historized even though the galaxy was configured not to do so.

3261424

960404170

If you created an instance from a master template, then changed the default settings for an object wizard in the master template, you could not edit the instance or export it to a CSV file.

3264570

960404338

If the input source and output destination for an attribute associated with an object wizard were different, the output destination was set to --- if a change was made to the object template. This occurred even if the attribute was created in the object instance and did not exist in the template.

3270224

960405891

Importing a package file containing a graphic with multiple client controls which used the same dependent DLLs failed.

3270262

960405918

With multiple people using the IDE at the same time, the aaGR service crashed every 15 to 25 minutes.

3270629

3065034

960390172

Enabling the System Management Server slows down log in to OMI ViewApps at runtime.

3278545

960407805

Longer than expected time to failover from one server to another caused unacceptably long gaps in historized data.

3279907

960407298

There was a small memory leak in the module aaGlobalDataCacheMonitorSrv. Eventually, this caused the following warning to be written to the log repeatedly: Warning GlobalDataDistributionClientRuntime Synchronizing local data cache with global data repository has failed for 20 consecutive times. As the memory leak was very small, it could take several months before this warning appeared.

3281737

960406315

Post-upgrade from System Platform 2023 P02 to System Platform 2023 R2, AVEVA.IOMBLS.ServiceHost.exe caused memory leak and then stopped responding.

3282637

960407900

When using the Assign to option to assign an object to an area, typing in the list box the on the dialog did not move the list to match your entry.

3293455

None

Validating a large object sometimes caused a System.OutOfMemoryException and could cause the IDE to crash. For example, this could happen when migrating a galaxy that contained large objects.

3303557

960411247

The I/O Mapping view showed attributes for an instance even if those attributes were excluded by object wizard choices.

3318750

960391528

Closing and reopening the IDE caused deployed VIewApps to incorrectly show that they needed to be redeployed, even though they had not changed.

3324307

960417221

Checking in changes to a template and propagating the changes to its children could take hours and then fail, even though the IDE showed that it had completed successfully. When this occurred, the template remained checked out and error messages were written to the logger, starting with something like: Error WWCdi Error 80040E14: Description 'Violation of PRIMARY KEY constraint 'PK__#trimatt__38174EC39114E2BF'. Cannot insert duplicate key in object 'dbo.#trimattr'. The duplicate key value is (512616, 1041602300). Line:308, Store proc:internal_ow_streamline_dynamic_a appeared