AVEVA™ Application Server 2023 Patch 03 Readme

Original Issue

Related Issues

Case/SR Number

Description

IMS2414287

960291144

After installing a Microsoft update, started to see "APPCRASH events for aaObjectViewer.exe and wm.exe in the Windows Logger after closing the Object Viewer. Tthese events did not cause any problem with using the IDE.

IMS 2441229

960283947

The GalaxyBrowser pop-up window always opened to the last position it had occupied for any user. If the new user had a smaller monitor than the previous user, this sometimes caused the Galaxy Browser position to be completely off the screen of the smaller monitor.

IMS 2452008

960287309

After exporting a Galaxy from 2014 P01 and then importing it to 2023, the default element styles were missing from the new Galaxy.

IMS 2464781

960294256

With redundant engines deployed and redundancy alarms enabled, no alarm was generated when the primary engine shut down and the redundant engine took over.

IMS 2473677

960295264

In some cases, after an upgrade from 2014 P01 to 2023, customized alarm severity images appeared enlarged and distorted.

IMS 2476051

960297286

The IDE opens the wrong object in the Object Editor if you perform these actions, in order:

1. Select an object (object A) in the Deployment pane.
2. Select an object (object B) in the Templates pane.
3. From the Home ribbon, select Open or Open read only. This correctly opens the Object Editor for object B.
4. Close the Object Editor.
5. Again, from the Home ribbon, select Open or Open read only.

   This time, the Object Editor opens for object A instead of object B, as it should.

IMS 2482518

960290054

When historizing alarm data using A2ALMDB, the displayed timestamp for buffered data was incorrect. It did not take into account the time zone offset from UTC.

IMS 2489138

960281235

Importing previously exported alarm messages sometimes failed with a timeout error reported in the log.

IMS 2493247

960300171

When there were complex visibility expressions in the Object Wizard Visibility Settings, the choices chosen for an instance did not display in the IDE, though they worked correctly in runtime.

IMS 2513357

960291831

After upgrading from 2017 U3 SP1 to 2020 R2 SP1, when a new item was added in the PLC\OFS UPC server, the new object did not show any data until the OPCDA DI object was redeployed.

IMS 2535753

960300675

Importing a template with I/O enabled overrode existing instances' settings for invertvalue and deadband.

IMS 2564110

960303538

Restoring a Galaxy .cab file failed if there was more than one .mdf file in the database.

IMS 2567323

960225587

If an Object Wizard included a User Defined Attribute (UDA) with:

• the buffered property set to true
• an option to set the UDA to Used or Not Used

  and you created an instance with the option set to Not Used, saving the instance caused the warning Buffered enabled UDA <attribute name> does not have an input source.

IMS 2574326

960297592

After working correctly for a period of time, the Web Client display showed ###Hatch#. Restarting the ASBService service fixed the issue, but it re-occurred after periodically. Log showed Failed to connect PDMS-Web. Error description: "No connection was established at the service endpoint".

IMS 2582433

960312547

After migrating from 2020 R2 SP1 to 2023 P01, deploying an instance created from a template that contained a series of User Defined Attributes caused multiple warning messages in the log. The deployment appeared to be successful, but attempting to undeploy the instance caused an object is not registered to the engine error and sometimes hung the engine.

IMS 2588645

IMS 2541429

960295797

If an Application Object Server hosting the primary object engines was unplugged from the SCADA network, then re-attached, the platform failed to restart.

Issue Number

Description

IMS 2486054

In certain circumstances, the ShowGraphic window will not be sized correctly when a Layout is used as the content, with the "Initial State" property set to "FullScreen".

Workaround: Should you experience this issue, a HotFix is available that you can apply to Patch 03.

Original Issue

Related Issues

Case/SR Number

Description

IMS 2325393

960256256

Enhanced the logging of the application category component to better troubleshoot object deployment issues.

IMS 2329110

960259732

Improved check-in performance after adding options to a template.

IMS 2338358

960263766

In the galaxy browser, using filter by attribute did not work for device integration objects or RDI objects.

IMS 2354864

IMS 2167852

960269666

An InTouch application running in a remote desktop session would temporarily freeze for a few seconds to a few minutes, then resume working normally.

IMS 2357627

960264356

