AVEVA™ System Platform 2023 R2 SP1 Patch 01 Readme

Last revision: 3/20/2025

In This Document

Included in System Platform 2023 R2 SP1 Patch 01

New in System Platform 2023 R2 SP1 Patch 01

About patch release 2023 R2 SP1 Patch 01

AVEVA™ System Platform 2023 R2 SP1 ReadMe

Included in System Platform 2023 R2 SP1 Patch 01

This document contains important information about AVEVA™ System Platform 2023 R2 SP1 Patch 01, which applies a patch to the products listed below. The Readme file for System Platform 2023 R2 SP1 is included below, following the patch information.

The following AVEVA products and versions that are included in the release of System Platform 2023 R2 SP1 P01 (i) include Microsoft.web,webview2 (Webview2 SDK), (ii) include MicrosoftEdgeWebView2RuntimeInstaller; or (iii) are bundled with AVEVA’s PCS version 8.1.3, which includes the Microsoft.web,webview2 (Webview2 SDK). In those AVEVA products and versions, AVEVA has not disabled the Microsoft Defender SmartScreen in the respective release.

The Microsoft Defender SmartScreen feature collects and transmits user information to Microsoft, as detailed in Microsoft’s Privacy Statement at https://aka.ms/privacy and the Microsoft Edge Privacy Whitepaper at https://learn.microsoft.com/en-us/microsoft-edge/privacy-whitepaper#smartscreen. For additional details, refer to Microsoft documentation on Data and privacy in WebView2 - Microsoft Edge Developer documentation | Microsoft Learn.

The relevant AVEVA products and versions that are included in the release of System Platform 2023 R2 SP1 P01 are:

Program Name	Version
AVEVA Application Server and AVEVA OMI 2023 R2 SP1 P01	23.1.101
AVEVA Communication Drivers Pack 2023 R2 SP1 P01	23.02.101
AVEVA Historian 2023 R2 SP1 P01	23.1.101
AVEVA Historian Client 2023 R2 SP1 P01	23.1.101
AVEVA InTouch HMI 2023 R2 SP1 P01 (all languages)	23.1.101
AVEVA OMI Web	1.0.200.0
AVEVA Platform Common Services 8.1.3	8.1.25016.4

Review the individual product Readme files for details regarding product-specific known and resolved issues. When you extract the patch installation files, the product Readme files are extracted to individual folders. The Readme files are also posted on the AVEVA Global Customer Support (GCS) website. Readme files from previous releases of System Platform and its component products are also posted on the AVEVA Global Customer Support (GCS) website, along with additional technical information about System Platform. For the latest updates related to supported operating systems and databases, see the GCS Technology Matrix.

Notice: Online help access

The System Platform online help files and AVEVA Help Viewer will not be included or supported in future releases. All product documentation will continue to be available in PDF format on the installation media and on the web at docs.aveva.com.

New in System Platform 2023 R2 SP1 Patch 01

Severity 5 alarms

System Platform 2023 R2 SP1 Patch 01 allows up to five alarm severity levels to be defined and shown at runtime, instead of four as in prior releases.

New OMI ViewApp security attribute

A new security attribute, ShowLoginDialogAsTopMost, has been added to allow additional control over how the user login dialog is displayed.

Revised procedure for importing widgets

The procedure for importing a new widget version has been updated to avoid issues during import. For details, refer to "Import a newer widget version" in the Application Server Help.

Enhanced IDE import view

The IDE has been enhanced to let users configure, start, and monitor import operations while remaining in the galaxy view, without the need to switch to the IDE backstage. The Import button in the IDE ribbon now opens a context menu that replicates the functions that were previously available only from the IDE backstage. A Status button has also been added to the ribbon that lets you monitor the progress of import and deployment operations.

About patch release 2023 R2 SP1 Patch 01

In addition to the new features listed above, this patch release includes the following changes:

Incorporation of hot fixes for all products
Miscellaneous bug fixes
Improvements to the OMI web client.

Supported System Platform Versions for Product Upgrade

This patch can only be applied to System Platform 2023 R2 SP1.

Important! System Platform does not support mixed Windows workgroup/domain environments. As stated in the System Platform 2023 R2 Installation Guide, although workgroups are supported, domain-based networking is recommended. However, you cannot use workgroup nodes within a domain environment.

Readme Files for Other Products in this Release

The extracted patch files include a ReadMe directory with the Readme files for each individual component product. To access the product Readme files, navigate to the applicable folder under the ReadMe directory. Review the known and resolved issues contained in each file as applicable.

Resolved issues -- 2023 R2 SP1 Patch 01

See the product-specific Readme files for issues resolved in this patch release.

InTouch HMI Resolved Issues

In addition to the fixes listed in the InTouch HMI 2023 R2 SP1 P01 Readme file, InTouch HMI includes fixes for the issues listed in the following table. These issues were fixed too late to be included in the InTouch Readme.

Original Issue	Case/SR Number	Description
IMS-3750706	960546297	Trend Pen was not connecting to Historian when SMS was turned off and InTouch application was running on a computer other than the Historian.
IMS-3739322	960544363	In French version of InTouch HMI 2023 R2 SP1, could not import the .aaSLIB script library files in WindowMaker as the file did not appear in the import scripts window.
IMS-3778063	960548983	The option Cache Industrial Graphics not embedded in InTouch Windows under configure WindowViewer, did not remain selected after restarting the application.

Documentation corrections

This section lists corrections to System Platform documentation for this release.

In the System Platform Installation Guide

Location

Existing Text

Change

Industrial Graphic Editor User Guide/Web Help

Appendix A: Windows common control list methods

User Guide (PDF): page 439

Web Help: Windows common control list methods

FindItem

Purpose: Accepts a string as a parameter and returns the index of the first item that matches the string. The first item in the list has an index of 0.

