Last revision: 12/19/2023
This document contains important information about AVEVA System Platform 2023 R2.
Program Name |
Version |
AVEVA Application Server 2023 R2, including AVEVA OMI |
23.1.000 |
AVEVA Communication Drivers Pack 2023 R2 |
23.02.000 |
AVEVA Enterprise License Manager 4.0.1 |
4.0.1 |
AVEVA Enterprise License Server 4.0.1 |
4.0.1 |
AVEVA Enterprise Licensing Platform 4.0.1 |
4.0.1 |
AVEVA Enterprise Licensing Platform(x86) 4.0.1 |
4.0.1 |
AVEVA Enterprise License Server Legacy Support 4.0.1 |
4.0.1 |
AVEVA Help |
23.1.000 |
AVEVA Historian 2023 R2 |
23.1.000 |
AVEVA Historian Client 2023 R2 |
23.1.000 |
AVEVA InTouch HMI 2023 R2 |
23.1.000 |
AVEVA InTouch Access Anywhere Server 2023 R2 |
23.1.000 |
AVEVA InTouch Access Anywhere Secure Gateway 2023 R2 |
23.1.000 |
AVEVA Platform Common Services 8.0.1 |
8.0.23345.1 |
System Monitor Agent Install Manager 1.5 |
1.5.0 |
System Monitor Manager 1.5 |
1.5.0 |
Operations Control Logger |
23.1.000 |
Operations Control Management Console |
23.1.000 |
System Platform 2023 R2 includes the following features, as well as miscellaneous bug and security fixes.
Operations Control and the Connected Experience
AVEVA Operations Control is an industrial software subscription to one or more of two packages that provides access across both on-premises and cloud applications. This flexibility provides multiple configuration, architecture, and deployment options that support your objectives and meet your requirements.
Adding connected experience to an Operations Control subscription provides the security of federated identity management for authentication and authorization, superseding the segmented approach of individual product security configurations. A per-user common identity is configured, authenticated, and managed through AVEVA Connect.
The Getting Started Guide describes AVEVA Operations Control and connected experience, how Operations Control differs from perpetual and flex license modes, and benefits of the Operations Control mode with connected experience. You can access it at: Welcome to AVEVA™ Operations Control (zoominsoftware.io)
Changes to the Default TCP port for Communication with Historian Server
The default TCP port for communication with Historian server has been changed to 32565. This is configurable and is used for data replication and communication with remote IDAS version 2023 R2 and later (which implies gRPC communication). The Classic Historian TCP port - 32568, for WCF communication, was used for data replication and remote IDAS communication with Historian versions 2023 and earlier, and remains for compatibility with previous versions.
Support for Import of SVG as an Industrial Graphic
The Industrial Graphic Editor supports import of Scalable Vector Graphics (SVG) as Industrial Graphics. You can perform the following:
Application Server 2023 R2 includes a number of new features, hot fixes, and provides support for the latest versions of Microsoft products. Refer to the GCS Technology Matrix for the list of supported Microsoft products.
Improved User Interface
The System Platform IDE has an improved user interface that provides object status at a glance.
New OMI Web Client
The web client for use with OMI ViewApps is completely new. The new client offers better performance, a look and feel more like the desktop client, and an easier way to make ViewApps available from a browser: you just assign them to an instance of the new WebViewEngine object type. The OMI web client is suppored with the latest versions of the Google Chrome and Microsoft Edge browsers.
OPC UA Scripting
You can now use Application Server object scripts and/or Industrial Graphics scripts to call OPC UA servers. Method calls are executed in the OPC UA server through the OPC UA client, are supported through the OPC client in the OI Gateway Communication Driver.
Alarm Latching and Alarm Dismiss
Latching is a new alarm state that can be enabled for a Galaxy. When latching is enabled, an acknowledged alarm that has returned to a normal value will continue to be displayed in the LATCHED alarm state. Alarms go to the LATCHED state if you ACK an alarm from UNACK_RTN state or return an alarm from ACK state. LATCHED alarms continue to be displayed to show that the alarms did occur. A dismiss command will return alarms that are in the LATCHED state to normal.
InTouch HMI 2023 R2 (Version 23.1.000) includes a number of new features, hot fixes, and provides support for the latest versions of Microsoft products. Refer to the GCS Technology Matrix for the list of supported Microsoft products.
Alarm Latching and Alarm Dismiss
If the Alarm latching feature is enabled, an acknowledged alarm that has returned to a normal value will continue to be displayed in the LATCHED alarm state. LATCHED alarms can be displayed in the current alarms mode to show that the alarms did occur. Alarms go to the LATCHED state when:
Or
To view the LATCHED state, enable the LATCHED state in the Alarms and events configuration screen of the IDE. You can dismiss the LATCHED alarms to remove the LATCHED alarms from the current mode of the Alarm Client Control grid. The dismissed LATCHED alarms would be visible in the recent mode of the Alarm Client Control.
Credential Manager
Use the Credential Manager utility to securely store and manage login credentials. You can retrieve the stored credentials (from AVEVA Application Manager for standalone applications, and from the Application Server for managed applications) for authenticating access to other components in WindowMaker, WindowViewer, and Alarm utilities.
By default, all named credentials are added to the Administrators group. In addition, we recommend you to add groups that the users running the application belong. This will allow the users to access the credentials even when running the application in a non-administrator mode, such as WindowViewer.
Changes to the Default TCP port for Communication with Historian Server
The default TCP port for communication with Historian server has been changed to 32565. This is configurable and is used for data replication and communication with remote IDAS version 2023 R2 and later. The Classic Historian TCP port - 32568, was used for data replication and remote IDAS communication with Historian versions 2023 and earlier, and remains for compatibility with previous versions.
OPC UA Enhancements
A new option External providers has now been added under Tag dictionary, that lists all the OPC UA server connections configured in the Gateway Communication Driver present on the same machine. Using this option, you can avoid several manual steps and create access names and InTouch tags for OPC UA item references easily. You can create the tags by just dragging and dropping from the External providers pane to the new Model – Tagname pane, that displays all the alarm groups and tags of the InTouch application.
Create Graphic Elements and Industrial Graphics using InTouch Tags
A Model – Tagname tab has been added in the Properties configuration pane of the Industrial Graphic Editor which displays all the tags available in the InTouch application. You can simply drag and drop the tags to the canvas to create graphic elements or Industrial Graphics. When creating multiple symbols at a time, the dot field property will be bounded automatically. This method simplifies the graphic development workflow and significantly reduces the application development time.
Embed an Industrial Graphic from the Toolbox Tab of Industrial Graphic Editor
You can embed an existing Industrial Graphic into current graphic using the Toolbox tab located in the Properties configuration pane of the Industrial Graphic Editor. The Toolbox tab displays all the Industrial Graphics available in the InTouch library. Once you have embedded the graphic, you can then edit it like any other component of the graphic.
Support for Import of SVG as an Industrial Graphic
The Industrial Graphic Editor supports import of Scalable Vector Graphics (SVG) as Industrial Graphics. You can perform the following:
Support for User Defined Types (UDTs) in InTouch
This feature supports the following:
Introducing the new Unified Identity
AVEVA Unified Identity enables Single Sign-On (SSO) for all Operations Control products on a given node with AVEVA Connect cloud capabilities. It supports common user authentication, authorization, and access entitlements across AVEVA Operations Control products. It includes:
The connected experience requires access to the AVEVA Connect cloud repository from each node where you want to use it.
Option to secure InTouch application folder
To restrict access to the applications folder for Standalone applications, a new check box has been introduced in Application Manager under Tools > Security. When the security feature is enabled on a node, strict read and write permissions are applied to the InTouch View Application.
Update default local working directory for NAD and Managed InTouch application
An option Enable local working directory integrity check for Managed and NAD InTouch Applications has been added in the Application Manager, under Tools > Node properties > Security. If this option is enabled,when launching WindowViewer for a Managed InTouch application andr NAD application, a file time stamp and file content hash comparison is performed between the deployed application and the application in the local working directory. If the files do not match, WindowViewer will copy the deployed application to the local working directory and run the application.
AVEVA Operations Control connected experience sign-on support
Historian supports the AVEVA Operations Control connected experience with AVEVA System Platform.
The server must be configured with an advanced license to retrieve data for expressions.
Note that the following still require Windows credentials:
Changes to default Historian communications protocol and ports
The Historian communications protocol has been updated. The port for the new protocol is 32565 by default. The previous port, 32568, is supported as a legacy port for connecting servers that are running older software that doesn’t support the new protocol.
Tier 1 Historians, AppEngines, and Platforms that support the new protocol and use the default 32568 port are updated automatically when the software is updated to the latest version. The local IDAS is also updated automatically. Existing connections that use legacy custom ports will need to be updated manually. External firewalls may need to be updated to allow connections on the new port.
Connecting servers that support the new protocol but are still using a custom legacy port will show as using the HCAL (Classic) protocol on the Data Acquisition page. (Note that connecting servers on older software will also use the HCAL (Classic) protocol. This is expected. Older software does not support the new protocol, and should still connect on the legacy port and use the classic protocol.)
If you have connecting servers that support the new protocol but still use the legacy port, the following warning appears once each hour in the Operations Control Logger:
The Historian Client Access Point running on XXX:XXX is an older version using a legacy protocol. Please update the port in the connection definition to point to the new Historian Client Access Point (port 32565 by default).
For more information, see the following sections in the Historian Administrator Guide:
Tags support multiple languages in Historian Client Web, Historian Client Query, and Historian Client Trend
You can now configure multiple translations for the same tag in Historian Client Web, Historian Client Query, and Historian Client Trend.
The language for these applications will be set automatically based on the operating system or browser language.
HTTPS-based communications
Internal Historian network communication is more secure and easily integrated with HTTP proxies.
Live data via iData
View latest historical values as the “live” values on OMI displays.
Alarm grid filter and sort in Historian Client Web
Browser-based alarm history in Historian Client Web supports more filtering and sorting options.
Historian Client Web / Excel integration
Easily transition from Historian Client Web charts to detailed analysis in Excel.
New look for Historian Client Web
The Historian Client Web interface is updated to be more powerful and easier to use.
Export / import Historian Client Web content
Include saved charts in CSV configuration import/export.
Ad-Hoc expressions in Trend
Historian Client Desktop Trend control and its embedded ActiveX controls now support Ad-Hoc expressions. The Expression application and pane now appear in the Tag Picker with the Textbox editor.
For embedded ActiveX controls, scripting is supported for ad-hoc expressions in InTouch applications.
Ad-hoc expressions are supported with both SQL and REST connections.
Expanded ad-hoc expression functions
New functions added to ad hoc expressions make results simpler and more valuable.
Runtime language switching
Runtime language switching is supported for Trend Control, Query Control, Embedded control, and the Excel and Word ActiveX controls. It's supported for the following fields:
If there is no value for the requested language for a field, the default language is used.
Improved Trend control for InTouch
Configuration is simplified for the Trend control within InTouch. The control is available in the graphic editor and can be placed in InTouch directly.
AVEVA Identity Manager Server login
Trend and Query support single sign-on authentication with AVEVA Identity Manager. This is restricted to REST-based connections and is not available for SQL-based connections.
Additional script functions for OMI Trend App and Graphic Editor support
The event tags TagAdded and TagRemoved have been added and are available at the Graphic level and in the HistoricalTrendApp control.
General performance improvements
Performance has been improved across the Historian Client controls.
Microsoft Office Historian Client Workbook improvements
The classic Historian Client Workbook add-in has been updated. Note the following:
Note: Make sure that you are not using the 64-bit version of Microsoft Office.
Tool for migrating from Historian Client Workbook to the newer Excel task pane add-in
The Excel Migration Tool updates Excel workbooks created in Historian Client Workbook to formulas compatible with the newer Historian Excel task pane add-in.
This tool is supported for files created in Excel 2016 or later.
For more details, see the Migrate data from Historian Client Workbook to the Excel add-in section in the AVEVA Historian Client User Guide.
OPC UA Methods Support
Client applications (such as Application Server) can call a method in an OPC UA server through the OPC UA client in the Gateway Communication Driver.
Related Topics
Supported System Platform Versions for Product Upgrade
Supported System Platform Versions for Migration
Security Changes Related to End-of-Life Third-Party Components
Name Changes to Graphics and Graphic Toolsets
Readme Files for Other Products in this Release
You can upgrade directly to System Platform 2023 R2 from System Platform 2017 or later, provided the prior version was installed on a 64-bit operating system.
Upgrades to System Platform 2023 R2 are NOT supported from the following System Platform versions:
Limitations
All existing, installed products on a node must be upgraded to the same version. Upgrading is defined as installing a newer version of the software when a previous version of the software exists. An upgrade is possible when the system requirements (operating system, SQL Server, .NET Framework) are met. The upgrade process will properly remove or uninstall the previous software version and install the new version. For versions older than the current and previous licensed versions, only the latest service pack or patch versions are tested. For distributed systems, some products must be upgraded in a particular order. For more information, see upgrade information for each product in the System Platform Installation Guide.
IMPORTANT! Back up any relevant application configuration files and databases before you start an upgrade or migration.
IMPORTANT! System Platform does not support mixed Windows workgroup/domain environments. Although workgroups are supported, domain-based networking is recommended. However, you cannot use workgroup nodes within a domain environment.
Operating System Compatibility
The earliest versions of Windows that support System Platform 2023 R2 are:
See the GCS Technology Matrix for complete information about operating systems that you can use with System Platform 2023 R2 products.
You can migrate user-created content (for example, .cab files, .aaPKG files, Historian databases, etc.) to System Platform 2023R2, as long as the content was created in one of the following product versions:
Security changes in System Platform 2023 and later include the removal of certain assemblies from Microsoft that have reached their end-of-life and are now out of support. These assemblies may pose a security risk and are no longer needed to support System Platform installation. The removed assemblies include:
System Platform components that may be affected: The flexibility of System Platform allows extensive customization, which could potentially involve these libraries. It is important to note that components that do not reference the removed libraries are not affected. System Platform components that may be affected include:
If you are upgrading an existing System Platform installation, the out-of-support libraries are retained if they are already present, ensuring ongoing functionality. However, clean installations of System Platform 2023 R2 will not include the libraries, and this could affect any imported/migrated applications that rely on them.
For ways to take remedial action to avoid any problems with components that may be affected by the removal of the out-of-support libraries, see the System Platform Installation Guide.
Important! Installation of out-of-support assemblies is NOT recommended.
AVEVA System Platform uses the server-based licensing subsystem introduced in System Platform 2017. This licensing subsystem provides centralized license management, and replaces the file-based licensing system that was used in prior releases. Licenses must be activated before use.
If you are upgrading from Wonderware System Platform 2014 R2 SP1 (with or without patches), you must first install and configure a license server node, and activate the licenses to ensure continuous plant operation. The license server is typically installed on the Galaxy Repository node, but you can use a dedicated license server. See the "License Installation and Activation" section of the System Platform Installation Guide.
Microsoft .NET Framework 4.8 or later is required for System Platform 2023 R2. When the System Platform installation process begins, it automatically checks the .NET version and installs the correct version if needed.
The Application Object Toolkit (AOT) is not included in the System Platform 2023 R2 release, but if you use AOT to build objects for Application Server, check that you have installed and configured the developer pack for .NET Framework 4.8 when you create your AOT solution in Visual Studio.
As of System Platform 2023, the System Platform IDE changes the names of some of the toolsets and graphics included in the Graphics Toolbox. The affected toolsets and graphics are in the path
_Default Content > 3. Graphics > Icon Library
The SE_Branding toolset is now simply Branding, SE_Domain_Pictograms is now Domain_Pictograms, and so on.
The new Icons toolset contains only one graphic named AVEVA_Logo. This graphic is new for System Platform 2023.
Existing galaxies that were created before System Platform 2023 will continue to contain the previous toolset and graphic names; you do not need to change any existing graphics or layouts that use any of these graphics under the SE_* or WW_* name.
New galaxies created after an upgrade to System Platform 2023 or 2023 R2 will contain only the new graphics.
Except for replacing the old WW_Logo graphics with AVEVA_Logo, this is a name change only. The graphics themselves have not changed.
To access individual product Readme files, insert the System Platform installation DVD and navigate to the applicable folder under the InstallFiles directory. Review the known and resolved issues contained in each Readme file for the component products updated for this release:
Product |
Location on Installation DVD |
Application Server |
InstallFiles/CD-ApplicationServer/UserDocs/English/Readme.html |
InTouch HMI |
|
Historian Server |
|
Historian Client |
|
InTouch Access Anywhere |
Before installing System Platform, download and install the latest Microsoft updates to enhance security and ensure product compatibility. Allow the Windows update process to finish before you start installing System Platform. This recommendation applies to all Windows versions.
Note that when Windows updates run in the background, there is the possibility that different software processes can be adversely affected. Therefore, it is important to schedule the updates to run only during planned shutdown periods.
Configuring Automatic Windows Updates
If Windows is configured to update automatically, these automatic updates, when running in the background, can disrupt System Platform components, including Application Server and OMI during installation/upgrade, configuration and run-time operations. These updates may cause the IDE, GR, OMI web client and related components, and other services to shutdown unexpectedly. Therefore, we recommend that you DISABLE automatic Windows updates, or otherwise ensure the updates will be installed only when System Platform applications are not being actively used.
For important information about this product release, go to the AVEVA Global Customer Support (GCS) website. Information on the GCS website includes product requirements and compatibility, as well as downloads from previous releases. After you log in, you can filter search results by product name and the release/version.
Web Help - Browser-based User Assistance
Web help opens in the default browser on your local computer. Help displayed in a browser allows more dynamic and searchable user assistance including standard web browser navigation and tutorial videos.
You can open help from within the System Platform IDE, InTouch WindowMaker, and other System Platform component products by pressing F1. You can also access the help system from the Windows start menu (located under the AVEVA folder). Or, you can simply enter AVEVA Help to locate and open the browser-based help library.
Supported Browsers
The AVEVA OMI Software Developer Kit (SDK) provides programmatic access to component APIs and namespaces. Using the methods and properties that these provide, you can build your own custom AVEVA OMI applications. Users can then add these custom apps to their ViewApps, the same way that they can add the AVEVA OMI apps that are included with Application Server.
When you install the System Platform IDE, the AVEVA OMI SDK is automatically installed, including samples and libraries. A link to the AVEVA OMI SDK Web Help is added to the Windows start menu. You can also open the OMI SDK Help via AVEVA Help, accessible from the Windows Start Menu, under AVEVA.
C:\Program Files (x86)\ArchestrA\Framework\AcfSdk
For detailed installation instructions in English, see the AVEVA System Platform Installation Guide (SP_Install_Guide.pdf). The Installation Guide pdf file is located in the root directory of the System Platform installation DVD.
Important! Installing System Platform on a computer used as a domain controller is not supported.
For more information, see the Microsoft Security Best Practices Checklist.
Some AVEVA products released prior to System Platform 2023 R2 must be installed BEFORE you install System Platform, if the product will be installed on the same node as System Platform. These are:
The Network User Account, previously called the ArchestrA User or AdminUser Account, is a user name and password combination that enables inter-node communication between computers in a System Platform environment. You must specify the same user account on every node when you install the System Platform components for the first time on computers that communicate with each other.
WARNING! The Network User Account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, System Platform software that uses the account may stop functioning properly.
After you install a System Platform component, you can use the Change Network Account utility to change or re-create the Network User Account. The AVEVA Start menu contains a shortcut to the utility.
You must have Administrator privileges to use the Change Network Account utility. For more information, see the Change Network Account utility help, available from within the utility.
Note: If you re-create the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the Galaxy node. Until that occurs, some System Platform components may not function properly. Restarting the Galaxy node updates this information immediately.
We highly recommend the following System Monitor installation and configuration sequence. For more information and details, please see “Configuring the System Monitor Agent" and "Configuring the System Monitor Manager” in the System Platform Installation Guide (SP_Install_Guide.pdf).
If you connect a machine to the System Management Server and then later replace the machine due to hardware failure, or restore the VM to a state prior to that connection without first disconnecting the machine from the System Management Server, you will not be able to reconnect that same machine to the System Management Server.
Cause:
To protect the security of the system, the System Management Server uniquely identifies each machine that connects to it. If an intruder attempts to pretend to be that machine (spoofing) and re-registers with that machine’s name, the System Management Server will detect the mismatched identity and reject the suspected intruder’s registration.
Solution:
After attempting to reconnect the machine, the logger will contain the warning:
“ArchestrA.CertificateManager: Please un-register the device <device name> from management server. Use the (Remove-AsbDevice) script to remove the device registration”
The PowerShell command will remove the machine’s connection information from the System Management Server. We recommend that you contact your support team, or AVEVA Global Customer Support (GCS), for assistance with executing this command.
Once installed, a link to the AVEVA Enterprise License Manager can be found in the \AVEVA folder on the Start menu.
It can also be accessed by pointing your browser to the following URL:
http://<nodename>/AELicenseManager
where <nodename> is localhost or the name of the node where the AVEVA Enterprise License Manager is installed.
The AVEVA Enterprise License Server can be installed separately from the AVEVA Enterprise License Manager.
In System Platform 2023 R2, running both InTouch HMI and AVEVA OMI in a session on an RDS Server will attempt to acquire two (2) Supervisory Client Server (unlimited) licenses instead of one (1).
If you have purchased a Supervisory Client Server license (unlimited RDP sessions on a single server) and then run both InTouch HMI and AVEVA OMI simultaneously, there can be issues acquiring the server license due to differences in how the license is handled between the two. The order of startup will impact the results.
This behavior is seen in only a limited number of instances, only when you have purchased a subscription license. If you do see this behavior, change the order of InTouch HMI and AVEVA OMI startup.
If this behavior continues, contact AVEVA Software Global Customer Support (GCS), describe the behavior, and request a temporary license, typically valid for 60-days.
License Reservation
Reserving a license for a specific device ensures a license will be available for that specific device whenever it is needed, regardless of the number of devices connected to the system. Keep in mind, each license can only be reserved to a single device, so if the device names are unknown ahead of time, it's better to not use reservations and instead allow the licenses to be acquired on a first-come, first-serve basis.
User-based License Reservation
In the AVEVA Enterprise License Manager license reservation page, it is possible to mark a license to be reserved to a specific user. While the reservation page allows this particular configuration, it's important to know that neither AVEVA OMI nor InTouch HMI ViewApps support user-based license reservations. The end-result will be the inability for the software to acquire the license reserved. Therefore, only use device-based reservations for Supervisory Client licenses.
Device-based License Reservation
When reserving a Supervisory Client license for a specific device, the Device Name needs to be the name of the computer running the InTouch HMI/AVEVA OMI ViewApp. In the case where the ViewApp is running inside of a Remote Desktop Session, on an RDS (aka: Terminal Server), then the Device Name needs to follow this naming pattern:
<RDSHostName>-<RDPClientName>-<index>
where RDSHostName is the name of the Remote Desktop Server (aka: RDS or Terminal Server), and RDPClientName is the name of the PC running the RDP client software, and "index" is 1, unless there will be multiple RDP sessions from a single client machine, in which case the index should be incremented (starting at 1) for each reservation for that specific RDP client, up to the total number of RDP sessions from that specific RDP client.
Reservation Examples
Situation: A computer with a hostname of "ControlRoomA" runs AVEVA OMI
Device Name: "ControlRoomA"
Situation: A computer with a hostname of "ControlRoomB" running a single Remote Desktop Client (RDP), connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"
Device Name: "PrimaryRDS-ControlRoomB-1"
Situation: Two computers with hostnames "SupervisorPC1" and "LineMgrA", respectively, each running a single Remote Desktop Client (RDP) connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"
Device Names:
Situation: A computer with a hostname of "ExecutiveDesktop" running four (4) Remote Desktop Clients (RDPs), connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"
Device Names:
Virtual Environments: License Servers are supported in virtual environments. However, under certain circumstances, such as transferring a license from one virtual environment to another, the License Server may interpret the transfer as an improper move and therefore go into grace period.
High Availability: License Servers in a High Availability virtual environment are supported in specific topologies. Basic redundancy topologies are described in the AVEVA Enterprise Licensing online help.
Disaster Recovery: License Servers in a Disaster Recovery virtual environment will go into a grace period during DR activities. This is because DR activities are similar to an improper move of licenses and will trigger a grace period.
To avoid a grace period trigger in a DR virtual environment, we recommend that you run the License Server outside the virtualized DR environment and use a redundant License Server configuration through the functionality built into the License Server software. Another option is to purchase Disaster Recovery licenses at a discounted rate and establish a backup License Server with these additional licenses.
In all environments, we recommend you install and run the AVEVA System Monitor to monitor licensing functionality and view alerts on issues such as a License Server going into grace period or licenses expiring.
Antivirus Software should be implemented as part of a defense-in-depth strategy to secure your Industrial Control Systems. TechNote TN2865, available from the AVEVA Global Customer Support (GCS) web site, lists important information about antivirus software. Enter your GCS credentials to access the TechNote.
https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn2865
The following important known issues are listed by their assigned reference number in ascending order. Additional known issues are documented in the product-specific Readme files.
PCS: Platform Common Services
MGC: Multi-Galaxy Communication
Issue Number |
Description |
IMS 1586624 |
The logger will repeatedly display error/exception messages from the "view" component if a multi-galaxy pairing is broken for any reason, and then an InTouch HMI Managed ViewApp is launched that contains cross-references to tags in another galaxy. Workaround: Since the exceptions are caused by the broken galaxy pairing, simply pair the galaxies again. The exceptions will no longer be logged. |
IMS 2829309 |
If you are using the connected experience for security and you close the browser window where you signed in when starting an OMI ViewApp, you may see one of these symptoms when signing out of the ViewApp: The sign out option may not appear; no users may show as signed in; if there are multiple connected users, you may be able to sign out as a different user; or you may see a message saying that sign out did not succeed even though it did. Workaround: Either have the System Administrator change the authentication browser option in the configurator (found under Common Platform > System Manager Server > Advanced > Authentication) to use the embedded browser pop-up dialog box, or keep the sign-in browser window open the entire time you are using the OMI ViewApp. Sign out then functions correctly. |
|
|
TFS 1263702 |
When upgrading from a node with Platform Common Services (PCS) 4.3.3 installed, such as the case when upgrading from System Platform 2017 Update 3 SP1 or installing on a node with RMP 2017 Update 2, errors are logged while deploying the OPCUA service. However, the service is deployed successfully. The errors are similar to the following: Application certificate does not have an application URI: CN=AZURE2019 Failed! UnifiedAutomation.UaBase.StatusException: Application certificate does not have an application URI: CN=AZURE2019 Workaround:
|
IMS 2658043 |
In an installation which uses workgroups and has MultiCast-DNS enabled, upgrading from an earlier version to PCS 8.0 (for example, during an upgrade to System Platform 2023R2) causes an issue with the PCS certificate. This causes secure communication with the SMS to fail. The SMS falls back to using non-secure communication. This causes error messages to be written continuously to the logger on all remote nodes. Workaround: Perform the following procedure on all nodes, including the SMS node:
|
Issue Number |
Description |
IMS 1578426 |
When attempting to establish a secure, encrypted SuiteLink connection, an error may be generated and the connection is terminated (by either the Client or Server). This condition will occur if the standard user has not been added as a member of the 'ArchestrAWebHosting' user group. Workaround: For a secure, encrypted communications over SuiteLink, add the standard user to the 'ArchestrAWebHosting' user group on the server side. For details, see the AVEVA Communication Drivers Pack Help, "Secure SuiteLink Connection," available after installation in the AVEVA Help application. |
IMS 1435622 TFS-1355437 |
If the Gateway Communication Driver (v4.0-v6.0) is installed on a machine and you try to upgrade to System Platform 2020 R2 SP1, then the Gateway Communication Driver gets uninstalled. Workaround: Use Modify install option in System Platform 2020 R2 SP1 and select Standards - Gateway to install on the machine. Note: If you install the Gateway Communication Driver using System Platform 2020, System Platform 2020 R2, or Wonderware System Platform 2017 U3 SP1 (along with InTouch and Application Server), then there is no issue in upgrading the Gateway Communication Driver using System Platform 2020 R2 SP1. |
Issue Number |
Description |
|
IMS 2967085 |
During an upgrade to System Platform 2023R2, you may receive an error message from the LicAPISvcProxy.NET service that starts: Failed to communicate with AVEVA Enterprise License Product Service. This is caused by an upgraded component trying to acquire a license before the Licensing service has started. Workaround: None needed. The error will resolve itself once the upgrade is complete and the node is rebooted. |
|
IMS 2917871 |
After an upgrade, the AVEVA Insight Supervisor service is not set to start automatically. Workaround: After the upgrade, open the Windows Services dialog box. In the list of services, right-click the AVEVA Insight Supervisor service. Select Properties and, on the General tab, set the Startup type to Automatic. |
|
IMS 2840477 |
When you run setup to upgrade from System Platform 2023 or other version to System Platform 2023 R2 and reach the "Ready to Upgrade the Application" form, but then select Back, setup may not navigate to the previous page. This happens because the previous page is a prerequisite check. Since all prerequisites have been satisfied, the setup program remains on the "Ready to Upgrade" form. Workaround: If you wish to return to a prior point in the upgrade process, press the Cancel button and restart the setup program. |
|
IMS 1958954 |
After upgrading from a prior version to System Platform 2023, Windows start menu icons from the prior version of System Platform may be displayed instead of the new System Platform icons. This may affect the icons for all System Platform products and components, including the Operations Control Management Console, Trend App, and InTouch HMI WindowMaker. This is an operating system cache issue that affects newer versions of Windows. There is no impact to the functionality of the products, and all new System Platform features will work as expected. Workaround: You can clear the Windows cache. Note that the cache is owned and managed by the Windows operating system. Therefore, we recommend that you contact Microsoft before using this procedure.
|
|
IMS 1925046 |
After installing or upgrading to System Platform 2023, and then completing configuration of the System Monitor Manager, icons and the UI title bar from the previous version of System Platform are shown for the Operations Control Management Console (OCMC), even if this is a new installation. This also occurs when installing OCMC Standalone and then installing any product that has an older version of OCMC (SMC). The icon in the title bar of the OCMC and the task bar icon revert to old icon. Workaround: Use Programs and Features in the Control Panel to repair the Operations Control Management Console. |
|
IMS 1758909 |
MDT AutoSave 5.01a is not supported on System Platform 2023 and System Platform Enterprise 2023. |
|
TFS 1249251 |
Upgrading to System Platform 2020 or later from a prior version does not succeed if the prior version used a 32-bit version of SQL Server. Support for 32-bit SQL Server was discontinued for the System Platform 2020 release. Workarounds: Two methods for upgrading System Platform and migrating galaxies are listed below. Use the first method if you will use SQL Server Express, included with System Platform. Use the second method if you will be installing a 64-bit full version of SQL Server in place of a 32-bit version. Method 1 (install SQL Server Express as part of System Platform installation):
Method 2 (install full version of SQL Server):
|
|
|
|
|
Issue Number |
Description |
IMS 1212168 |
On Windows 10 operating systems, layouts created in System Platform 2020 with non-English OS/regional settings show a warning and do not open when migrated to System Platform 2020 R2 or 2020 R2 SP1. Workaround: Before migrating the galaxy, make sure the operating system locale is set appropriately by following these steps:
|
TFS 1369154 |
Under certain circumstances, an instance derived from a template with an invalid reference will not show a warning during design time. This can occur if the following occurs: 1. A symbol is added to the Graphic Toolbox with an undefined relative reference, for example, “Me.Attribute001,” where Attribute001 has not been created yet. 2. The symbol is then added to a layout. 3. The layout is linked to a UDO (User Defined Object) template. When the template is saved, no warning is displayed. 4. When an asset is derived from the template, no warning is displayed for the instance either. Result: Although no warnings are issued during design time, when you create and then deploy a ViewApp with the linked layout, and show the linked layout in any screen, an error message will be displayed at run time (or in Preview Mode) that will allow you to troubleshoot and correct the error. The message will be similar to: Element ‘TEXT1’ in Symbol ‘UDO_001.S1’ has Configuration error: Invalid reference ‘Galaxy1:Me.Attribute001’ with owning object ‘UDO_001’ does not exist. |
TFS 1160616 |
If an admin user logs in, launches a ViewApp, and then logs off the system while leaving the ViewApp running, registry keys are unloaded in the profile of the user account. This results in continuous errors from CheckPointFileServer in the logger similar to: ""INVALID HRESULT LINE765 File CheckPointFile.cpp hResult 80003fa after logging off and logging on as different users (non-admin)." Cause: This is a known Microsoft issue. This problem typically occurs after an administrator uses a service account to log in to the server for an interactive session, and then logs off. For example, an administrator may log in to a Web Front End (WFE) server by using the farm account, and then log off. This activity forces the registry keys to be unloaded in the profile of that account, and makes the keys unavailable for future use. Microsoft recommends using either of the following workarounds to resolve this issue. For more information, see: "800703fa Illegal operation attempted on a registry key" error A COM+ application may stop working on Windows Server 2008 when the identity user logs off Workaround 1: Do not log in to the server for interactive sessions by using a service account. Workaround 2: Disable the related Windows User Profile Service feature as follows: 1. Open the Group Policy editor (Gpedit.msc) on the affected server. 2. Open the User Profiles folder in the following path: 3. Locate the "Do not forcefully unload the user registry at user logoff" setting. 4. Change the setting to Enabled. |
CR L00150114 |
SR59513303: TheGetCPTimeStamp() scripting method, when used in an AVEVA OMI action or named script within a symbol, does not return the timestamp at run time. Instead, it returns characters for the timestamp format, such as "mm/dd/yyyy hh:mm:ss." No errors or warnings will appear in the logger. This is similar to issue 777504, listed below. Workaround: Use the GetCPTimeStamp() method in an object script instead of a symbol script. |
Missing NavTree |
After upgrading or migrating an AVEVA OMI ViewApp from 2017, a warning message states that the NavTree entity could not be found. In 2017 Update 1, this navigation object has changed and is now called “NavTreeControl.” Workaround 1: To replace the NavTree object in a ViewApp or Layout when upgrading from System Platform 2017: 1. Open the ViewApp or Layout that shows the warning. 2. In the ViewApp or Layout editor, look in the Actions list for all references to “NavTree.” An icon showing “Content not available” will be displayed for these references. 3. To see the entire action list for a ViewApp, toggle the Actions for Primary switch to show Actions for Home (does not apply to the Layout editor). a. Replace the NavTree object with the new NavTreeControl. b. Search for NavTreeControl under the Toolbox tab. 4. Drag the NavTreeControl onto the pane to replace the NavTree. 5. Confirm that you want to replace the content, then save the ViewApp or Layout and close the editor. 6. Verify Layouts and ViewApps no longer show any warnings related to the NavTree. 7. Deploy the ViewApp. Workaround 2: To replace references to NavTree when importing packages from System Platform 2017:
|
TFS 774717 |
When an AVEVA OMI application (View.exe) that uses one of the following web controls is run in 4K mode or on multiple 1080p monitors, under certain circumstances the application may stop responding:
Workaround: When running a ViewApp that uses a web control on a 4K monitor, set the monitor resolution to 2560 x1440 or less. When running the ViewApp on 1080p monitors, do not attempt to span multiple monitors. |
TFS 777504 |
The GetCPQuality() scripting method is not supported in AVEVA OMI. If used in a ViewApp, it always returns quality = 0 (bad quality). This is similar to issue L00150114, listed above. |
TFS 781006 |
If an invalid custom property is added to a symbol, no warning is logged in the Operations Control Management Console, even though no value is displayed for the custom property. |
TFS 781620 |
The Height and Width properties of a group with text elements do not change in accordance with changes made to the label font size, and are not rendered correctly. |
TFS 784470 |
Tooltip animations that contain multiple lines of text with line breaks may not display properly in deployed ViewApp. |
TFS 784474 |
A tooltip may partially cover the element with which it is associated in the deployed ViewApp. |
TFS 787192 |
When OSGroup security mode is used, the VerifiedWrite dialog is not displayed when you modify the value of a VerifiedWrite attribute from a combobox, if you first attempted to perform the VerifiedWrite without having the correct security credentials. |
TFS 789958 |
On some high resolution tablet devices, such as the Surface Pro 4, object names in the System Platform IDE may have insufficient line spacing between items, which can make it harder to read object names. |
TFS 794383 |
When a custom property is changed from public to private, the change does not have any affect, and the value of the private custom property is shown at run time (private values should not be shown). Similar situations occur when:
Workaround: Manually validate the outermost symbol and then deploy the ViewApp. |
IMS-1989484 |
After galaxy migration, if a linked symbol information is unavailable, the layout validator cannot process the linked symbol. This can result in the layout in warning state. Immediately connecting to the galaxy will display a warning state and empty symbol preview for the specific unprocessed linked symbol. Workaround: After the migration completes, connect to the galaxy and open the layout in warning state. Identify the symbols showing empty previews, validate those symbols only, then validate the layout to resolve the issue. You do not need to validate all symbols, only those symbols with missing previews in the layout. |
IMS-1989662 |
Some alarm field localizations might not appear in the Alarm Control in InTouch HMI and AVEVA OMI when running in Historical Alarms and Events client mode. When running the Alarm Control, either as an embedded symbol in InTouch HMI or in AVEVA OMI, or as an AlarmApp in AVEVA OMI configured to run in Historical Alarms, Historical Events, or Historical Alarms and Events modes, some alarm field localizations may not load even if present in the galaxy translation files. This occurs when the control is configured to display alarms from the History Blocks database. Following are the known cases (Alarm/Event types) where the localizations fail to load at runtime: 1. For user write operations (User.Write) and events, the AlarmComment field is only partially localized in an Alarm App configured to view Historical Alarms and Events. 2. For a Boolean alarm (Alarm.Set, Alarm.Clear) events, the AlarmComment, Limit and Value field localizations are not displayed in an Alarm App configured to view Historical Alarms and Events,. 3. For Boolean write operations from an I/O reference (Application.Write) events, the AlarmComment and Value field localizations are not displayed in an Alarm App configured to view Historical Alarms and Events. |
IMS-1991749 |
After installing and configuring System Platform 2023 or rebooting the system, the following message will be logged in the Operations Control Logger, "AnnounceOnline could not announce to local discovery service due to communication error," when the InTouchIDataService is unable to connect to the Discovery Service. This can occur if the InTouchIDataService starts before the Local Discovery Service. This message will not be logged after the Discovery Service starts. There is no functional loss once all services have started. |
IMS 2918856 |
In some cases, in the OMI web client, the Trend Pen graphic element and the HistoricalTrendApp OMI ViewApp cannot retrieve historical data. There are two reasons for this:
Perform workaround 1 to correct the first issue. For the second issue, perform one of the two procedures in workaround 2. Workaround 1: Update the application settings file for the WebViewEngine:
|
|
Workaround 2: To fix the security certificate issue, you have two choices.
Decide on the method you wish to use and follow the appropriate procedure below. You need to follow only one of these procedures. To install the certificate on a Windows node or remote device: Note: Depending on your organization's network configuration, your IT department may be able to install the certificate on all devices remotely. Users would not then need to perform this procedure.
Note: For remote devices which use an operating system other than Windows, see the manufacturer's instructions for installing a certificate. To change the certificate on the Historian Server node:
|
IMS 2968494 |
Basic translation is supported for trend controls using an SQL connection. This translates the descriptions of tags as well as the user interface of the trend control. However, you can more fully use the translation capabilities to the trend control by connecting to the Historian using the REST oData interface. Using the REST oData interface expands the translation capabilities to include the translation of descriptions, engineering units and Boolean on/off messages. |
|
|
Issue Number |
Description |
IMS 2003461 |
In the Industrial Graphic Editor, the largest allowable X and Y co-ordinates for a graphic element are 4096. You cannot position the top-left corner of a graphic element--such as a rectangle, an Industrial Graphic, or an image--beyond that location. However, you can define graphic elements that extend to the right of or lower than this limit. These elements may extend past the visible part of the Graphic Editor canvas, but will still appear correctly if you place the graphic in a layout pane. You also cannot enter a value higher than 4096 for the width or height of a graphic element. As a workaround, you can exceed this limit by selecting the element and using the sizing handles to expand it to the size you want. |
The following known issues are in addition to those documented in the InTouch HMI Readme.
Issue Number |
Description |
- |
On a fresh installation of System Platform 2023, you may notice the following issues related to Secure Suitelink Connection:
Workaround: To ensure connectivity between the Suitelink client and the WindowViewer:
For more information, see Configuring a Secure Suitelink Communication in the AVEVA InTouch HMI Help. |
1928318 |
When the Supertag instances are created by importing from a .CSV file, the imported Supertags are not displayed in the Supertags pane of the WindowMaker. Workaround: The Supertag instances created by importing from a .CSV file can be viewed in the tag dictionary. |
IMS 1488851 |
Post-upgrade from InTouch HMI 2017 U3 SP1 to InTouch HMI 2020 R2 SP1, the following warning message is logged in the LogViewer: “Unable to start the aaServiceHost Could not load file or assembly 'PCS.Client.Discovery, Version=1.3.1.0, Culture=neutral, PublicKeyToken=23106a86e706d0ae' or one of its dependencies. The system cannot find the file specified.” This has no functional impact. However, restarting the system will resolve the message. |
IMS 2886663 |
After you upgrade PCS from 7.0.1 to 8.0, InTouchDataService continually writes warning messages to the logger. These messages occur, on average, about every 30 seconds. There is no loss of functionality from this issue. Other than generating the warning message, InTouchDataService continues to operate normally. |
IMS 2917871 |
After an upgrade, if InTouch and Historian are installed on the same node, InTouch ViewApps published to AVEVA Insight may not show tag data. This is because an XML configuration file for the ViewApp is inadvertently deleted during Historian configuration. Workaround: Republish each affected InTouch ViewApp. |
IMS 2968494 |
Basic translation is supported for trend controls using an SQL connection. This translates the descriptions of tags as well as the user interface of the trend control. However, you can more fully use the translation capabilities for the trend control by connecting to the Historian using the REST oData interface. Using the REST oData interface expands the translation capabilities to include the translation of descriptions, engineering units and Boolean on/off messages. |
The following known issue is in addition to those documented in the InTouch Access Anywhere Readme.
Issue Number |
Description |
TFS 1280717 |
InTouch Access Anywhere cannot be removed through the Modify workflow. An error message is displayed that states, "To install this product, please run Setup.exe. The setup will now exit." Workaround: Select the Remove workflow, instead of Modify, from the Maintenance dialog. This successfully deletes InTouch Access Anywhere and its components. |
Issue Number |
Description |
TFS 1300491 |
Activating OI Gateway consumes a license even though OI Gateway does not require a license unless the MQTT component has been configured and is in use. Workaround: Reserve a license for each Communication Driver (OI Server) that requires a license. No licenses will then be available because they are reserved to other Communication Drivers. When OI Gateway is activated but not using MQTT, no license will be consumed by OI Gateway. OI Gateway will run without interruption. |
TFS 1241116 |
MES 2017/2017 R2 may not acquire a trial license when installed with System Platform 2020. This is due to a file path name change for the TrialLicensePool that is part of the System Platform 2020 release. This issue only occurs if you are using a trial license. For both MES 2017 and MES 2017 R2, the file path for the TrialLicensePool folder is: For System Platform 2020, the file path for the TrialLicensePool folder is: Workarounds: Use one of the following workarounds.
|
TFS 793643 |
If you have not set a default browser, and you install System Platform with AVEVA Enterprise licensing selected, clicking the AVEVA Enterprise License Manager shortcut does not open the License Manager in the browser as it should. Instead, the shortcut opens in Windows Explorer. From Windows Explorer, you cannot open License Manager (the OK button is inactive). Workaround: Follow the instructions for your operating system to set the default browser, and then open the AVEVA Enterprise License Manager from the shortcut, or: Open your browser and copy the shortcut link, http://localhost/AELicenseManager, directly into the browser's address bar. |
TFS 779958 |
When the same license is acquired on both a local node and in an RDP session that originates from the same node, the License Manager may not show all the licenses that have been acquired. This occurs even though the licenses are counted properly on the license server. The license count that you see applies only to the node you are viewing. Thus, once you reach your maximum number of licenses, you will not be able to acquire additional licenses, even though the license manager may indicate that more licenses are available. |
The following known issues are in addition to those documented in the AVEVA System Monitor Readme.
Issue Number |
Description |
1436013 |
Email alerts cannot be sent through secured SMTP. |
1511692 |
Post Install -> Reboot, ASM has an alert that Bootstrap is not running that does not update to show Bootstrap IS running. Workaround: Resolve the Bootstrap alert. It will not shows the incorrect status again. |
If you create a filter for a history block query that results in no matches, "Not Connected" appears in the status bar and a warning is logged in the Logger. The status bar should show "Connected" even though no matches are returned.
AVEVA Edge is not a component product of System Platform, but is sometimes installed with it.
Issue Number |
Description |
TFS 1342283 |
If you attempt to upgrade a computer to System Platform 2020 R2 from System Platform 2020, and AVEVA Edge 2020 is installed on the same computer, an error message may be displayed that warns of an incompatibility. This will occur during the upgrade if certain registry values are incorrect, and the upgrade installation will be blocked. Workaround: Use regedit to enter the correct registry values. Location: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ArchestrA\Framework
|
Most System Platform help documents are provided as PDF and web help documents.
|
© 2015-2023 AVEVA Group Limited and its subsidiaries. All rights reserved. | Contact Us |