After turning on the Simplified Layout option in the Application Server IDE, the keyboard shortcuts for IDE features did not work. This continued until you restarted the IDE, even if you turned off Simplified Layout.

IMS 2365598

960271756

After upgrading from 2014R2 SP1 to 2020R2 SP1 (with or without Patch 01), Boolean ASP arrays stopped working. The arrays were configured following the instructions in Tech Note TN000022758 (legacy ID TN423).

IMS 2372346

960270563

Under certain conditions, when checking in a template that had had unrelated changes made, the AlarmSourceAttr attribute was locked in error.

IMS 2384675

960243658

When using a DDESuiteLink object to read from an OI.MQTT server, after a disconnection and reconnection, store-and-forward late data was being played back through the HMI and was missing from the historian.

IMS 2396741

960275948

When "Enable advanced communication management" is enabled in the IDE, value for attributes stop updating when written to with a different datatype.

IMS 2396784

IMS 2339386

960278840

The AVEVA Galaxy Repository Service (aaGR.exe) was sometimes crashing randomly.

IMS 2412334

IMS 987524

960275032

After updating an OMI ViewApp and deploying it to two or more hosts, launching the ViewApp sometimes still launched the older version of the ViewApp.

IMS 2420563

960282853

After changing a template with a large number of child objects, the changes were not always propagated to all children. In this case, the save process reported that it was successful, but errors were recorded in the logger.

IMS 2422899

960284673

The Change Network Account dialog box was unreadable on a Chinese Operating System after upgrading to 2023 Patch01.

IMS 2422443

IMS 2380893

960244101

Using a GRAccess application to change the Symbol Wizard option descriptions of a UDO changed the OMI ViewApp runtime behavior of the embedded symbol.

IMS 2435545

960278150

For some Galaxies, Galaxy load and validation took much longer in 2020R2SP1 than it had in 2014R2SP1.

IMS 2442091

960265213

In the IDE, the properties window for an attribute was always too small when it first opened and needed to be resized.

Original Issue

Related Issues

Case/SR Number

Description

IMS 2217089

960225037

When trying to show more than 100 items, the Content Presenter app had unacceptably poor performance and high CPU usage.

IMS 2286445

960247928

If a button configured with ShowContent to open the Web Browser app was added from within the ViewApp editor, the Web Browser App did not work. However, If the button was added from within the layout editor, it worked.

IMS 2288058

960246824

When previewing an OMI ViewApp, selecting an asset that was not in the current area of the ViewApp caused OMI to crash.

IMS 2290229

960254115

When an embedded graphic included a Windows Common Control (WCC), changing the embedded graphic's size also changed the embedded graphic's position in the parent graphic.

IMS 2311590

960257093

When a graphic was configured using Symbol Wizard options, animations in the graphic did not work in an OMI ViewApp.

IMS 2314502

IMS 2219591

960243452 960273575

In a multi-Galaxy environment, you could not write to a remote Galaxy attribute from a popup graphic in an OMI ViewApp.

IMS 2384559

960260957

After attempting to add an attribute with an invalid name and then deleting it, if any other attribute was duplicated, it caused the IDE to crash.

Issue Number

Description

IMS 2486386

When you shut down a backup platform to install the patch on it, alarm information may stop being sent to all clients on all nodes. (This is uncommon, but may happen.) The primary logger will show a message similar to: Warning ITAlarmProvider UpdateAlarm - Received message 8 with no alarm name for alarm provider.

If this happens, just continue the patching process. When the backup platform has been patched and redeployed, alarm information will again be sent to all clients.

This issue is fixed in Patch 02, once you have installed Patch 02, it will not occur during future patch installations.

Original Issue

Related Issues

Case/SR Number

Description

IMS1848600

960157869

Creating a new instance of a working, deployed OMI application caused all of the working instances of the application to need to be redeployed.

IMS1860423

960174949

Intermittently, the Secured Write "Retrieving Reason Description" timed out and displayed the message Unable to retrieve Reason Description.

IMS1877088

960176481

In dynamic text referencing for Integer alarms, comment did not work with String arrays.

IMS1888024

960161993

While importing objects from a specific CSV file, the IDE closed with the message Connection to the Galaxy Repository has been lost. Archestra IDE will shut down.