Used by: Combo Box, List Box

Syntax: ControlName.FindItem(SearchString);

Info: Find an item in a list

FindItem

Purpose: Accepts a string and a Boolean as parameters and returns the index of the first item that matches the string. The first item in the list has an index of 0.

Used by: Combo Box, List Box

Syntax: ControlName.FindItem(SearchString, IgnoreCase);

Info: Find an item in a list

Industrial Graphic Editor User Guide/Web Help

Chapter 3: Work with Graphic Elements > Configure a time value display animation

User Guide (PDF): page152

Web Help: Configure a time value display animation

Elapsed time format

The format for elapsed time is:

[–][DDDDDD] [HH:MM:]SS[.fffffff]

Elapsed time format

The format for elapsed time is:

[–][DDDDDD] [HH:MM:]SS[.fffffff]

You cannot change the default format for elapsed time.

-- End of Patch 01 Readme --

AVEVA™ System Platform 2023 R2 SP1 ReadMe

Last revision: 10/29/2024

This document contains important information about AVEVA System Platform 2023 R2 SP1.

Included in this release

Program name	Version
AVEVA Application Server 2023 R2 SP1, including AVEVA OMI	23.1.100
AVEVA Communication Drivers Pack 2023 R2 SP1	23.2.100
AVEVA Enterprise License Manager 4.1.0	4.1.0
AVEVA Enterprise License Server 4.1.0	4.1.0
AVEVA Enterprise Licensing Platform 4.1.0	4.1.0
AVEVA Enterprise Licensing Platform(x86) 4.1.0	4.1.0
AVEVA Enterprise License Server Legacy Support 4.1.0	4.1.0
AVEVA Help	23.2.000
AVEVA Historian 2023 R2 SP1	23.1.100
AVEVA Historian Client 2023 R2 SP1	23.1.100
AVEVA InTouch HMI 2023 R2 SP1	23.1.100
AVEVA InTouch Access Anywhere Server 2023 R2	23.1.000
AVEVA InTouch Access Anywhere Secure Gateway 2023 R2	23.1.000
AVEVA OMI Web	1.0.100.0
AVEVA Platform Common Services 8.1.2	8.1.24299.3
System Monitor Agent Install Manager 1.6	1.6.0
System Monitor Manager 1.6	1.6.0
Operations Control Logger	23.2.000
Operations Control Management Console	23.1.000

New in System Platform 2023 R2 SP1

System Platform 2023 R2 SP1 includes the following features, as well as miscellaneous bug and security fixes.

New in Application Server and AVEVA OMI 2023 R2 SP1

Application Server 2023 R2 SP1 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 OMI web client

The web client for use with OMI ViewApps has been enhanced to eliminate many of the limitations that existed previously, and provide better alignment with the native behavior of desktop ViewApps.

OMI web client supported as Progressive Web Application

The OMI web client supports being saved as a Progressive Web Application (PWA). When an OMI web client PWA is launched, it displays a landing page listing all the deployed ViewApps. For an OMI web client PWA to work, the machine with the deployed WebViewEngine must be reachable.

OMI web client security enhancements

The system supports OS-user-based and OS-group-based security in the OMI web client. This includes support for the following MyViewApp namespace security attributes:

MyViewApp.LoggedInUserName (User Logon)
MyViewApp.LoggedInUserRoles (User Logon Roles)
MyViewApp.LoggedInAccessLevel (Access Level)

AlarmApp enhancements

The OMI AlarmApp has new columns available for alarm messages and ack messages. A new option has also been added to apply color or to blink an entire row, or just a single column.

HistoricalTrendApp enhancement

Follow Current Context now works for the HistoricalTrendApp.

Application Server instance name length

The maximum number of characters allowed for Application Server instances has been increased from 32 to 128.

Note that only instance names support 128 characters. Template object names continue to support a maximum length of 32 characters.
Graphics, Layouts, Screen Profiles, ViewAppNamespaces, ViewApps, InTouch ViewApps, and ViewEngines continue to support a maximum length of 32 characters.

Change Network Account utility

To simplify IT security tasks for multi-node systems, the Change Network Account utility, also known as .AdminUser Change Utility, lets you paste a plain text password into the utility. Copying the password from the utility remains prohibited.

New in InTouch HMI 2023 R2 SP1

InTouch HMI 2023 R2 SP1 (Version 23.1.100) 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.

Multi Pens Trend enhancements

XML Import/Export support

Now you can import and export the Multi Pens Trend to an XML file in the Industrial Graphic Editor. You can export the Multi Pens Trend to an XML file similar to other graphic elements. For more information on how to export and import a graphic element, see "Exporting and Importing Industrial Graphics Programmatically" in the AVEVA Industrial Graphic Editor Help.

Enabled Format String

The Format String option is now enabled in Multi Pens Trend Edit Animations. You can configure runtime options for all pens. The default value for Format String supports 0, #, comma, and decimal point. At runtime, values, minimum range, maximum range, and values in readout will use the selected format to display the values. Five formatting styles are supported. You can go to IDE > Galaxy > Configure > Styles and the configure format style.

Expand and collapse Top Header

The expand and collapse Top Header option allows you to collapse the Top Header and increase the chart area so that you can easily analyze the trends. Additionally, you can expand the Top Header to view the pen configuration when required.

Cursor readout shows the actual value

For the trend pen with line mode, even if the slope of the line goes beyond the trend plot area, the cursor readout now shows the actual value.

Render data of any quality

Render data of any quality option has been introduced in the Multi Pens Trend Animations screen to render and plot the trend for any data quality as per the current value. For the data quality other than good, the trend will be plotted in dotted lines.

Configured References enhancement

