Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Application Server

July 2025

  • Last UpdatedJul 16, 2025
  • 3 minute read

Application Server 2023 R2 SP1 Patch 02 includes the resolved issues listed below.

The description of limit alarms has been updated to include information about configuring the alarm deadband.

Originating Issue

Related Issues

Case/SR Number

Description

IMS 3696863

960523687

After disconnecting and reconnecting the network between the two galaxies, communication between the galaxies could not be reliably established.

IMS 3735974

960501011

When a redundant AOS server hosting a DDESuiteLink DI object was rebooted, corresponding failover DDESuiteLink DI object went on alarm, but the alarm could not be acknowledged.

IMS 3747167

960543938

The Alarm Client control did not correctly display attribute names when client mode was set to Historical Alarms.

IMS 3769257

960550619

When OPCClient Block Write functionality was used, setting the Transaction Timeout to 5000ms while executing repeated Block Writes faster than 5000ms resulted in warnings and errors, and the object eventually ceased to function even though the transactions completed successfully.

IMS 3771589

960543517

Exceptions occurred while looping IGObjects obtained using the GRAccess Toolkit.

IMS 3790931

960547566

When the IDE was launched as a non-admin user, WWPackageManager error messages were logged and license details were not shown. These issues did not occur when the IDE was launched as an admin.

IMS 3796539

960446167

An AppEngine changed to store and forward mode when the Redundant DI object switched to backup

IMS 3796557

960558125

An attribute of data type BigString did not retain the value if it was set to "calculated retentive" after the object was redeployed.

IMS 3798813

960533461

The SetDateTimeParameterByName() method inserted the wrong timestamps into the text of a SQL statement.

IMS 3799173

960558336

The time needed to check in the same template after editing varied greatly. and seemingly at random, sometimes taking a couple of minutes and sometimes taking 40 minutes.

IMS 3804684

960551151

Using aaMethods to call OPC UA methods did not succeed and warning messages were logged..

IMS 3807119

960553132

When the galaxy Security page was opened and began synchronizing, the IDE was unresponsive for several minutes, until the selected authentication mode indicated that it was active.

IMS 3809329

IMS 3524696 IMS 3710535

960533754

Multiple instances of AppEngines stuck following reboots.

IMS 3815386

960564859

Objects that had graphic names longer than 32 characters caused issues when deploying the associated ViewApp. A warning message was displayed that some files were missing on the node where the ViewApp was deployed.

IMS 3842383

960437869

After installing HotFix 3665000 to address a GR Memory leak, object validation used a large amount of memory, which did not get released.

IMS 3851020

960570443

The IDE stopped responding after associating an attribute with an object wizard. GRAccess was used to create and set the initial attribute values.

IMS 3853558

960578140

When the IConditions.Remove() function in GRAccess was used, it removed the wrong item.

IMS 3878716

960585149

The Object Viewer worked very slowly across all platforms.

IMS 3882564

IMS 3264570

960586712

Instance IO sources were changed for attributes associated with an object wizard when importing an updated template.

IMS 3892601

960588874

After editing a a base template, check in of the object did not complete, and a primary key error was logged.

IMS 3918559

IMS 3918559

960577383

Multiple messages were created after installation of a fix.

IMS 3927113

960588463

After importing templates into production galaxies, pending changes remained, forcing manual validation of all instances.

IMS 3929566

960461295

Writing IO chunks exceeded the timeout of 60 seconds.

IMS 3942049

960605256

It was not possible to check in a master template.

IMS 3977097

960616116

After upgrading to System Platform 2023 R2 SP1 P01, any alarm with a severity of 5 was setting the fifth element in the AlarmCntsBySeverity[] array. This caused all alarms to signal an alarm condition.

TitleResults for “How to create a CRG?”Also Available in