IMS1892267

960171722

If a platform was deployed during an upgrade from AVEVA System Platform 2020 to System Platform 2020 Patch 01, the AlarmClient and TrendClient controls were not updated. No warnings or error messages were written to the log.

IMS1911736

960166135

While deploying a redundant engine, the bootstrap service encountered an error, stopping the engine and the platform. The error message generated was aaEngine.exe RedundancyPrimitiveRuntime2 Error INVALID HRESULT LINE 246 FILE <path>\RedundancyPrimitiveRuntime.cpp

IMS1914761

960180506

Some objects were not updating dynamic data on the Application Object Server. Redeploying the objects fixed the issue. The cause was a communications issue between the Telemetry Server and Application Server

IMS1926125

960179494

Changing the SQL Server Compatibility level to 2019 made importing objects unacceptably slow.

IMS1934343

1819846 1862300

960190420

There was a performance issue when using a derived template to create instances through GRAccess with a large Galaxy (Galaxy size over 2GB, 31K IO size).

IMS1939546

960191284

InTouch values were not being updated due to an issue with the NmxSvc service.

IMS1941500

960185850

When using the scan mode "Active on Demand" and warm redundancy for the backup engine, failover to the backup engine caused all items to become active.

IMS1949369

960192655

Changing a limit alarm value did not cause the alarm condition to be re-evaluated for buffered attributes. A buffered attribute's alarm state did not change until the next time the attribute value was updated.

IMS1969449

960196010

After writing to an attribute in the OPC client, the client that updated the attribute did not see the new value, while other clients did.

IMS1988488

2118272

960200700

After upgrading from AVEVA System Platform 2020 to System Platform 2020 R2 SP1, a Galaxy which had not shown any object errors or warnings showed over 3000.

IMS1991737

960201613

In some cases, after aaGR.exe was restarted, it took up to ten minutes to restart the IDE or OCMC (formerly SMC).

IMS 1992148

960192426

The search feature in the System Platform IDE was unacceptably slow in certain system configurations.

IMS1998690

960128047

Under certain conditions, the AreaHerarchy.Xml could not be updated during deployment. Though this did not cause an error message, items could be missing or incorrectly marked as deployed or undeployed. This could cause, for example, alarms not to display in the EAC.

IMS2024863

960206498

Using the mouse to select part of the text in a field did not work.

IMS2068077

960216050

When using Azure AD as the authentication provider, the IDE could not retrieve roles from Azure AD. Instead, it displayed the message Failed to retrieve groups. See logger for details.

IMS2074106

960194657

One customer's Application Servers were having a number of consistency issues, including inability to deploy OMI applications.

IMS2086283

960188670

Intermittently, data and graphics were loading slowly in OMI applications.

IMS2101753

2287792 2130255

960221853

The OPC client failed when browsing items from the OPC server.

IMS2127825

960111993

There were delays in data updates in an OMI application when switching between primary and backup servers.

IMS2137381

960226495

If a client computer running the alarm control was rebooted, shelved alarms appeared in the control as if they were active. To correct this, each alarm had to be unshelved, then shelved again.

IMS2138833

960214835

In some cases, adding a new symbol to a graphic corrupted the graphic, causing it to show a circular reference message. This could also affect other graphics in the same object.

IMS2139129

2137841

960228455

After modifying a template, the template's child objects showed warnings. There were no warnings before the template was modified. Validating the objects cleared the warning state.

IMS2145673

960230037

In AVEVA System Platform 2023, if you cleared the Associate Galaxy Graphics check box for an InTouch ViewApp template, the option remained selected when you opened the template again.

IMS2149159

960221364

The output destination for some instances was changed from "---" to the default when a locked property in the instance's template was changed and the template was checked in.

IMS2158159

960219741

Changes to a symbol that belonged to an area were not being saved correctly. When the area was closed and re-opened, the original symbol reappeared, without the editing changes.

IMS2171127

960218196

The .AlarmInhibit setting was not retained when an Engine was redeployed.

IMS2178063

On a Japanese operating system, the Graphic Editor Save Confirmation dialog shows overlapped message text while saving a graphic.

IMS2178106

The AVEVA System Platform 2023 IDE became sluggish and unstable when creating 30 instances of an MES Application Object (OCO with PEM enabled).