The ShowConfiguredReferences property is available in Industrial Graphic Editor under the Runtime Behavior section of the Properties pane. If you set the ShowConfiguredReferences property to True, then in runtime, on right-clicking any element, the Configured References dialog box opens and displays the attributes configured on that element.

Graphic Cache enhancement

At runtime, when you reopen the window, the default text configured in the respective animation is displayed instead of the previously cached values which caused confusion. For more information on caching the graphics, see "Configuring Memory Usage for WindowViewer Windows" in the AVEVA InTouch HMI help.

Supported animations for this graphic cache enhancement are:

Value Display
User Display
Color Change Fill
Color Change Line
Color Change Text
Tooltip
Named Style

Alarm Hotbackup pairs enhancement

The Hotbackup Utility now allows multiple hot backup pairs with the exact same node names. This is only allowed for provider types Galaxy and Galaxy_<name>.

Introducing Secret Key in Credential Manager

The Named Credentials dialog in InTouch Application Manager has been updated to support a new credential type. The new credential type is called Secret. The secret credential type allows a user to specify a secret string with a maximum length of 1024 characters. There is no username associated with the secret, just a string. It can contain any special characters and is meant for use with the Map application API key property.

Support for Secret Key and Credential Name in Map source provider

The API key property in the map source configuration now supports selecting a secret from Named Credentials. When typing the API key, the edit box will list named credentials of type Secret. You can select one of these named credentials as the API key. You will still have the option to manually specify the API key in the edit box. Displaying the named credentials in the API key edit box is only supported when using a standalone InTouch Application.

The map application in InTouch WindowMaker and WindowViewer has been updated to support the CredentialName property in the map application configuration. The CredentialName property is for specifying a credential which represents a Windows user login. This is used when a map server requires Windows authentication.

InTouch Alarm Utilities support for alarms with 128 characters

Alarm Utilities now support 128 characters.

Set colors for ACK and UNACK alarms

You can now set the text and background colors for records of acknowledged alarms and unacknowledged alarms. For each of the priority ranges, you can set a text color and a background color.

Removal of Wonderware NetDDE Helper Windows Service

The Windows Service Wonderware NetDDE Helper has been removed from the InTouch HMI product installation. The service startup type was Manual in previous releases. Hence the service was not running, unless explicitly started. There is no expected impact to your InTouch applications as part of removing this service.

New in Historian 2023 R2 SP1

AVEVA Data Hub is now rebranded to CONNECT Data Services.

Improved logging for secure communication to Historian is now enabled.

Support for Kerberos Authentication while replicating to PI Server has been added.

If a tag's raw type is Integer but its minimum or maximum value is configured as a float value, the raw type will now be changed to Float when it is replicated to CONNECT data services.

The following enhancements give the Historian Client Web a more modern look:

Kiosk mode is now supported. This allows you to set up a device to display pertinent information for an extended period of time that you can define.
Gantt charts can now be expanded or collapsed. You can also now disable or enable tags via the legend.
Line and scatter charts now display arrows in the margins to indicate when data extends outside the current scaling range.
Event and alarm overlays are now supported for line charts.

About this release

Supported System Platform versions for product upgrade

You can upgrade directly to System Platform 2023 R2 SP1 from System Platform 2017 or later, provided the prior version was installed on a 64-bit operating system.

Upgrades to System Platform 2023 R2 SP1 are NOT supported from the following System Platform versions:

System Platform Enterprise 2023
System Platform 2020 R2 CR1 and CR2

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 SP1 are:

Long Term Servicing Channel
- Windows 10 Enterprise, IoT Enterprise 2015 LTSB (1507)
- Windows Server 2016 LTSC Standard and Datacenter
General Availability Channel:
- Windows 10 22H2 Pro, Enterprise, and IoT Enterprise

See the GCS Technology Matrix for complete information about operating systems that you can use with System Platform 2023 R2 SP1 products.

Supported System Platform versions for migration

You can migrate user-created content (for example, .cab files, .aaPKG files, Historian databases, etc.) to System Platform 2023 R2 SP1, as long as the content was created in one of the following product versions:

System Platform: Version 4.5 or newer
Application Server: Version 2.5 or newer
InTouch HMI: Version 7.11 P07 or newer
Historian Server: Version 9.0 P02 or newer
Historian Clients: Version 9.2 or newer
FS Gateway: Version 1.5 or newer

Security changes related to end-of-life third-party components

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:

Microsoft SQL Server 2012 Management Objects SP2 (11.2.5058.0)
Microsoft Visual C++ 2008 Redistributable
Microsoft Visual C++ 2010 Redistributable

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:

Custom or third-party base templates built with the Application Object Toolkit, if they reference any of the removed libraries.
The discontinued ApplicationObjects $FieldReference and $Switch
Custom script libraries (DLLs) or custom .NET controls built with these out-of-support components.
Any other component that leverages the out-of-support assemblies.
Remote Response Objects (RRO).

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.

Application Object Toolkit

Microsoft .NET Framework 4.8 or later is required for System Platform 2023 R2 SP1. 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 SP1 release, but if you use AOT to build objects for Application Server, verify that you have installed and configured the developer pack for .NET Framework 4.8 when you create your AOT solution in Visual Studio.

Readme files for other products in this release

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	InstallFiles/CD-Intouch/ReadMe.html
Historian Server	InstallFiles/CD-Historian/ReadMe.html
Historian Client	InstallFiles/CD-HistorianClient/Readme.html
InTouch Access Anywhere	InstallFiles/CD-Server/ReadMe.html

Important notice: Windows updates

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.

Configure 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 'a0 Integrated Development Environmen 'a0

Integrated Development Environment (IDE), Galaxy Repository (GR), OMI web client and related components, and other services to shut down 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.

Browser and internet access security

In environments that allow browsers to access external web sites, we recommend that you use a proxy to limit browser access to only trusted sites.

Pending restart

