Last revision: 6/28/2022
This Readme provides information about important resolved and known issues for AVEVA™ Application Server and the AVEVA™ Operations Management Interface (OMI), included with Application Server.
For information about new features, hardware and software requirements, product compatibility, installation and upgrades, and user documentation, see the AVEVA System Platform Readme, located in the root folder of the System Platform installation media.
Readme files from previous releases of Application Server are posted to the Product Hub section of the AVEVA Global Customer Support (GCS) website. You must log in to access the GCS Product Hub.
In addition to new features described in the System Platform 2023 ReadMe, Application Server 2023 fixes a number of customer reported issues. Note that the System Platform IDE has an updated GUI, and some workflows may have changed as a result.
The following tables describe the important resolved issues in Application Server 2023 and AVEVA OMI 2023. Some issues fixed in this release may have been inadvertently left out of these tables.
This table describes important resolved issues in Application Server. Some issues that have been fixed in this release may not be listed.
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. |
This table describes important resolved issues in AVEVA OMI. Some issues that have been fixed in this release may not be listed.
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. |
This section describes known issues that remain in Application Server 2023.
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.
|
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. |
© 2022 AVEVA Group plc and its subsidiaries. All rights reserved. | Contact Us |