IMS2179834

960238000

Deploying an OMI ViewApp after importing new objects into the working Galaxy failed with the message Error occurred in generating the Asset Hierarchy.

IMS2180111

960223297

Exporting an object to a CSV file, changing a field such as ShortDesc, and re-importing the object resulted in unexpected and incorrect changes to the object's wizard options.

IMS2180583

960238103

After rebooting a platform, the platform engine crashed while the application engine instance continued to run. There were no MX communications and you could not deploy or undeploy objects on the platform.

IMS2183152

Intermittently, when using a warm redundant engine, if the primary engine was disconnected from the network, causing failover to the backup engine, then reconnected to the network, the Object Viewer could not resolve references. Attributes showed bad quality with a Communication Error until the Object Viewer was closed and re-opened. This issue was specific to the Object Viewer; OMI VIewApps and InTouch Applications showed correct values.

IMS2184681

960235646

When using Azure AD as the authentication provider, only groups without a space in their names were listed when adding new roles.

IMS2219073

960229273

New users could write to an attribute from an OMI VIewApp only when on the Application Object Server where the object was running. The attempt failed with a message saying that the user did not have the needed permission. Once they had written to an attribute from that server, they could then write to attributes from any operator machine.

IMS2192057

960230061

With several remote users connected to the GR node and using the IDE, the IDE would sometimes crash.

IMS2199153

960214756

At times, the ConnectionStatus of an RDIObject was Disconnected despite one of the DIObject being Connected. This occurred randomly.

IMS2213923

960227806

In AVEVA System Platform 2023, you could not retrieve the value of the TYPE parameter from a DIObject. The parameter seemed to be removed by the ScanGroupRuntime.

IMS2219405

960236095

In AVEVA System Platform 2023, when using Azure AD as the authentication provider, once a user had logged into an OMI VIewApp using their user name and password, they could then log in to InTouch for System Platform using only their user name, without having to enter a password.

IMS2292916

960253318

When using a redundant AppEngine, the View In Object Viewer feature did not automatically focus on the selected object.

IMS2293862

960245764

The Cross Reference tab for an object did not always show all cross references.

IMS2296755

960251997

Deploying objects that pointed to a DDE/SL object on another AppEngine on the same platform caused LMX warnings during or just after deployment. In addition, some objects, not limited to the ones that received the warning, showed bad quality in the Object Viewer.

IMS2304964

960234377

The GR Platform aaEngine process kept using increasing amounts of memory until the system became unresponsive and showed the message Heap Create failed Not enough storage is available to process this command. At that point, the server needed to be restarted.

IMS2320864

960262032

During some installations, the AVEVA NmxSvc service was not set up properly.

IMS2322204

960245921

If failover to a backup GR node occurred after an alarm occurred but before it was acknowledged, acknowledging the alarm sometimes failed with the message Failed to Ack the Alarm; Operational error: Alarm Acknowledged Already.

Original Issue

Related Issues

Case/SR Number

Description

IMS1311645

1404698

960078748

In AVEVA System Platform 2020 R2 P01, data in faceplate graphics was slow to update.

IMS1923348

1949157

960186853

The size of a faceplate graphic was being determined by settings in the template instead of the settings in the derived instance.

IMS1932837

960186425

In AVEVA System Platform 2020 R2 P01, embedded vertical fonts appear distorted in OMI ViewApps.

IMS1936152

960188224

When using the ShowGraphic() function to display a graphic in a popup window, the graphic was displayed correctly in an InTouch application but was shifted down in an OMI ViewApp.

IMS1989797

960191143

Using a list view control to display users and groups in an OMI ViewApp actually displayed only users. Groups were not shown.

IMS2034413

960195794

Using the ShowContent() function in an OnShow script to load secondary layouts into the panes of a "main" layout was unacceptably slow in some configurations, leading to time-out errors and one or more layouts failing to load.

IMS2047527

960211554

An OMI ViewApp was sometimes crashing at runtime with an OWS09 error when a user clicked a layout. This behavior appeared random.

IMS2070745

960214465

If a pane was defined as multiple/tabbed, displayed values were disappearing when a different asset was selected in the ViewApp.