If Windows Update or the System Platform setup program detects that a system restart is pending:

Restart your computer.
Run System Platform installation again.

What to do if the restart message reoccurs

Occasionally, restarting the computer does not clear the pending restart message. This can be caused by a value in the following registry key:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

Value: PendingFileRenameOperations

If you find this key/value combination:

Check the registry value data to identify the component that is requiring system restart and contact your IT department or the component vendor for further help.

If you are still not able to proceed with installation, contact AVEVA Software Support.

Import restrictions related to .NET Core

Libraries, client controls, and OMI apps compiled with any version of .NET Core (including .NET 5, 6, 7, or 8) are not supported in System Platform. While the system may indicate a successful import, these components will not appear in the IDE or be usable in design time or at runtime. Some .NET Standard libraries may work, but compatibility is not assured. For the best results, we recommend only using libraries compiled with .NET Framework 4.8.1.

Object name length limitations and compatibility

This version of System Platform extends the maximum name length for Application Server instance objects from 32 to 128 characters.

The maximum length of an object plus attribute and any extensions can be as long as 329 characters.
Not all products that can be used with System Platform allow the same object and attribute name lengths.
Only application object instances support 128 characters.
The maximum name length for WinPlatform instances is 127 characters.
The maximum name length remains 32 characters for templates and visualization objects such as Graphics, Layouts, Screen Profiles, ViewAppNamespaces, ViewApps, InTouch ViewApps, and ViewEngines.

The following products that are often installed with System Platform have different limitations than System Platform for object/attribute names.

Product/Component	Version	Max characters supported
AVEVA Manufacturing Execution System	2023	80
AVEVA Plant SCADA	2023 R2	254
AVEVA Mobile Operator	2020 R2 SP1	100
AVEVA Reports	2023 R2	254

How to Find the Latest Product Requirements and Compatibility Information

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 GCS Product Hub contains Readme files, videos, and product downloads from previous product releases.
The GCS Technology Matrix is a searchable database that contains the latest product information. Enter the product name in the search bar, then select the current release to view:
- Product Information: version name, number, release date, etc.
- Product Notes: key release information, new features, and updates
- OS Compatibility: list of compatible Windows and Windows Server versions
- Database Compatibility: list of compatible SQL Server and other database product versions
- Virtualization Compatibility: list of compatible virtualization software products and versions
- Product Coexistence: list of products that can be installed on the same computer
- Product Compatibility and Interoperability: list of products that can operate together and communicate with each other through a common message protocol

AVEVA System Platform help system

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

Microsoft Edge Non-Chromium
Microsoft Edge Chromium 97.0.1072.76 and newer
Firefox version 96.03 ESR and newer
Google Chrome version 98.0.4758.80 and newer
Opera version 83.0.4254.16 and newer

AVEVA OMI SDK

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.

The default installed location of the SDK is:
C:\Program Files (x86)\ArchestrA\Framework\AcfSdk

System Platform installation

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.

The AVEVA System Platform Installation guide is also found on the AVEVA documentation website.

Important! If you install System Platform to a location other than the default folder, you must set the Access Control List (ACL) for the selected location to avoid file tampering or other malicious activity. Refer to Microsoft's recommendations for setting the ACL for your version of Windows.

Before you install System Platform

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 SP1 must be installed before you install System Platform, if the product will be installed on the same node as System Platform. These are:

Alarm Adviser (2014 R2 SP1 and prior versions)
Intelligence (2017 SP1 and prior versions)
Recipe Manager Plus (2017 Update 1 and prior versions)
Skelta BPM (2017 R2 Update 1 and prior versions)

About the Network User Account

The Network User 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.

Caution: 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.

If the Network User Account has not previously been configured, you will be prompted to configure it during the System Platform installation. You must specify a user name, password, and domain.
If you use an existing user account, it should have a permanent password that does not expire, and the password should not be changed.
If your IT guidelines require that the password is changed periodically, note that this release allows you to paste a plain text password into the password field to simplify the task on multi-node systems.

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.

System Monitor installation and configuration

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).

Install System Platform.
Start the Configurator.
Configure the Common Platform, including the System Management Server (SMS) and license type, on all nodes. Only one SMS node should be configured per System Platform installation; configure all other System Platform nodes to point to the SMS node.
Configure the AVEVA System Monitor on all nodes. Only one System Monitor node should be configured per System Platform installation; configure all other System Platform nodes to point to the System Monitor node.
Configure the Alert Email Server on the System Monitor Manager node.
Configure the remaining product plug-ins.
Restart your system.

Re-connecting to System Management Server after hardware replacement or VM restoration

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:

Before replacing a connected machine, and/or restoring the connected VM to a pre-connected state, run the Configurator on that machine and disconnect it from the System Management Server.
If that is not possible (that is, the machine is no longer available due to hardware failure), then you will need to remove the connection information on the System Management Server manually:
After attempting to reconnect the machine, the logger will display the following 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.

Application Server topology with a remote OI server node

This information applies to the following System Platform topology:

Node 1: Application Server Galaxy Repository (GR)

Node 2: Operation Integration (OI) server node with the Communications Driver Pack (CDP). Node 2 does not have any other System Platform components installed.

Communications between the OI server and the GR will not be successful. This is because the Network User Account was not installed on the OI server node as part of the System Platform installation process.

Normally, a local Network User Account is automatically created when you install System Platform components, but this does not happen if CDP is the only System Platform component installed on the node. If you use this type of topology, use the Windows Computer Management app (Compmgmt.msc) to create a local Network User account on the OI server node. The account credentials must match those used on the other Application Server/System Platform nodes.

Licensing information

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.

Server-based license

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.

Security advisory

If your system includes clients that were configured to use a licensing version prior to AVEVA Enterprise Licensing Platform version 4.0, you can reduce potential security vulnerabilities as follows:

