Last revision: 7/28/2022
This document contains important information about AVEVA System Platform 2023 and AVEVA System Platform Enterprise 2023.
AVEVA System Platform Enterprise builds upon the core technology of AVEVA System Platform to bring enhanced user accessibility and exclusive visualization extensions, specifically for enterprise users in assembling an AVEVA Unified Operations Center solution. This includes the AVEVA Operations Management Interface (OMI) Web Client, allowing applications to be viewed in a standard web browser. AVEVA System Platform Enterprise is an AVEVA Flex subscription activated product.
Important: 32-bit operating systems and 32-bit SQL Server versions are no longer supported. This version of System Platform is only compatible with 64-bit operating systems and SQL Server versions. If you have a 32-bit version of SQL Server, you must uninstall it before installing System Platform. System Platform will check that an installed SQL version is compatible prior to installation, and will display an error message if the installed SQL Server version is not compatible for any reason (not only for 32-bit versions). For information about moving from 32-bit to 64-bit SQL Server, refer to Issue 1249251 under Installation, Upgrade and Galaxy Migration Issues. For general information about SQL Server requirements, see SQL Server Notes.
Program Name |
Version |
AVEVA Application Server 2023 including AVEVA OMI |
23.0.000 |
AVEVA Communication Drivers Pack 2023 |
7.4.000 |
AVEVA Enterprise License Manager |
3.7.002 |
AVEVA Enterprise License Server |
3.7.002 |
AVEVA Enterprise Licensing Platform |
3.7.002 |
AVEVA Help |
1.0.0 |
AVEVA Historian 2023 |
23.0.000 |
AVEVA Historian Client 2023 |
23.0.000 |
AVEVA InTouch HMI 2023 |
23.0.000 |
AVEVA InTouch Access Anywhere Server 2023 |
23.0.000 |
AVEVA InTouch Access Anywhere Secure Gateway 2023 |
23.0.000 |
AVEVA Platform Common Services 7.0 |
7.0.22195.1 |
Insight Publisher |
4.4.000 |
System Monitor Agent Install Manager 1.4 |
1.4.0 |
System Monitor Manager 1.4 |
1.4.0 |
System Platform 2023 includes the following features, as well as miscellaneous bug and security fixes.
Refreshed user interface
The design environments for Application Server, AVEVA OMI, and InTouch HMI now have a new look and improved user interface. Menus and icons have been redesigned for a better user experience. Some of the key highlights include new backstages and menu organization. This updated interface provides more efficient workflows and a common look and feel across AVEVA’s operations control software.
Integrated Web Help System
System Platform 2023 now includes an integrated Web Help system that uses your default browser to display both general and contextual help.
System Platform Enterprise 2023
System Platform Enterprise is intended for customers who subscribe to AVEVA Operations Control Enterprise. It features capabilities that are specific to the implementation of Unified Operation Centers (UOC). Exclusive features of System Platform Enterprise include:
System Platform Enterprise does NOT include:
Application Server 2023 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.
New look for Application Server
The System Platform IDE, the design environment for Application Server, now has a new look and improved user interface. Menus and icons have been redesigned for a better user experience. Some of the key highlights of the System Platform IDE user interface include a new backstage, menu items, and groups. All special operations that you need to access frequently are now in the backstage, on the Galaxy menu. Other commands have been regrouped in different menu items based on their functionality and ease of accessibility.
User authentication and single sign-on via Azure Active Directory
Azure Active Directory (AD) can be used for identity authentication and single sign-on. After setting Galaxy security to use an external identity provider, Azure AD can be used to authenticate users. System Platform users can then use their Microsoft-managed identities to log in to the System Platform IDE, Operations Control Management Console, AVEVA OMI ViewApps, and to perform secured and verified writes.
Integrated web help system
Help for Application Server is now available as web help, and can be viewed and searched in your default browser. Help for other System Platform products has also been migrated to web help, allowing you to more easily view and search across all System Platform products.
Alarm translation enhancements
You can now localize alarm and event message, and alarm groups.
Preview a ViewApp
System Platform includes the capability for developers to preview an OMI ViewApp from the ViewApp editor without deploying any associated assets. After selecting the Preview Web button, the ViewApp appears in the Web Client.
Object wizard performance
The time needed to propagate changes has been significantly improved, thus greatly increasing performance during development.
Symbol wizard integration
Symbol Wizard support has been improved in web graphics that appear in OMI web ViewApps. In the case of SAL symbols, Wizard Options are supported to provide different configurations of the same symbol.
Display a web ViewApp on a mobile device
The AVEVA Mobile Operations application has been updated to show OMI web ViewApps on a mobile device.
Enhanced management of cloud graphics
AVEVA Connect users are prevented from accessing or overwriting any cloud graphics that were created with a higher version of the Graphic Editor than their local editor. Since multiple AVEVA products use the Industrial Graphic Editor, this allows organizations to use these different products, which may incorporate different versions of the editor, while avoiding any issues that may result from attempting to edit a graphic with new extensions that do not exist in their local version of the editor.
Embed web widgets within OMI Industrial Graphics
Place one or more web widgets directly in an Industrial Graphic for use in the OMI desktop as well as the OMI web client.
GRAccess as an API
The GRAccess Toolkit is now delivered as an API with System Platform to allow users to programmatically interact with Application Server.
Security identity event logging
Log-on and log-off events, both successful and unsuccessful, are tracked for security and audit purposes.
Updates for historical playback capability
Source non-historized values during historical playback to avoid missing information. These values can optionally be flagged to make the viewer aware of the alternative data source.
New BigString data type
The BigString data type supports a virtually unlimited string size to allow users to store and transmit huge strings.
Dynamic images in Industrial graphics
A new property, ImageURI, has been added to Industrial Graphics. This allows the user to modify the property at runtime to dynamically change the image.
AVEVA Flex subscription enhancements
Multiple Flex single engine licenses can now by assigned to a single platform.
Workspace feature for the AVEVA Operations Management Interface Web Client
Use the Workspace feature to create customizable dashboards for casual users across the enterprise. Workspace displays all graphics available in the Workspaces toolset of Graphic Toolbox in the selected application. This allows viewing an Industrial Graphic with operations data by binding attributes from AVEVA System Platform Enterprise. You can create, modify, and save your dashboards, and even share them with others.
To access Workspace, you must:
Note:
- The AVEVA Historian search and elastic search features are installed to support the Workspace feature for the OMI Web Client. Workspace is available if you are using Flex licensing. Therefore, after installation, you may see AVEVA Historian listed as a Windows program, even if you did not install the Historian. Do not uninstall Historian. You can use the Modify workflow to restore the Historian search and elastic search features if you inadvertently uninstalled Historian.
- In this initial release of Workspace, searching for Application Server attributes is not supported when using Workspace on a remote node. Searching for Application Server attributes is only supported on the GR or Galaxy Repository node. This feature will be supported in future releases.
For more information, see Widgets, Apps, and Controls in the AVEVA Help.
Cybersecurity enhancements
Application Server and AVEVA OMI incorporate ongoing cybersecurity enhancements and hardening.
Extensions
InTouch HMI 2023 (Version 23.0.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.
New Look of InTouch HMI
InTouch HMI 2023 now has a new look. The product and icons have been redesigned for a simpler and enhanced user experience. The new user interface complies with the fluid design and adheres with the AVEVA Design System. Some of the key highlights of the new InTouch HMI 2023 user interface are:
Longer tag names and item names
The tagname length has been extended from 32 to 128 characters. Item name length has been extended from 79 to 254 characters.
Unlimited Tag Count Support
The InTouch license now supports unlimited tag count. This means that the run-time database can theoretically store unlimited tagcount license, which includes both local tags and tags that reference a remote tag source. However, we have tested up to 300,000 tag handles (300K) only. For more information, see the section Licensing in InTouch HMI in the InTouch HMI Help.
Cloud Graphic Versioning Support
The AVEVA Drive graphics supports Industrial Graphics, Client Controls, and Widgets in the Cloud, published from different products with different versions of the graphic subsystems. For more information, see the section Working with Industrial Graphics in AVEVA Connect in the InTouch HMI Help.
Map App Web Widget
You can use the Map App Web Widget to incorporate a zoomable map into InTouch HMI applications and display selected graphics in a geographical context. It supports a number of popular map providers, and is perfect for geographically distributed applications. You can integrate Supertags with MapApp widget to display it in WindowViewer or Web Client. For more information, see the section Using MapApp Widget with Supertags in the InTouch HMI Help.
Supertags
Supertags is now more easily accessible from the Windows panel. It also has an improved workflow, making it easier to manage members, instances, and attributes.
Improved Search in WindowMaker
The improved search functionality in WindowMaker allows you to search with a keyword simultaneously within the windows, scripts, tags, and symbols.
Bit State Animations
Bit State animations allow you to add conditions to an animation based on bit values. You can add multiple conditions and for each condition you can select individual bits in any pattern up to 32 bits.
Extended Truth Table Animations
The Blink, Disable, Value Display and Visibility animations have now been extended with the ability to configure animations with truth table conditions.
New Graphic Element - Multi Pens Trend
Introducing a new graphic element – Multi Pens Trend. A Multi Pens Trend is like a trend pen and displays a succession of process values but with multiple trend lines.
Ramp option with the Pushbutton Animation
Within the Pushbutton animation you can choose to apply a percentage ramp to the Increment, Decrement, Multiply and Divide actions.
Support for Momentary Touch
The Momentary Contact action is now available for the Pushbutton Boolean animation, allowing you to configure a time-period to hold the set value.
Option to Reset Industrial Graphic Option Cached Values
You can now choose to reset the Industrial Graphic cached values and windows properties when the window is closed and reopened.
Improved Association of Tag Reference with Graphic Element text
There is an improved association of the the tag reference with the text displayed for the Graphic Element.
Enhanced Language Switching at Runtime
The InTouch HMI application and the Alarm Client Control supports runtime language switching of alarm group names, and event and status bar messages.
Secure SuiteLink Configuration
As of System Platform 2023, the SuiteLink connection is by default set to secure with TLS encryption. If you want to enable the fallback mode to accept the unsecure connection, you have to make the configuration changes in the System Management Server. You can verify the mode of the SuiteLink connection, whether secure or unsecure, by checking the WWSLS component in the Log Viewer.
If unsecure fall back mode is not enabled and secure connection requirements are not met, then SuiteLink connection will fail. For more information, see Configuring Secure Suitelink as a Standard User in the AVEVA InTouch HMI Help.
Workspace Feature for the AVEVA InTouch HMI Web Client
Use the Workspace feature from the InTouch HMI Web Client for operators to create customizable dashboards dynamically. Workspace displays all graphics available in the Workspaces toolset of Graphic Toolbox in the selected application. This allows viewing an Industrial Graphic with runtime data by binding custom properties to tags from InTouch HMI. You can create, modify, and save your dashboards, and even share them with others on the team.
To access Workspace, you must:
Note:
- The AVEVA Historian search and elastic search features are installed to support the Workspace feature for the InTouch HMI Web Client. Workspace is available if you are using Flex licensing. Therefore, after installation, you may see AVEVA Historian listed as a Windows program, even if you did not install the Historian. Do not uninstall Historian. You can use the Modify workflow to restore the Historian search and elastic search features if you inadvertently uninstalled Historian.
- In this initial release of Workspace, searching for Application Server attributes is not supported when using Workspace on a remote node. Searching for Application Server attributes is only supported on the GR or Galaxy Repository node. This feature will be supported in future releases.
For more information, see Workspace in the AVEVA InTouch HMI Help, ITWebBrowser.pdf, and Widgets, Apps, and Controls Help.
Cybersecurity Enhancement
This version of InTouch HMI incorporates several cybersecurity enhancements.
X-Frame-Options Authentication Settings for Web Client
The Web Client now supports the X-Frame-Options HTTP response header. This can be used to indicate whether or not a browser should be allowed to render a page in a <frame>, <iframe>, <embed> or <object>. An XFrameOptions property has been added to the appsettings.json files under InTouchWeb\Server and InTouchWeb\Content.
The value of XFrameOptions in the appsettings.json file is blank by default. To ensure that the Web Client page can only be displayed in a frame on the same origin as the page itself, you must set the values of XFrameOptions as ‘SAMEORIGIN’. The value is not case sensitive. A shared Web Client may not load if the value of XFrameOptions is set to SAMEORIGIN.
If you specify the value of XFrameOptions as blank, the X-Frame-Options response header will not be added.
The AVEVA Historian 2023 release includes these features:
Ad hoc expressions in Historian Client Web and SQL queries
Replication to AVEVA PI and AVEVA Data Hub
Secure web access (HTTPS) that is easy to configure and use
Enhanced Excel add-in
Easily backfill to any replication server up to 10x faster (not just auto-summary)
Remote IDAS
Operations Control Management Console (formerly "System Management Console" or "SMC")
Modernized Interface
Hosted Help Integration
Miscellaneous
The AVEVA Historian Client 2023 release includes these features:
Modernized Interface
Option for auto-scale to always automatically update in Trend
Configurable color for cursor difference color in Trend
Simplified queries and improved alarm queries in Query
Enterprise license support
Hosted Help Integration
Miscellaneous
Revised Standard User Privileges and Options
A Standard User will now have only read rights. However, the Standard User will have an option to get the additional user privileges for a specific time interval by providing the OI Administrator user credentials. For more information on standard user privileges and getting Administrator Privileges, refer to "Accessing OCMC as a Standard User" in the Communication Drivers Pack Help.
Microsoft Edge for Auto-Build
Auto-Build now requires the Microsoft Edge browser.
MQTT
Buffered Data
Communication Drivers Pack supports buffered data up to 10K values/tag.
SuiteLink Fallback
Starting with this release, the fallback mode is set to secure (V3) by default, and the fallback mode to accept unsecure (V2) connections is disabled.
OPC UA Reverse Connect
The OPC UA Reverse Connect feature enables the OPC UA server to initiate a connection with the Gateway Communication Driver. In a secure environment, inbound connections to the OPC UA server are restricted as the server operates behind a firewall. By using Reverse Connect, the firewall restriction is alleviated as the connection is being made from the OPC UA server to the client.
New Security Policy Options
OPC UA now supports two new security policies: Aes128_Sha256_RsaOaep and Aes256_Sha256_RsaPss. Basic125Rsa15 and Basic256 are deprecated and supported only for compatibility reasons. For more information, refer to the Gateway Communication Driver Help.
Improved Server Browsing
You can now browse and select available endpoints of the OPC UA server and its supported security policy.
OpenSSL 1.1.1n Support
Gateway Communication Driver now uses OpenSSL 1.1.1n for MQTT, SuiteLink, and OPCUA for secure communication.
The following tables list the System Platform and System Platform Enterprise components available for installation. Most components are common to both, while some widgets, apps, and other components are available for installation to only one.
AVEVA System Platform - Development Components |
System Platform |
SP Enterprise |
|---|---|---|
System Platform IDE |
Yes |
Yes |
Application Server Galaxy Repository |
Yes |
Yes |
AVEVA System Platform - Run-Time Services |
System Platform |
SP Enterprise |
Application Server Run Time Platform |
Yes |
Yes |
AVEVA Operations Management Interface |
System Platform |
SP Enterprise |
OMI ViewApp Run Time (Desktop and RDP/InTouch Access Anywhere) |
Yes |
Yes |
OMI Web Server (Intranet) |
No |
Yes |
OMI Workspaces |
No |
Yes |
AVEVA OMI Desktop Apps |
System Platform |
SP Enterprise |
OMI Content Presenter App |
Yes |
Yes |
OMI Map App |
Yes |
Yes |
All OMI Apps included with System Platform 2020 R2 SP1 |
Yes |
Yes |
OMI Power BI App |
No |
Yes |
OMI PI Vision App |
No |
Yes |
OMI Sankey App |
No |
Yes |
AVEVA OMI Web Widgets |
System Platform |
SP Enterprise |
Grid View Widget |
Yes |
Yes |
Carousel Widget |
Yes |
Yes |
QRCode Scanner Widget |
Yes |
Yes |
Web Browser Widget |
Yes |
Yes |
Teamwork Widget |
Yes |
Yes |
OMI ScatterChart Widget |
No |
Yes |
OMI Breadcrumb Widget |
No |
Yes |
OMI Graphic Repeater Widget |
No |
Yes |
OMI Hamburger Widget |
No |
Yes |
OMI Map App Widget |
No |
Yes |
OMI Navigation Tree Widget |
No |
Yes |
OMI Title Bar Widget |
No |
Yes |
AVEVA InTouch HMI Components |
System Platform |
SP Enterprise |
|---|---|---|
InTouch WindowMaker |
Yes |
No |
InTouch WindowViewer |
Yes |
No |
InTouch Web Server (Web Client) |
Yes |
No |
InTouch Workspaces |
Yes |
No |
AVEVA InTouch Access Anywhere |
System Platform |
SP Enterprise |
InTouch Access Anywhere Server |
Yes |
Yes |
InTouch Access Anywhere Secure Gateway |
Yes |
Yes |
AVEVA Historian |
System Platform |
SP Enterprise |
|---|---|---|
Historian Server (Desktop/Server) |
Yes |
Yes |
Historian Client Web (Insight Local) |
Yes |
Yes |
Historian Client Desktop |
Yes |
Yes |
Insight Publisher |
Yes |
Yes |
AVEVA Common Services |
System Platform |
SP Enterprise |
|---|---|---|
Communication Driver Pack |
Yes |
Yes |
Common Services Framework |
Yes |
Yes |
AVEVA Enterprise Licensing |
Yes |
Yes |
System Monitor |
Yes |
Yes |
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
Start Menu and Shortcut Changes
Name Changes to Graphics and Graphic Toolsets
Readme Files for Other Products in this Release
You can upgrade directly to System Platform 2023 from System Platform 2017 or later, provided the prior version was installed on a 64-bit operating system.
You can upgrade directly to System Platform Enterprise 2023 only from System Platform 2020 R2 SP1.
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.
You cannot mix System Platform and System Platform Enterprise nodes; all nodes must be either System Platform or System Platform Enterprise.
System Platform Enterprise requires FLEX licenses.
IMPORTANT! Back up any relevant application configuration files or 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 and System Platform Enterprise 2023 are:
See the GCS Technology Matrix for complete information about operating systems that you can use with System Platform 2023 products.
You can migrate user-created content (for example, .cab files, .aaPKG files, Historian databases, etc.,) to System Platform 2023, as long as the content was created in one of the following product versions:
Security changes in this release include the removal of certain assemblies from Microsoft and other third-parties that have reached their end-of-life and are now out of support, and may therefore pose a security risk. Some assemblies have been removed completely as they are no longer needed to support System Platform installation. Other assemblies and executables, listed in the following table, are still included with the installation media. You are given the option to install them on an as-needed basis. Note that installation of the following components is NOT recommended. Instead, we recommend that you rebuild any custom objects and applications using currently-supported software versions.
Redistributable Description |
Folder/Assembly Name |
Microsoft SQL Server 2012 Management Objects SP2 (11.2.5058.0) |
SQL2012SP2FeaturePack/SharedManagementObjects.msi |
Microsoft System CLR Types for SQL Server 2012 SP2 (11.2.5058.0) |
SQL2012SP2FeaturePack/SQLSysClrTypes.msi |
Microsoft Visual C++ 2008 Redistributable |
VC90SP1/vcredist_x86.exe |
Microsoft Visual C++ 2010 Redistributable |
VC10SP1/vcredist_x64.exe VC10SP1/vcredist_x86.exe |
You may need to install the out-of-support assemblies if you are using or migrating any of the following objects:
Both the $FieldReference and $Switch templates are discontinued ApplicationObjects, and no longer included with System Platform.
Note: If you do not install the out-of-support assemblies and import objects that have dependencies on them, you may see errors from the aaPim and WWPackageServer components while importing the objects.
The installation process requires that you acknowledge this change in behavior before you can successfully install System Platform. This applies to both GUI-based and command-line (silent) installation. See the following sections of the System Platform Installation Guide (SP_Install_Guide.pdf), located at the root of the DVD for additional information:
Installation Method |
Installation Guide Section |
GUI-based installation |
Installing System Platform |
Silent installation |
Using Silent Installation |
The end-of-life assemblies are included on the installation DVD under the InstallFiles\OutOfSupportRedist folder. If you select the option to install them now, they will be automatically installed during the installation process.
Important! Installation of out-of-support assemblies is NOT recommended.
Microsoft .NET Framework 4.8 is required for System Platform 2023. 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 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.
Some Start menu folders and some of the System Platform shortcuts they contain have been renamed. Commonly used applications, such as the Change Network Account utility, Configurator, and Operations Control Management Console, are now located under the AVEVA Start menu folder. These were under the Wonderware Utilities folder prior to System Platform 2020.
Old Name (SP 2017 Update 3 SP1 or earlier) |
New Name |
Type |
Wonderware Utilities |
AVEVA |
Folder |
Wonderware Documentation |
AVEVA Documentation |
Folder |
Wonderware Historian |
AVEVA Historian |
Folder |
Wonderware InTouch |
AVEVA InTouch HMI |
Folder |
Wonderware System Platform |
AVEVA System Platform |
Folder |
Sentinel System Monitor |
AVEVA System Monitor |
Folder |
ArchestrA Service Bus Portal |
Common Services Portal |
Shortcut |
AVEVA Enterprise License Manager |
Enterprise License Manager |
Shortcut |
Sentinel Application |
System Monitor Application |
Shortcut |
System Platform Management Console (SMC) |
Operations Control Management Console |
Application |
For 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 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.
Affected Systems
This information is applicable to a small subset of highly secured environments, in which operating systems and supporting networks have been configured to enable TLS 1.2 and where TLS 1.0 and 1.1 have been purposefully disabled. In these rare instances, some additional configuration is required to ensure that System Platform will work as expected.
System Platform 2023 includes various measures to strengthen security, including the ability to leverage TLS (Transport Layer Security) 1.2, provided that TLS 1.2 is enabled and configured in the host operating system.
In some cases, you may have to enable TLS 1.2 support by applying Microsoft updates and by making several manual edits to the system registry. The tasks of applying all Microsoft updates and editing the system registry must be completed before you install System Platform 2023. These instructions also apply to any other software products that support TLS 1.2. Follow the instructions listed below.
If you are required to enable TLS 1.2 and disable TLS 1.0 and TLS 1.1:
The .REG file shown below sets registry keys to their safest values.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
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.
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
Hardware Requirements
Operating System, Firewall, .NET Framework, and Virtualization Notes
Software Requirements
Windows Operating System Notes
Supported Operating Systems at Time of Release
.NET Framework Requirements and Compatibility
Third-Party Application Prerequisites
Operating System Notes
Operating System Notes: Common for AVEVA Products
Operating System Notes: InTouch HMI 2023
Operating System Notes: Application Server
Operating System Notes: Historian Client
SQL Server Considerations
Considerations for SQL Server Express
The following table provides guidelines for hardware configurations suitable for System Platform 2023 software based on the size of the application. These guidelines are subject to the limitations of your Windows operating system, and if applicable, to the SQL Server edition (Express, Standard, or Enterprise). See the AVEVA GCS Technology Matrix for supported versions of Windows operating systems and SQL Server.
The following guidelines are provided for reference only. The system configuration required for your application will depend on multiple factors, including but not limited to the size and complexity of the application, and the features and components used.
Application |
Level |
Logical Processors 1 |
RAM 3 |
Free Disk Space 2, 3 |
Network Speed |
Application Server Nodes 5 |
|||||
Small Application |
Minimum |
4 |
2 GB |
100 GB |
100 Mbps |
Recommended |
8 |
4 GB |
200 GB |
1 Gbps |
|
Medium Application |
Minimum |
8 |
8 GB |
200 GB |
1 Gbps |
Recommended |
16 |
12 GB |
500 GB |
1 Gbps |
|
Large Application |
Minimum |
16 |
16 GB |
500 GB |
1 Gbps |
Recommended |
32 |
24 GB |
1 TB |
Dual 1 Gbps |
|
Galaxy Repository Nodes |
|||||
Small Galaxy |
Minimum |
4 |
2 GB |
100 GB |
100 Mbps |
Recommended |
8 |
4 GB |
200 GB |
1 Gbps |
|
Medium Galaxy |
Minimum |
8 |
8 GB |
200 GB |
1 Gbps |
Recommended |
16 |
12 GB |
500 GB |
1 Gbps |
|
Large Galaxy |
Minimum |
16 |
16 GB |
500 GB |
1 Gbps |
Recommended |
32 |
24 GB |
1 TB |
Dual 1 Gbps |
|
Historian Server Nodes |
|||||
Small Historian |
Minimum |
4 |
2 GB |
100 GB |
100 Mbps |
Recommended |
8 |
4 GB |
200 GB |
1 Gbps |
|
Medium Historian |
Minimum |
8 |
8 GB |
200 GB |
1 Gbps |
Recommended |
16 |
12 GB |
500 GB |
1 Gbps |
|
Large Historian |
Minimum |
16 |
16 GB |
500 GB |
1 Gbps |
Recommended |
32 |
24 GB |
1 TB |
Dual 1 Gbps |
|
Thin Client Nodes |
|||||
RDP clients, InTouch Access Anywhere, mobile devices |
Minimum |
2 |
512 MB |
N/A |
100 Mbps |
Recommended |
4 |
2 GB |
N/A |
100 Mbps |
|
Client Nodes |
|||||
WindowViewer, OMI ViewApp, Historian Client, Remote IDE |
Minimum |
4 |
1 GB |
100 GB |
100 Mbps |
Recommended |
8 |
4 GB |
200 GB |
1 Gbps |
|
Remote-Desktop Server Nodes |
|||||
Basic RDS, InTouch Access Anywhere Server |
Minimum |
8 |
8 GB |
200 GB |
1 Gbps |
Recommended |
16 |
12 GB |
500 GB |
1 Gbps |
|
Large RDS, InTouch Access Anywhere Server |
Minimum |
16 |
16 GB |
500 GB |
1 Gbps |
Recommended |
32 |
24 GB |
1 TB |
Dual 1 Gbps |
|
All-In-One Nodes 4 |
|||||
Small Application - All products on one node: 1,000 I/O max |
Minimum |
8 |
8 GB |
200 GB |
100 Mbps |
Recommended |
12 |
12 GB |
500 GB |
1 Gbps |
|
Medium Application - All products on one node: 20,000 I/O max |
Minimum |
12 |
16 GB |
500 GB |
1 Gbps |
Recommended |
16 |
32 GB |
1 TB |
1 Gbps |
|
Large Application 6 - All products on one node: 100,000 I/O max |
Minimum |
20 |
32 GB |
2 TB |
1 Gbps |
Recommended |
24 |
64 GB |
4 TB |
1 Gbps |
|
1) To calculate the number of logical processors: multiply the number of physical cores by the number of threads each core can run. A four core CPU that runs two threads per core provides eight logical processors. The terms "Hyper-Threading and "simultaneous multithreading" (SMT) are also used to describe logical processors. |
|||||
Supported and Recommended Node Hardware Types
Product |
Server Node |
Thin Client- Server Node |
Client Node |
Thin Client |
All-In-One |
Application Server |
|||||
Galaxy Repository |
Preferred |
Supported |
Supported |
No |
Supported |
Application Engine |
Preferred |
Supported |
Supported |
No |
Supported |
IDE |
Preferred |
Supported |
Supported |
RDP |
Supported |
OMI ViewApp Runtime |
Supported |
Supported |
Preferred |
ITAA/RDP |
Supported |
InTouch Standalone |
|||||
WindowMaker (No Modern Apps) |
Supported |
Supported |
Preferred |
RDP |
Supported |
WindowMaker (with Modern Apps) |
Preferred |
Supported |
Supported |
RDP |
Supported |
WindowViewer / InTouch ViewApp (runtime only) |
Supported |
Supported |
Preferred |
ITAA/RDP |
Supported |
InTouch for System Platform |
|||||
WindowMaker (with Managed Apps) |
Preferred |
Supported |
Supported |
RDP |
Supported |
WindowViewer / InTouch ViewApp (runtime only) |
Supported |
Supported |
Preferred |
ITAA/RDP |
Supported |
InTouch Access Anywhere |
|||||
InTouch Access Anywhere Server |
Supported |
Preferred |
No |
No |
Supported |
InTouch Access Anywhere Client (HTML5 Browser) |
Browser |
Browser |
Browser |
Browser |
Browser |
InTouch Access Anywhere Secure Gateway |
Supported |
No |
No |
No |
No |
Historian |
|||||
Historian Server |
Preferred |
Supported |
Supported |
No |
Supported |
AVEVA Insight (Historian Client) |
Browser |
Browser |
Browser |
Browser |
Browser |
Historian Client |
Supported |
Supported |
Preferred |
RDP |
Supported |
Support Components |
|||||
OI Gateway |
Preferred |
Supported |
Supported |
No |
Supported |
AVEVA Enterprise Licensing - Server |
Preferred |
Supported |
Supported |
No |
Supported |
AVEVA Enterprise Licensing - Manager |
Preferred |
Supported |
Supported |
No |
Supported |
AVEVA Enterprise Licensing - Manager Client |
Browser |
Browser |
Browser |
Browser |
Browser |
Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for System Platform 2023. Refer to the following Microsoft Web sites for Windows and SQL Server hardware requirements.
Windows requirements
Note: System Platform 2023 is not supported on any 32-bit Windows operating system. Windows 10, Version 1809 (64-bit), is the earliest version of Windows 10 that supports System Platform 2023. For the complete list of supported Windows operating systems and SQL Server versions, see the AVEVA GCS Technology Matrix.
SQL Server requirements
For system sizing examples, see the System Platform Installation Guide (SP_Install_Guide.pdf).
The latest product information for each System Platform product is listed in the AVEVA Global Customer Support GCS Technology Matrix. Each link includes:
Minimum Required Operating System Version
The following table shows the minimum operating system for each product. See the GCS Technology Matrix for a list of all supported operating systems.
Product |
Minimum Required Operating System Version |
|
Client OS (x64 only) |
Server OS (x64 only) |
|
Application Server |
Windows 10 SAC Version 20H2 |
Windows Server 2016 or later SAC versions of later Windows Server operating systems are not supported |
InTouch |
||
Historian |
||
Important: Regardless of which operating system you are using, we recommend that you download and install the latest Microsoft updates to enhance security and ensure product compatibility.
Note: Only Windows Server versions licensed under Microsoft's long term servicing channel (LTSC) are supported. Versions of Windows Server licensed under the Semi-Annual Channel (SAC) do not include Desktop Experience, and therefore, are not supported.
The latest product information for each System Platform product is listed in the AVEVA Global Customer Support GCS Technology Matrix. Each link includes:
Note: Only Windows Server versions licensed under Microsoft's long term servicing channel (LTSC) are supported. Versions of Windows Server licensed under the Semi-Annual Channel (SAC) do not include Desktop Experience, and therefore, are not supported. For example SAC versions 1709, 1903, and 2003 are not supported.
64-bit only
System Platform Product / Component |
SAC Windows 10/11 Pro/ Enterprise/IoT Enterprise |
LTSC Windows 10/11 |
LTSC Windows Server |
Application Server 2023
|
Windows 10 20H2 Windows 10 21H1 Windows 10 21H2 Windows 11 21H2 Windows 11 22H2 Includes Professional, Enterprise and IoT Enterprise. |
Windows 10 1809 Windows 10 21H2 Windows 11 Includes Enterprise and IoT Enterprise |
2016 Standard and Data Center 2016 IoT 2019 Data Center, Essentials, and Standard 2019 IoT 2022 Standard and Data Center |
InTouch HMI 2023
|
|||
InTouch for System Platform 2023
|
|||
Historian Server 2023 |
|||
InTouch Access Anywhere Server 2023
|
|||
Other System Platform 2023 components / products
|
SAC: Semi-Annual Channel (subscription)
LTSC: Long Term Servicing Channel
LTSC is the newer name for LTSB (Long Term Servicing Branch)
Windows Server Notes:
Important! Installing System Platform 2023 on a computer used as a domain controller is not supported.
For more information, see the Microsoft Security Best Practices Checklist.
The following web clients are included with System Platform 2023:
The client programs listed above can be used with most common web browsers. Compatible browsers include:
Versions of .NET Framework (other than 4.x versions) can coexist, but all .NET code, including QuickScript.NET scripts, run under .NET Framework 4.8 or higher. For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility.
Upgrading SQL Server with AVEVA products installed is supported. See the AVEVA Global Customer Support GCS Technology Matrix for the complete list of supported SQL Server versions.
Only 64-bit versions of SQL Server are supported in this System Platform release. See Supported SQL Server Versions at Time of Release for more information.
If an error message about an unsupported SQL Server version is displayed while installing or upgrading System Platform, check the following:
64-bit only
System Platform Product / Component |
SQL Server Express SSMSE |
SQL Server |
Application Server 2023
|
2016 SP3
2017 Core
2019 Core |
2016 Standard/Enterprise SP3
2017 Standard/Enterprise
2019 Standard/Enterprise
2022 Standard/Enterprise |
InTouch HMI 2023
|
||
InTouch for System Platform 2023
|
||
Historian Server 2023 |
||
System Monitor Manager |
The default database is SQL Server 2019 Express Core
For information about which version of SQL Server you are running, see Determine the version, edition, and update level of SQL Server and its components.
The following virtualization software and cloud-based virtual environments are supported for System Platform 2023:
In order to establish communication with other components and services on the network, System Platform and Platform Common Services (ASB services) require certain network ports to be opened in the Windows Firewall. Typically, these ports are automatically opened for the Windows Firewall during installation. However, if the Windows Firewall service is disabled or not running at the time of installation, or if an alternative firewall is in use, you will need to manually open the appropriate network ports in the firewall. For more information about port configuration, see "Configuring Service TCP Ports" in the Application Server User Guide (filename: IDE.pdf).
Note: The ArchestrA Service Bus (ASB) is superseded by Platform Common Services (PCS). However, some ASB references remain in System Platform.
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.
Due to the Data Execution Prevention (DEP) feature in Windows operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host, or will behave unpredictably in InTouch, either in WindowMaker or WindowViewer.
The ActiveX controls and error message, along with solutions to resolve the behavior, are described in detail in TechNote 522, "Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)". You can download this TechNote from the AVEVA Global Customer Support (GCS) website.
The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on currently-supported Windows and Windows Server operating systems.
When InTouch WindowViewer is started and generates alarms from an interactive Windows or Windows Server desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.
This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.
To configure the AlarmViewer's alarm query
\\nodename:ip_address\intouch!$system
where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.
Windows Server no longer supports the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. Session 0 is no longer an interactive session, and is reserved only for Windows services. Windows Server treats all remote connections as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.
This impacts InTouch HMI functionality such as Alarm Manager that depends on the Terminal Server Console session. The impact to Application Server is minimal as most Application Server processes run as services. One impact to Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.
Refer to the InTouch HMI Readme for further information about InTouch HMI applications running in the Terminal Server Console.
If you are running WindowViewer within a Terminal Server session and want to access alarms from WindowViewer in a client session, you must use the syntax \\terminalservernode:<IP address>\InTouch!$System to access the alarms, with a colon (:) after the node name. The IP address is that of the client computer connected to the session.
NetDDE is not supported for InTouchView applications.
By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. Industrial Graphics make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, Industrial Graphics cannot communicate with InTouch tags when used with an InTouchView license.
In Industrial Graphics, InTouch:<tagname> is still a valid method of referring to an InTouch tag on a local node.
System Platform 2023 with InTouch HMI 2023 supports User Account Control-enabled operations on run-time nodes.
This section describes specific behaviors and restrictions when using the supported versions of Windows and Windows Server operating systems with Application Server.
User Account Control can be enabled when the Historian Client application is running as non-administrator.
IMPORTANT: System Platform 2023 leverages Microsoft .NET Framework 4.8. Multiple versions of the .NET Framework can coexist, if other applications on the same machine have dependencies on other .NET versions.
All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.8. Although .NET Framework 4.8 is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts.
In scripts for Industrial Graphics and/or Application Server objects, some .NET codes could fail if proper text encoding is not used. This may cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .NET Framework 4.5 and later. To enable a script to decode ASCII XML data, for example, insert the following snippet:
BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());
To learn more about changes introduced in different versions of the .NET Framework, refer to the following Microsoft resources:
SQL Server is required for Application Server, InTouch, and Historian Server. We recommend that you install and configure the supported SQL Server version before you begin the System Platform installation program. If you select SQL Server Express during System Platform installation, it will be installed automatically (applicable to small installations only).
The System Platform installer will install all prerequisites. If SQL Server is not installed, SQL Server 2019 Express Core is installed automatically. If you wish to install a full version of SQL Server, exit the installation program, install a supported SQL Server version, then resume the installation.
Other considerations are:
Important! A 32-bit version of SQL Server cannot be upgraded to a 64-bit version through SQL Server Setup. However, you can back up or detach a database from a 32-bit instance of SQL Server, and then restore or attach the database to a 64-bit instance. For more information, see Supported Version and Edition Upgrades for SQL Server 2017.
If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the SQL Access Configurator to restore it. Refer to the "About the System Platform Network Account" in the Application Server User Guide for additional information.
For Historian Client:
Note: Make sure that you are not using the 64-bit version of Microsoft Office.
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 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, 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 CR or 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. |
|
|
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:
|
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 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. |
TFS 1100582 |
Switching languages during run time while using multi-content panes that use locale-specific scripting calls can sometimes result in errors in the logger. Workaround: Restart the ViewApp after switching the run-time language. This action fully resolves the issue with no loss of functionality. |
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. |
Issue Number |
Description |
IMS 1592456 |
If a non-admin user logs into a remote IDE node and the User Access Control (UAC) setting in Windows is disabled, the user cannot launch AVEVA OMI editors from the IDE. AVEVA OMI editors are the Layout, Screen Profile, External Content, and ViewApp editors. Workaround: Turn on (enable) UAC on the remote IDE client node. |
TFS 1352630 |
When IP addresses are used for galaxy pairing, pairing is successful. However an error dialog is displayed and an error message is logged. The error message is similar to: "Failed to get the Discovery Service information for the target Galaxy Repository 'x.x.x.x'. Please see the logger for more details." Workaround: We recommended that you use the hostname of the node for galaxy pairing. If you use the IP address instead, make sure the reverse DNS lookup zone is configured properly on the DNS server. If the reverse DNS lookup zone is not set up while pairing the galaxy with the IP address, galaxy pairing may be successful. However you may see the message described above. You may safely ignore the error message. |
CR L00138837 |
AppEngine can crash due to calls made to API dlls even when using try/catch. This issue is specific to Nullable data types. The recommendation is to use wrapped API DLLs in Application Server scripting. |
TFS 1296015 |
In a client-server System Platform implementation where the client node is running a remote GR and run time features, the asb.Watchdog service may stop. As a result, MXData and Authentication warning messages appear in the logger. Workaround: Insert the System Platform installation DVD and run setup.exe, then select the Repair option. For more information, see "Repairing an Installation" in the System Platform Installation Guide (SP_Install_Guide.pdf). |
TFS 1291740 |
After editing a parent template with child template and instance objects across multiple hierarchy levels, checking in the template takes longer than expected. |
TFS 1290449 |
A legacy object with field attributes goes into an error state after importing a package file having field attributes and converting them using the Galaxy menu option, Convert Legacy UserDefined Object, even after the object has been validated. |
IMS 1999133 |
Creating a derived template or instance from an Object Wizard template fails when its hierarchical level has changed. The message "Create Instance: Fail to save the object. One or more related objects may be in use" appears. An error message also appears in the Logger, "Cannot insert the value NULL into column 'ow_setting_id', table '<GALAXY NAME>.dbo.ow_setting_def'; column does not allow nulls. INSERT fails." This behavior can occur when creating a derivative (template or instance) of an a Object Wizard template that was imported to a hierarchical level different from its level in the source Galaxy. Workaround: Create hierarchical levels of templates in the recipient Galaxy to match the original hierarchical level of the template in the source Galaxy. |
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. |
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 |
.NET Apps |
When importing AVEVA .NET Apps that use AVEVA Historian Client controls, some of the required files are not imported correctly. Workaround:
|
TFS 1345774 |
Logger errors from during the galaxy migration can occur if the Historian Client Control was renamed. Workaround: If a Historian Client Control in the galaxy was renamed, and if there are errors during migration related to the Historian Trend Client (aaTrendControl), resolve this error as follows:
Note: If you have multiple Historian Client Controls in the galaxy and errors are being logged, and you want to retain only the original Historian Client Control, you can do this as follows:
|
TFS 931966 |
When using silent install to upgrade Historian from System Platform 2017 or earlier that sets a default password for SQL Server users, warning messages are logged that alert you to set new passwords for various system users after the Configurator runs. Your system will continue to operate normally without resetting the passwords, but changing the passwords will increase system security. |
TFS 924302 |
When installing Historian along with any other component, and the other component requests a system restart, if you restart immediately after closing out the Configurator, a number of warnings may appear in the logger from the Historian services. This is caused by a timing issue. The warning messages can be safely ignored because they do not affect the configuration of the Historian, and do not have any effect on the system during or after the system restart. |
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. |
1881074 |
Multiple instances of the warning “Unable to add item ‘.ItemErrorCntAlarm.AlarmInhibit’ with access path‘’ are logged in the Logger when adding an item to a DASEngine. Workaround: Disable the device integration rules for which warnings are logged and publish the manifest. |
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.
Most System Platform help documents are provided as PDF and web help documents.
|
© 2022 AVEVA Group plc and its subsidiaries. All rights reserved. | Contact Us |