IMS2074100

960209524

When using the Trend Pen element in a graphic, with the FillTrend property selected, an extraneous vertical line appeared at either end of the Trend Pen element.

IMS2117058

2167966

960223948

Changing the graphics used in an OMI ViewApp and deploying the changes did not always update the graphics in the ViewApp.

IMS2132541

960226167

Opening an InTouch OMI application on a system that did not have InTouch installed caused multiple warning messages to appear in the logger.

IMS2167300

960227733

The MyPlatform attribute sometimes resolved to one of the other platforms in the Galaxy instead of to the current platform.

IMS2187523

960215199

When multiple instances in a model hierarchy contained common text in their names, the graphics contained in some of the instances did not always display correctly in an OMI ViewApp. For example, the autofill property did not work.

IMS2199335

960241624

After importing updated graphics into a Galaxy, the affected OMI ViewApps could not be deployed. The deployment failed with the message Error occurred in generating the Asset Hierarchy error event in the Galaxy node.

IMS2202531

960237108

Using a graphic in an OMI ViewApp to write to the Me.AlarmModeCmd attribute failed; the attribute value did not change. The message Write attempt to Me.AlarmModeCmd failed with error Operational was written to the log.

IMS2228133

960240919

Right-clicking on particular graphics in an OMI ViewApp caused the ViewApp to crash with the warning message "An unexpected error has been detected" "System.InvalidOperationException: This visual is not connected to a PresentationSource..."

IMS2262836

960249147

In the Alarm App, the Details column and the Delete icon did not appear, making it impossible to delete or modify an existing query.

IMS2269408

960246297

You could not copy and paste text from a web site using the WebBrowser control in an OMI ViewApp.

IMS2283646

960253037

In AVEVA System Platform 2020R2 SP1 P1, some of the customer's OMI VIewApps crashed during use with the message system.nullReference Exception for OnShow script on navigation to different symbol.

IMS2330844

960254124

Under some conditions, it took a long time(more than five minutes) to deploy an OMI application.

IMS2363862

None

When invalid license information is entered in the Configurator, running an OMI application should write a Demo mode activated message in the logger. This message was not being generated.

Item

Location of Change

Existing Documentation

Change

1

Application Server User Guide
IDE.pdf, page 218

Understanding Alarms > Limit Alarms

AVEVA Application Server Help

https://localhost:5000/AVEVA Application Server/#/home/248722/10/11

You can also configure alarm and time deadbands for limit alarms. The alarm deadband is expressed as a percentage of the attribute’s full value range. The deadband value sets the percentage of the total range that the attribute value must change to reset a limit alarm to the inactive state. For example:

• An attribute's full value range is 0 to 50, and the HiHi alarm limit is 40.
• The alarm deadband is set to 5. Since the attribute's range is 50, the actual alarm deadband value is 2.5 (50 * 5%).
• The attribute value reaches the HiHi alarm limit (40).
• To reset the HiHi alarm to an inactive state, the attribute value must fall below 37.5 (40 - 2.5).

The existing text is changed to the following:

You can also configure alarm and time deadbands for limit alarms. The alarm deadband is an absolute value, in engineering units, that the attribute value must exceed the configured HiHi, Hi, Lo, or LoLo limit before the alarm is triggered, or that the attribute value must revert to before the limit alarm resets to its inactive state. For example:

• The HiHi alarm limit is set to 90.
• The alarm deadband is set to 5.
  • The attribute value must exceed 95 (limit plus deadband value) to trigger the HiHi alarm.
  • The attribute value must fall below 85 (limit minus deadband value) to reset the HiHi alarm to an inactive state.

Issue Number

Related Issues

Case/SR Number

Description

L00155428

None

The Analog Value Display Animation displayed the value by using the 'Bad Quality with No Value' character, even though the bad quality reference had a previous good value.

IMS 1441871

960093655

In Application Server 2020R2 using FLEX licensing with Enterprise License Manger 3.7, warnings were generated in the System Platform Logger. The system continued operating normally despite the warnings.

IMS 1453607

960101956

In Application Server 2020R2, the SQLData Object stopped communicating and generated exception 0x80040014. The object did not return to normal functionality unless its AppEngine was restarted, even after communication was restored.

IMS 1487423