Configure Licensing in secure mode on all nodes.
Uninstall AVEVA Enterprise Licensing Legacy support from any license server nodes that include legacy support.

License server

The AVEVA Enterprise License Server can be installed separately from the AVEVA Enterprise License Manager.

Run both InTouch HMI and AVEVA OMI in a session on an RDS server

In System Platform 2023 R2 SP1, running both InTouch HMI and AVEVA OMI in a session on a remote desktop server (RDS) 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.

Reserve license for client devices

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. Each license can only be reserved to a single device, so if the device names are unknown ahead of time, it is 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 is important to know that neither AVEVA OMI nor InTouch HMI ViewApps support user-based license reservations. The end result will be that the software is unable to acquire the reserved license. 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, then the Device Name needs to follow this naming pattern:

where RDSHostName is the name of the Remote Desktop Server (RDS), and RDPClientName is the name of the computer running the RDP client software, and index is 1. If there will be multiple RDP sessions from a single client machine, 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 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 (Terminal Server) with a hostname of PrimaryRDS

Device Names:

License Reservation 1: PrimaryRDS-SupervisorPC1-1
License Reservation 2: PrimaryRDS-LineMgrA-1

Situation: A computer with a hostname of ExecutiveDesktop running four (4) Remote Desktop Clients (RDPs), connecting to the Remote Desktop Server with a hostname of PrimaryRDS

Device Names:

License Reservation 1: PrimaryRDS-ExecutiveDesktop-1
License Reservation 2: PrimaryRDS-ExecutiveDesktop-2
License Reservation 3: PrimaryRDS-ExecutiveDesktop-3
License Reservation 4: PrimaryRDS-ExecutiveDesktop-4

Enterprise licensing support in virtual environments

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 (HA) in VMWare and Hyper-V virtual environments does not activate licensing grace period during a failover as monitored environmental variables do not change.
Disaster Recovery (DR) in VMWare and Hyper-V virtual environments activates a licensing grace period as monitored environmental variables do change.

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

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

Resolved issues: Application Server

The Application Server ReadMe lists most of the resolved issues for this release. Resolved issues for other products included with System Platform are listed in the ReadMe for the product.

The following resolved issue is in addition to those listed in the Application Server ReadMe.

Issue	Description
IMS 3469816	An OMI ViewApp displayed a different number of active alarms than what was shown in Object Viewer.

Known issues

The following important known issues are listed by their assigned reference number in descending order. Additional known issues are documented in the product-specific Readme files.

PCS and MGC issues

PCS: Platform Common Services

MGC: Multi-Galaxy Communication

Issue Number	Description
IMS 3456786	After upgrading to PCS 8.1.2 on a node that has both System Platform 2023 R2 or 2023 R2 SP1 and Recipe Management 2023 R2, the RMPEventSvc service does not start and you are not able to view Recipe Management events in the OCMC Logger. The Logger also shows continuous warnings related to the PCS agent. Workaround: On the server running System Platform and Recipe Management 2023 R2, modify the file aaEventsEventService.aaSDEF by adding the <LaunchAssembly> property. Full path of the aaEventsEventService.aaSDEF file: C:\Program Files (x86)\Common Files\ArchestrA\Services\aaEventsEventService.aaSDEF Add <LaunchAssembly> property immediately after the <BinaryName> property. <LaunchAssembly>RMEventsEventServiceHost\RMEventsEventServiceHost.exe</LaunchAssembly> After you update the file, reboot the machine.
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 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.
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 2023 R2) 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: Open the Configurator and, under Common Platform, select System Management Server. Select No System Management Server configured and select Configure. Close the Configurator and reboot the node. After the reboot, open the Configurator again and set the System Management Server back to the correct selection: This machine is the System Management Server on the SMS and Connect to an existing System Management Server on all other nodes. Select Configure. Close the Configurator and reboot the node.
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.

Communication Driver Pack issues

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 guide, "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, 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.

Installation, upgrade, and galaxy migration issues


Issue Number		Description
IMS 3541417	After upgrading a node that contains both Application Server and Historian from System Platform 2020 to System Platform 2023 R2 SP1, a required DLL file is not installed. IMS 3540900 and IMS 3519786 are related to this issue, and the same general information applies to all three issues. Workaround 1: Uninstall System Platform, then do a fresh install of System Platform 2023 R2 SP1. Note: Be sure you have good backups of your Historian databases and Application Server galaxies before uninstalling System Platform. Workaround 2: Back up your Historian databases and Application Server galaxies and restore on a new node with System Platform 2023 R2 SP1. Workaround 3: Install System Platform 2023 R2 SP1 on a VM, then: Copy the following files from the VM: C:\Program Files (x86)\Wonderware\Historian\x64\System.Security.Cryptography.Cng.dll C:\Program Files (x86)\Wonderware\Historian\System.Security.Cryptography.Cng.dll Paste the copied files to the same locations on the existing node.
IMS 3540900	After upgrading a node that contains both Application Server and Historian from System Platform 2020 to System Platform 2023 R2 SP1, a required DLL file is not installed. IMS 3541417 and IMS 3529786 are related to this issue, and the same general information applies to all three issues. Workaround 1: Uninstall System Platform, then do a fresh install of System Platform 2023 R2 SP1. Note: Be sure you have good backups of your Historian databases and Application Server galaxies before uninstalling System Platform. Workaround 2: Back up your Historian databases and Application Server galaxies and restore on a new node with System Platform 2023 R2 SP1. Workaround 3: Install System Platform 2023 R2 SP1 on a VM, then: Copy the following files from the VM: C:\Program Files (x86)\Common Files\ArchestrA\Services\System.CodeDom.dll Paste the copied files to the same locations on the existing node.
IMS 3523525	After upgrading a node that contains both Application Server and Historian from System Platform 2020 R2 to System Platform 2023 R2 SP1, some files that should no longer be present on the node remain. This only occurs if both Application Server and Historian are installed. No user action is required.
IMS 3521148	After upgrading a node that contains both Application Server and Historian from System Platform 2023 to System Platform 2023 R2 SP1, errors related to licensing and the licensing API (LicAPISvcProxy.NET) appear in the logger. Workaround: This issue occurs when products attempt to acquire the license before the licensing service has started. This is an expected error during installation or upgrade. Once the installation or upgrade is complete, these errors will not occur.
IMS 3519786	After upgrading a node that contains both Application Server and Historian from System Platform 2023 to System Platform 2023 R2 SP1, some files that should no longer be present on the node remain. This only occurs if both Application Server and Historian are installed. No user action is required.
IMS 3509408	After upgrading from System Platform 2023 R2 SP1 from System Platform 2023 R2, data cannot be read from written to the OPC UA Service deployed from the IDE through the DDESuiteLink object. This occurs when using 128 character names for instances of the UserDefined object, combined with user defined attributes that also have 128 character names.
IMS 2967085	During an upgrade to System Platform 2023 R2, 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, select Cancel 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. Navigate to %LOCALAPPDATA%\Packages\Microsoft.Windows.Search_<AlphaNumericID>\LocalState\AppIconCache\100 and delete all files in the folder. Restart your machine. The updated icons should now appear.
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/ IMS 1739197		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 be using 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): Detach the galaxy databases through SQL Server Management Studio. Back up the database files by copying the Galaxy AVEVA™ System Platform Installation folder in the path: C:\Program Files (x86)\ArchestrA\Framework\ FileRepository\ Uninstall the 32-bit version of SQL Server Express. Launch the System Platform 2020 installation program (Setup.exe), and allow it to install SQL Server Express 2017 (64-bit). Restore the Galaxy folder to the path: C:\Program Files (x86)\ArchestrA\Framework\ FileRepository\ Attach the previously detached Galaxy database files. Restart the aaGR and Watchdog services. Launch the IDE, then connect to the galaxy and migrate it. Galaxy migration should succeed without any issues. Method 2 (Install full version of SQL Server): Detach the galaxy databases through SQL Server Management Studio and make a backup (see Considerations for SQL Server in the System Platform Deployment documentation for information about SQL Server Management Studio). Uninstall the existing 32-bit version of SQL Server. Install a supported 64-bit version of SQL Server. Attach the previously detached Galaxy database files. Launch the System Platform 2020 installation program (Setup.exe) and allow it to upgrade your products. After upgrade is complete, launch the IDE, then connect to the Galaxy and migrate it. Galaxy migration should succeed without any issues.

Application Server issues

The following issues may be seen when using long instance names.

Issue	Description
IMS 3533007	The ITAlarmProvider component will log warnings while generating alarms and events, if the total length used for ObjectName, AttributeName, Attribute Description and Alarm comments exceed 450 characters. This is due to a limitation in the AlarmManager component. This limitation will be fixed in a future release.
IMS 3509408	Data cannot be read from or written to the OPC UA Service when long object and attribute names are used. The total reference string (object name plus attribute name) cannot exceed 254 characters. If the reference string exceeds 254 characters, you will see errors generated from the aaCALWrapper.exe process and WWCLINTF component.
Redundant Telemetry Server issue	In a Redundant Telemetry Server deployment using PCS connectivity to Application Server, failover from the primary Telemetry Server to secondary Telemetry Server is not instantaneous and may take several seconds to complete. During this time, loss of data may occur.

AVEVA OMI issues

The following issues may be seen when using long instance names (greater than 32 characters). One issue was seen when using seven levels of template containment, but using the maximum 32 character length for each template name.

Issue	Description
OMI preview issue	Warnings appear in the logger when OMI Preview is launched when using Object Wizards/Symbol Wizards in a seven-level containment relation, using the maximum template length (32 characters).
Show graphic issue	The title of a show graphic is cut off in the OMI web client when using long object names (> 32 characters).
Localized character issue	Localized characters do not display in the component column of the Logger in the Operations Management Console when using long object names (> 32 characters).
Incomplete tooltip issue	The Tooltip for an instance graphic is displayed incompletely in the Japanese language version when long object names (> 32 characters) are used.
AutoComplete issue	When used with long object names (> 32 characters), the autocomplete text is not fully shown in the Graphic or Layout editors, or in the Edit Animations dialog, that is, the text is cut off on the left side.
Graphic alignment issue	When long names are used for TagName, Hierarchical Name, and Contained Name, graphics are shifted to the right when displayed using the Value Display animation at run time.