960100544

Platform Unable to start after power outage of the servers rack when network reestablishment takes more than 5 minutes. The domain controller communication and inter node communication takes 5 minutes after such failure.

IMS 1488140

IMS 1530370

960097543 960115246

After migrating from Wonderware System Platform 2014R2SP1 to System Platform 2020R2, the upgrade resulted in new operational permissions being added to the "Operate" security groups.

IMS 1490975

960084666

An InTouchViewApp that was migrated from Wonderware System Platform 2014P01 to Application Server 2020R2P01 required much more time to deploy than it did prior to migration.

IMS 1495193

960102891

A deployed AVEVA OMI ViewApp showed a message that graphics were not available, and the size of the deployed ViewApp, as indicated in the Application Manager, was much smaller than its actual size.

IMS 1502642

960097133

A user in a nested group was unable to open the IDE in a domain environment, even though the user was a member of the aaConfigTools user group.

IMS 1503391

960099917

In a galaxy that used OS Group security, some objects configured with an object wizard stopped working when these objects were moved to a different security group.

IMS 1513716

960104877

While attempting to restore a System Platform 2020R2P01 galaxy, an error message was shown stating that there was a galaxy name conflict, and the restore failed. This was traced to a primary key constraint error.

IMS 1516752

960109441

After migrating a galaxy from Wonderware System Platform 2014R2 to System Platform 2020, one specific template could not be checked in after editing, even though the check-in dialog said that check-in was successful.

IMS 1520896

960113669

The IDE component could not be installed for System Platform 2020R2, and the message that the GalaxyTagDictionaryServer.dll module failed to register was logged.

IMS 1520972

960107265

All nodes in a System Platform 2020 system lost communication when the GR was rebooted, and restoring communications between nodes was very slow.

IMS 1525029

960113426

The SP attribute of an AnalogDevice object remained in Initializing state with NaN as the value.

IMS 1534670

960105301

After migrating an InTouch Modern application from Wonderware System Platform 2014R2SP1 to System Platform 2020, none of the animations worked unless the custom properties for each graphic were opened.

IMS 1544328

960107552

The aaEngine process where a Redundancy object was deployed had an increasing handle leak that caused the engine to stop working.

IMS 1575561

960112366

After both the primary and RMC network connections were interrupted, the standby AppEngines remained in Standby-Not Ready state and constantly restarted, and the RMC connection could not be restored.

IMS 1576698

IMS 1548414

960109819

After HotFix IMS 1548414 was applied to System Platform 2017U2, an AnalogDevice SP attribute with a reference did not become active until the reference was added to the Object Viewer.

IMS 1582453

IMS 1758852

960102316 960153738

Some Boolean attributes with an input were not being updated, even though the attribute quality was good.

IMS 1583262

960113731

Performing an AppEngine Failover with an inhibited an alarm on a Boolean attribute resulted in Bad quality on the .InAlarm attribute after the failover.

IMS 1584848

960114953

When using Buffered on the I/O configuration, and TimeDeadband on the Alarm State configuration, the .InAlarm attribute remained false with bad quality when the TimeDeadband value was reached.

IMS 1589452

960110003

After migrating a galaxy from Wonderware System Platform 2014R2SP1 to System Platform 2020, restoring a galaxy load took much longer as compared to the earlier version of System Platform.

IMS 1606390

960112297

When a linked graphic was used instead of an embedded graphic, the error message "Graphic Not Found" sometimes appeared in the deployed OMI ViewApp.

IMS 1615151

960117896

After modifying a template and saving it, and then exporting the template and importing it into a galaxy, the IO auto assignment scan group overrides were corrupted.

IMS 1635321

960128754

The migration of a large galaxy (7 GB) from System Platform 2017U3 SP1 P01 to System Platform 2020R2 SP1 did not proceed beyond 75% complete.

IMS 1655279

IMS 1681712

960134839 960139298

In System Platform 2020R2P01, arrow keys did not work properly in the IDE Attribute Editor after a UserDefined object with several attributes was created.

IMS 1653421

960121522

The Bulk Import Utility tool failed to create a template when it was used to create a large number of attributes, some with string variables, on a System Platform 2020R2 object. If string variables were removed, the template was successfully completed.

IMS 1665444

IMS 1609008

960125486 960125486

If the GR node was disconnected, Application Server and Telemetry Server were not able to reestablish communication if either server was restarted.

IMS 1681712

IMS 1655279

960134839 960139298

In System Platform 2020R2SP1, arrow keys did not work properly in the IDE Attribute Editor for UserDefined template objects with many attributes.

IMS 1684156

960132917

After migrating a large galaxy with a large number of platforms from Wonderware System Platform 2014 to System Platform 2020, many of the platforms could not be deployed, and a number of PCS warnings were logged.

IMS 1685239

960139098

When Windows 10 nodes were deployed, an error was logged that the received Archestra user 'xxx' password from the GR node did not match to the local password. However, all Windows server nodes deploy correctly, without the error.

IMS 1721856

960141511

After migrating a galaxy from Wonderware System Platform 2014R2SP1 to System Platform 2020R2, checking in some object templates took much longer as compared to the earlier version of System Platform.

IMS 1731296

IMS 1755821

None

RPC and out of memory exceptions were noted when using GRAccess with System Platform 2020R2SP1.

IMS 1747806

960147791

Redundant AppEngine CPU consumption increased to full CPU load after running for two months without issues. Running at full load disrupted all communication and could only fixed by restarting both the primary and backup platforms.

IMS 1755467

IMS 1845293

960153778

An LMX Access Manager error occurred during when failing over an AppEngine and the DI Object did no failover.

IMS 1755821

IMS 1731296

None

When GRAccess Get APIs were used (GetChoicesGroup/GetChoices/GetOptions), all the inherited Choices and Options were hidden in the IDE at the instance level, instead of being visible.

IMS 1760199

960151444

An object that was configured with a bad reference was quarantined when it was deployed.

IMS 1768006

960156797

The last OMI ViewApp that was deployed did not run.

IMS 1774929

960150821

When objects that contained MyArea.Attribute or MyEngine.Attribute references were undeployed and moved to a different area, the references stopped working.

IMS 1779892

960146177

Due to a timing issue, the default object wizard settings were loaded instead of the wizard override settings.

IMS 1801033

960162666

Folder permissions were set properly when the Network Account was deleted, and then the Change Network Account utility was used to create a new account.

IMS 1801034

960150821

An exception was logged while restoring a dynamic attribute after failing over a redundant AppEngine.

IMS 1819008

960165954

A delay occurred on resolving faceplate symbol wizard related options when the redundant AppEngine failed over.

IMS 1819846

960151855

The generation of objects did not complete when GR Load was used to create instances.

IMS 1823142

960138723

When a galaxy that contained custom controls was migrated, the aaGR (galaxy repository) process stopped working before migration could finish.

IMS 1839413

IMS 1801342

960162695

Engineering Units were not passed from the template to a derived instance, if the template attribute was converted from a Field Attribute.

Issue Number

Related Issues

Case/SR Number

Description

IMS 1206363

960149654

In System Platform 2020R2, a ViewApp that contained an AutoSwitch script stopped working while opening and cycling through various assets and opening their graphics and the WWWebAppControls app.

IMS 1464013

960085476

The Trend pen did not plot data continuously if the data remained unchanged for seven days or the . When data was checked using the full retrieval option, the data contained null values.

IMS 1492033

960107119

Tooltips on multi-content panes were displayed inconsistently. The tool tip was not shown on the left navigation button while it did appear on the right button.

IMS 1492568

960106440

The width of a pop-up window in a ViewApp was made artificially large because OMI set the minimum width at 160 pixels.

IMS 1498809

960107167

When the property 'MyContent.NavTree.IsEnabled' was used in a script to disable the NavTree, an unhandled exception occurred and the ViewApp stopped working upon a mouseover event on the NavTree while it was disabled.

IMS 1514351

960103789

An error message continuously appeared in the SMC logger that the user was not authorized to access SharePoint and other resources.

IMS 1527962

960114596

In the OMI AlarmApp, the OK and Cancel buttons were truncated in the Shelve Comment dialog box.

IMS 1528078

960115051

A subsequent call to ShowGraphic() did not replace the layout that was being shown, even though the identity of the layout was the same.

IMS 1573397

960110629