The following issues were observed in previous releases, but may still occur occasionally.

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: Open the Windows Control Panel and select Region. Select the Administration tab when the Region popup opens. The Administration tab contains two buttons: Copy settings Change system locale Select Copy settings and then mark the checkboxes to copy current settings to "Welcome screen and system accounts", and "New user accounts". Select Change system locale and then choose the applicable locale from the dropdown list.
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: A symbol is added to the Graphic Toolbox with an undefined relative reference, for example, “Me.Attribute001,” where Attribute001 has not been created yet. The symbol is then added to a layout. The layout is linked to a UDO (User Defined Object) template. When the template is saved, no warning is displayed. 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."
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: Open the ViewApp or Layout that shows the warning. 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. 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). Replace the NavTree object with the new NavTreeControl. Search for NavTreeControl under the Toolbox tab. Drag the NavTreeControl onto the pane to replace the NavTree. Confirm that you want to replace the content, then save the ViewApp or Layout and close the editor. Verify Layouts and ViewApps no longer show any warnings related to the NavTree. Deploy the ViewApp. Workaround 2: To replace references to NavTree when importing packages from System Platform 2017: Launch the IDE and open the “Find” dialog. Search for “NavTree” using the default search settings. If the package file contains the obsolete NavTree object, it will be listed in the search results. Double-click the NavTree search result, which will select the NavTree object in the Graphic Toolbox. Delete the NavTree object from the Graphic Toolbox. Use Workaround 1 to replace the NavTree object with the new NavTreeControl object.
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: InSightApp MapApp WWWebAppControls 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, if you first attempted to perform the VerifiedWrite without having the correct security credentials, then the VerifiedWrite dialog is not displayed when you modify the value of a VerifiedWrite attribute from a combo box.
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: An override values for a custom property that is later made private. The override is also shown at run time. An override is applied to a custom property, and later the custom property is locked (can no longer be overridden). When the ViewApp is redeployed, the override value is still shown. 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: 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. 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,. 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: The Historian Server node name and port are not set in the application settings file for the proxy server on the WebViewEngine platform. The Historian Server does not use the security certificate from the System Management Server. This means the web client does not have a trust relationship with the Historian Server and will not accept data from it. 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: On the WebViewEngine node, in a text editor, open the file C:\Program Files (x86)\Common Files\ArchestrA\Services\proxyserver\appsettings.json. Find this section of the file: "history-data": { "HttpRequest": { "Version": "1.1", "VersionPolicy": "RequestVersionExact" }, "Destinations": { "destination1": { "Address": "https://localhost:32573/" Change localhost to the name of the node where the Historian Server is installed. If Historian is not using the default port of 32573, also set the correct port number. Save and close the file.
	Workaround 2: To fix the security certificate issue, you have two choices. Install each Historian's certificate on every remote node that will use the OMI web client. You do not need to shut down or disable Historian to do this, but each node or remote device must have the Historian certificate installed before it can use the OMI web client. Change the Historian Server node to use the certificate of the System Management Server. You need to shut down and disable the Historian during the change, but this method requires changes only on the Historian Server node. 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 Historian certificates on Windows nodes or remote devices 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. For each web client node, in a supported web browser, go to https://<historian_node>:32573/. (If Historian is not using the default port of 32573, use the Historian port number for your installation.) Select the Not secure message, then, in the dialog box that opens, select Certificate is not valid. On the Certificate Viewer dialog box, on the Details tab, under Certificate Hierarchy, select the line that ends in ... CA. Select Export. Save the Historian certificate to a file. You can place it in any folder and give it any name, but do not change the file type. Install the certificate. You can do this either by executing the certificate file you just created, or by opening the Windows Certificate Manager from the Start menu. Once you have started the process, follow the wizard prompts and place the Historian certificate in your Trusted Root Certification Authorities store. Close, and re-open your browser. You should now be able to open the OMI web client, start the ViewApp, and see historical data. 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 On the Historian Server node, use the OCMC to stop and disable the Historian: Start the OCMC and expand the Historian node in the left pane until you see the Historian Server node name. Expand the node name. Right-click Management Console, select All Tasks, and select Shutdown (and disable) Historian. On the Shutdown and Disable Historian dialog box, make sure the node name is correct and select OK. From the Windows start menu, select AVEVA, then Configurator. Under AVEVA Historian, select Server. Select Rest Configuration. The Rest Configuration dialog box opens. For Certificate Source, select Provided by IT. In Certificate, select <hostname> ASB, where <hostname> is the name of the node where the Historian Server is installed. Select OK, then select Configure. Select Close to close the Configurator. In the OCMC, restart the Historian: Expand the Historian node again. Right-click Management Console, select All Tasks, and select Enable (allow to run) Historian.
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.

AVEVA Industrial Graphic Editor issues

Issue 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.

InTouch HMI issues

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 R2 SP1, you may notice the following issues related to Secure SuiteLink Connection: The SuiteLink client does not connect to the WindowViewer. The Web Client does not bind to InTouch tag. When WindowViewer is launched, the system displays the SuiteLink error message in the Logger. Workaround: To ensure connectivity between the SuiteLink client and the WindowViewer: Enable System Management Server in the Configurator. Configure Secure SuiteLink connection (V3). Enable Unsecure SuiteLink connection (V2) fall back. For more information, see Configuring a secure SuiteLink communication in the AVEVA InTouch HMI Help.
IMS 3582930	When creating a new InTouchViewApp, and the Include all graphics from graphic toolbox option is selected from the Tag Dictionary, error messages from WWFsObject and aaMxValue components appear in the Logger. Workaround: None is needed. There is no loss of functionality.
IMS 3567276	In runtime, all pens of Multi Pens Trend may not update in synchronization. Workaround: Use Set time period option in runtime, to change the time period and hence to update all pens in synchronization.
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.
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 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 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.

InTouch Access Anywhere issues

The following known issues are in addition to those documented in the InTouch Access Anywhere Readme.

Issue Number

Description

IMS 2973015

User access to the local drive from InTouch Access Anywhere 2023b is prevented due to security issues. You will not be able to save a downloaded file because File Explorer does not to let you specify a location to save the file. The file is instead downloaded to the user's temporary file location.

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.

Historian issues

Issue Number	Description
IMS 3541417	After upgrading a node that contains both Application Server and Historian from System Platform 2020 to System Platform 2023 R2 SP1, a required .DLL file is not installed. IMS 3540900 and IMS 3519786 are related to this issue, and the same general information applies to all three issues. Workaround 1: Uninstall System Platform, then do a fresh install of System Platform 2023 R2 SP1. Note: Be sure you have good backups of your Historian databases and Application Server galaxies before uninstalling System Platform. Workaround 2: Back up your Historian databases and Application Server galaxies and restore on a new node with System Platform 2023 R2 SP1. Workaround 3: Install System Platform 2023 R2 SP1 on a VM, then: Copy the following files from the VM: Program Files (x86)\Wonderware\Historian\x64\System.Security.Cryptography.Cng.dll Program Files (x86)\Wonderware\Historian\System.Security.Cryptography.Cng.dll Paste the copied files to the same locations on the existing node.
IMS 3540900	After upgrading a node that contains both Application Server and Historian from System Platform 2020 to System Platform 2023 R2 SP1, a required .DLL file is not installed. IMS 3541417 and IMS 3529786 are related to this issue, and the same general information applies to all three issues. Workaround 1: Uninstall System Platform, then do a fresh install of System Platform 2023 R2 SP1. Note: Be sure you have good backups of your Historian databases and Application Server galaxies before uninstalling System Platform. Workaround 2: Back up your Historian databases and Application Server galaxies and restore on a new node with System Platform 2023 R2 SP1. Workaround 3: Install System Platform 2023 R2 SP1 on a VM, then: 1. Copy the following files from the VM: C:\Program Files (x86)\Common Files\ArchestrA\Services\System.CodeDom.dll 2. Paste the copied files to the same locations on the existing node.
IMS 3523525	After upgrading a node that contains both Application Server and Historian from System Platform 2020 R2 to System Platform 2023 R2 SP1, some files that should no longer be present on the node remain. This only occurs if both Application Server and Historian are installed. No user action is required.
IMS 3519786	After upgrading a node that contains both Application Server and Historian from System Platform 2023 to System Platform 2023 R2 SP1, some files that should no longer be present on the node remain. This only occurs if both Application Server and Historian are installed. No user action is required.

Licensing issues

Issue Number	Description
IMS 3521148	After upgrading a node that contains both Application Server and Historian from System Platform 2023 to System Platform 2023 R2 SP1, errors related to licensing and the licensing API (LicAPISvcProxy.NET) appear in the logger. Workaround: This issue occurs when products attempt to acquire the license before the licensing service has started. This is an expected error during installation or upgrade. Once the installation or upgrade is complete, these errors will not occur.
IMS 2655533	Issue: The status symbol for the License Server security plug-in may not show the actual configured status of license server security. This can occur if: You change the SMS configuration. If you change the SMS configuration, the Configurator will continue to show the license server as configured securely (green icon). You must reconfigure secure mode by selecting Configure, even though the plug-in already shows that it is configured. You do not configure an SMS node. If you do not configure SMS, the Configurator will show that license server security is in a warning state (orange icon). Even though there is no SMS, you still must configure the secure mode by selecting Configure. This will not change the plug-in status icon; it will still show a warning state. However, this step is required to enable communication between the license server and license manager. Note that having an SMS configured is a requirement for secure communication between the license server and other System Platform components. Workaround: Always configure secure mode for the License Server security plug-in by selecting Configure. When you first configure the System Platform node, even if you do not configure a SMS. If you change the SMS configuration.
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	Manufacturing Execution System (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: C:\ProgramData\Schneider Electric\Licensing\TrialLicensePool For System Platform 2020, the file path for the TrialLicensePool folder is: C:\ProgramData\AVEVA\Licensing\TrialLicensePool Workarounds: Use one of the following workarounds. If only the file path C:\ProgramData\Schneider Electric\Licensing\TrialLicensePool is on your system, change the name of the Schneider Electric folder in the file path to AVEVA. No other change is needed. If both file paths exist on your system, copy the trial license from C:\ProgramData\Schneider Electric\Licensing\TrialLicensePool to C:\ProgramData\AVEVA\Licensing\TrialLicensePool. No other change is needed If the AVEVA License Manager is open while you are moving the license file or renaming the file path, you may see a series of error messages. However, these will clear once the trial license is acquired. You can avoid this by closing the License Manager prior to renaming or moving the file.
TFS 793643	If no default browser is set, 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.

System Monitor issues

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 shows an alert that Bootstrap is not running that does not update to show Bootstrap is running.

Workaround: Resolve the Bootstrap alert. It will not show the incorrect status again.

AVEVA Alarm Control issues

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 Co-Existence issues

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 2023 R2 SP1 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

Change the value of InstallPath to C:\Program Files (x86)\ArchestrA\Framework\ (add the final backslash character)
Change the value of TargetInstallPath to C:\Program Files (x86)\ArchestrA\ (add “ArchestrA\”)

Documentation

Most System Platform help documents are provided as PDF and web help documents.

The System Platform Installation guide is located in the root folder of the installation DVD.
Use the Start Menu to access Application Server, InTouch HMI, Historian, and other System Platform PDF documents in the AVEVA Documents folder.
Online help can be viewed in your browser using the AVEVA Products Help Viewer.
- To launch the Help Viewer from the Windows Start menu, select AVEVA, then select AVEVA Help.
- The Online Help can also be accessed directly from the various System Platform applications, including Application Server (System Platform IDE), InTouch HMI (WindowMaker), and Historian.
The AVEVA System Platform 2023 R2 SP1 documents are also available online from the AVEVA documentation site.

AVEVA OMI documentation corrections

This section lists important OMI documentation corrections.

Location of Change

Existing Documentation

Change

OMI Help

Install a security certificate on Windows

https://localhost:28808/AVEVA%20OMI/#/home/1313125/10/11

To install security certificate on Windows

Open File Explorer and navigate to the certificate file you copied to the devices, then open the certificate file. The Certificate dialog box opens.

To install a security certificate on Windows

Open File Explorer and navigate to the certificate file you copied to the devices, then double-click on the certificate file to open it. The Certificate dialog box appears.

InTouch HMI documentation corrections

This section lists important InTouch HMI documentation corrections.

In the Industrial Graphic Editor help documentation, in the Set configured references section, add a note to show that the ShowConfiguredReferences property is not supported in OMI. Configured reference is disabled in runtime OMI.