When WorkTasks 2020 U1 was used with System Platform 2020, an OMI ViewApp using WWWebAppControls did not render an inbox popup correctly within a multi-content pane when the workflow form was set for full screen mode/maximized.

IMS 1579593

IMS 1735025

960116581 960149896

In a ViewApp that contained a popup with a slider animation, the cursor appearance was incorrect if the mouse button was held down on the slider and then moved out of the popup window.

IMS 1587360

960116556

Getting a value from an instrument via a RedundantDIObject connected with two legacy DI Network Devices resulted in a spurious attribute “AlarmCntsBySeverity[-1]” with bad quality shown for the RDI and DI Networks Device. This would also result in an ItemErrorCntAlarm.

IMS 1642710

960119370

With Windows security enabled, the "User must change password at next logon" function did not work in a ViewApp.

IMS 1652210

960116520

When a value was changed by an operator through a ViewApp, The "NodeName" column in the AlarmApp History displayed the value as "Remote Node." However, if the value was changed through the Object Viewer the node name was shown correctly in the AlarmApp history.

IMS 1726974

960133979

In a ViewApp with Historical Playback enabled, an OnShow script with Data Timeout configuration resulted in data delay at runtime for bad status references.

IMS 1734427

960149654

An OMI ViewApp crashed with index out of range exception while quickly switching between the assets.

IMS 1770801

960157038

After migrating a very large galaxy from System Platform 2020 to System Platform 2020R2SP1, alarm translation caused a delay in when using the ViewApp Preview feature.

Issue Number

Description

IMS 1869732

If the domain controller goes down and at the same time, an IDE user attempts to perform a change user operation, there is a slight possibility that Windows will display a crash dialog for the IDE. Note: This is a very rare scenario.

Workaround: Restart the IDE to proceed.

IMS 1861501

Endpoints on remote nodes, including redundant SSO nodes, are not discovered when the Global Discovery Server is not available. As a result, logging in to a Galaxy using Azure AD credentials when the security mode is Authentication Provider is not successful.

Workaround: For discovery of any endpoints that are not on the local node, then a GDS (global discovery) server MUST be available for discovery. You can configure a secondary GDS to avoid non-discovery, which can occur when the redundant SSO is on a different node. You can configure secondary discovery servers in the System Platform IDE. See the System Platform help for instructions on configuring multi-galaxy communication. You can also configure a secondary discovery server through the PCS Configuration utility.

1. Open the PCS Services Configuration utility
   C:\Program Files (x86)\Common Files\ArchestrA\Services\aaServiceConfiguration.exe
2. Open the Configure link (near the top of the utility window), the select Discovery Service from the menu.
3. Enter a secondary node name for both the Local and Cross solution.

   "Local solution" is equivalent to Local Galaxy server in the System Platform IDE, and "Cross solution" is equivalent to Multi-Galaxy server.

IMS 1846869

When System Platform is configured with a standalone System Management Server (SMS) and Authentication Provider, other nodes pointing to the SMS node may not be able to reach the Authentication Provider on the SMS node for user authentication.

Workaround: Use one of the recommended SMS system configurations described in the System Platform Installation Guide. Refer to the section "Recommended SMS Architecture Utilizing an Authentication Provider."

IMS 1842703

If, after configuring a node to connect to an existing System Management Server, you choose to make the node a redundant SSO server, the Configurator does not indicate that the Authentication Provider configuration parameters must be configured (green checkmark is still shown and the Configure button is grayed out).

Workaround: Select the Authentication Provider configuration option and configure the parameters as described in the System Platform Installation Guide.

IMS 1404918

If a network failure occurs on the active engine node and Warm Redundancy is enabled, the last value is shown as NULL for slow-changing Tags.

Workaround: Perform a SQL Insert or CSV Insert for the tag in question on the Historian side. This will restore the value in the Historian trend.

TFS 922856

The object name extension "_New" cannot be used if another object in the Galaxy uses the same name without the "_New" extension. For example, if you have an object named "Pump," you cannot have a second object named "Pump_New." You could, however, use "Pump_Old" and "Pump_New." Note that this restriction applies to templates as well as instances. For example, you cannot have a derived template named "$Area_New" or "$ViewApp_New" since these add the "_New" extension to a base template name.