System Platform 2020 R2 SP1 Released

AVEVA™ System Platform, formerly Wonderware Version 2020 R2 SP1 Readme

New in System Platform 2020 R2 SP1

System Platform 2020 R2 SP1 includes the following features, as well as miscellaneous bug fixes.

New in Application Server and AVEVA OMI 2020 R2 SP1

Warm Failover

Redundant AppEngines can be configured for warm failover. This greatly reduces the time and number of scan cycles needed before the backup AppEngine becomes functional, and thus greatly reduces any data lost during failover. See the Redundancy section of the Application Server User Guide for details.

Alarm Message Translation

Alarm comment language switching (message translation) is now supported in the AVEVA OMI AlarmApp. See the Languages section of the AVEVA OMI Help.

New in InTouch HMI 2020 R2 SP1

InTouch HMI 2020 R2 SP1 (Version 20.1.100) includes a number of 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.

Cybersecurity Enhancements

This version of InTouch HMI incorporates the following cybersecurity enhancements:

  • Removal of end-of-life third-party redistributable assemblies
  • Removal of shared DLLs from GAC for Graphic Editor
New in Historian 2020 R2 SP1

This release of Historian includes the following new feature:

Licensing Enhancement

Additional product features, such as replication, can now be enabled with an incremental license without regenerating your original license.

New in Historian Client 2020 R2 SP1

This release of Historian Client incorporates miscellaneous bug fixes and hot fixes.

Web Help Display and Video Playback

Web Help – Browser-based User Assistance

Web help components have been delivered in this release. 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.

Typically, help content is installed on your local machine as part of the documentation library, and displays in your browser without requiring an Internet connection. When you install the Application Server IDE, a link to the AVEVA OMI Web Help is added to the Windows start menu. To open the help, use one of the following methods (depending on the editor/UI you are using):

  • Press F1 from the ViewApp editor, Screen Profile editor, or Layout editor.
  • From the System Platform IDE, select a Layout, ViewApp, Screen Profile, AVEVA OMI app, or External Content object and:
    • press Ctrl+F1, or
    • right-click, then select Help from the short-cut menu.
  • To open AVEVA OMI help from its installed location:

    C:\Program Files (x86)\ArchestrA\Framework\Docs\1033\NGX\index.htm

  • To open AVEVA OMI help from the start menu, go to:

    Start > AVEVA Documentation > AVEVA OMI Help

Browser Requirements and Recommendations

Internet Explorer is recommended.

  • Microsoft Edge will not load help content, unless you use the “Open with Internet Explorer” option in the Edge browser.
  • Chrome and Chromium-based browsers, such as Vivaldi, will not load help content unless you install and use an IE-rendering extension (for example, IE Tab).

Browser Permissions for Displaying Web Help

Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer as an example, you may see a dialog requesting that you “Allow blocked content” each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.

You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the Advanced tab, then navigate to the Security section. Enable the “Allow active content to run in files on My Computer.” Permissions and security settings will vary depending on your specific browser.

Playback of Tutorial Videos

The web help may contain a number of brief tutorial videos. To play these videos, you must have Microsoft Media Player installed on your local machine. In Windows Server operating systems, you must enable the “Desktop Experience” feature using Server Manager.

Internet Explorer (or IE-rendering in other browsers) may be required for viewing video content. If using a browser other than Internet Explorer without IE rendering enabled, videos may not be visible.


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 OM 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 Application Server 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.

  • The default installed location of the SDK is:

    C:\Program Files (x86)\ArchestrA\Framework\AcfSdk

  • To open the SDK help from the start menu, go to:

    Start > AVEVA Documentation > AVEVA OMI SDK Help

Resolved Issues

Issues that were previously listed as known issues in the System Platform Readme that are now resolved are listed in this table. For additional resolved issues that apply to a specific product, see the Readme file for that product.

Issue Number


TFS 1195009

Users experienced a 5 to 10 second delay if any option from the Configure New Asset dialog box was selected, or if the dialog box was closed.

TFS 1233570

The aaGR service generated errors and warnings when a Galaxy was migrated from System Platform 2014 R2 SP1 to System Platform 2020. This issue was most noticeable on nodes with eight or more cores, although it could also occur on nodes with six or fewer cores.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but was not documented.

TFS 1249822

If the aaGR process was restarted while importing a Galaxy, the import process did not complete.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but was not documented.

TFS 1258604

The System Platform IDE became non-responsive after attempting to edit a ViewApp associated with a layout that contained more than 32 panes.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but not documented.

TFS 1279394

In Application Server 2020, the MxDataprovider service may have had a memory leak of about 2MB per day (based on 5000 updates/sec or about 360 million changes/day).

Note: This issue was resolved in the prior release (System Platform 2020 R2) but was not documented.

TFS 1283400

An aaPKG file that contained a large number of objects or symbols could take longer to export or import in System Platform 2020 as compared to System Platform 2017 Update 3.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but was not documented.

TFS 1287606

At run time, an overview symbol showed the LocalSymbolSetting override, even though the override setting visibility was changed to false in the Object Wizard settings.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but was not documented.

TFS 1287616

After an attribute, script, or symbol was added to a template with about 2500 child instances, checking in the template took more than a minute.

TFS 1289649

Certain characters could not be entered when the Layout Script Editor was set to the International US keyboard. Instead of the typed character, the keyboard produced a space.

TFS 1290949

Changes to an Object Wizard containing a symbol during run time or while in preview mode do not hide the symbols associated with the Wizard.

TFS 1291740

After a parent template with child template and instance objects across multiple hierarchy levels was edited, checking in the template took longer than expected.

TFS 1292344

While the System Platform IDE was running and an ipconfig /release command was followed by an ipconfig/renew command on a remote client machine, the IDE remained responsive but objects could not be edited.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but was not documented.

TFS 1295525

A ViewApp did not always provide a WYSYWYG preview.

TFS 1295718

After an expression in a template was changed from locked to unlocked and an invalid expression was added to a script, a derived instance when into a warning state when the template was checked in.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but not documented.

TFS 1297211

When an instance object with a Boolean attribute was configured with read/write I/O (and options for invert, buffer, reflect input and output, and output every scan were enabled), the instance was overwritten by its parent template at run time, if the attribute in the parent object was configured as an Integer.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but was not documented.

TFS 1303484

The FLEX licensing configuration was lost if “Unlimited Engine” FLEX licensing was configured for an Application Server platform, and the System Platform IDE was closed and then reopened.

Note: This issue was resolved in the prior release (System Platform 2020 R2) but was not documented.

TFS 1342283

An error message that warned of an incompatibility was displayed if a computer was upgraded to System Platform 2020 R2 from System Platform 2020, and AVEVA Edge 2020 was installed on the same computer.

Known Issues

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.

  • ASB, PCS and MGC Issues
  • Communication Driver Pack Issues
  • Install/Uninstall and Galaxy Migration Issues
  • AVEVA OMI Issues
  • Application Server Issues
  • InTouch HMI Issues
  • InTouch Access Anywhere Issues
  • Historian Issues
  • Licensing Issues
  • System Monitor Issues
  • AVEVA Alarm Control Issues
  • Citect SCADA Co-Existence Issues

ASB, PCS and MGC Issues

ASB: ArchestrA Service Bus

PCS: Platform Common Services

MGC: Multi-Galaxy Communication

Issue Number


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 1278013

In certain multi-galaxy environments (MGC) running different versions of System Platform and using OS User Security, Verified Writes from InTouch to an attribute on another Galaxy node do not succeed. This occurs where one node is running System Platform 2014 R2 SP1, and a Verified Write is attempted from an InTouch window to an attribute on another node that is running System Platform 2020. Both nodes have InTouch and the GR installed. The following error message is logged: “Write attempt failed for the following reason: ‘Security error: 8018’.” However, Verified Writes from Object Viewer are successful.

Workaround: When performing a Verified Write from an InTouch window, enter the user name in the format “.\<UserName“. Do not use the format “<LocalMachineName>\<UserName>”.

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
at UnifiedAutomation.UaBase.ApplicationInstanceBase.LoadApplicationCertificate (ApplicationDescription application, String hostName, Boolean silent)
at UnifiedAutomation.UaBase.ApplicationInstanceBase.CheckConfiguration(Boolean silent)
at UnifiedAutomation.UaBase.ApplicationInstance.Start(ServerBase server, WaitCallback callback, Object userData, Boolean silent)
at PCS.Provider.OpcUa.UaServerHostedService.StartApplication()
at PCS.Provider.OpcUa.UaServerHostedService.<ExecuteAsync>d__7.MoveNext()


  1. Upgrade all nodes and install and configure PCS 4.4 on each.
  2. On the node that will function as the OPC UA Server, select the “No System Management Server configured” option and finish configuration.
  3. Start the Configurator again (reboot if necessary), and configure the System Management Server option as applicable for your system.

Communication Driver Pack Issues

Issue Number


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 User Guide, “Secured SuiteLink Connection,” available at [Installation Media]\InstallFiles\CD-OIEngine\Docs\OICore.pdf.

IMS 1435622


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.

Install/Uninstall and Galaxy Migration Issues

Issue Number


TFS 1354470

If Intelligence 2017 Update 1 (or prior version) is installed on a machine that has System Platform 2020 R2 installed, the Configurator cannot open after the system restarts.

Workaround: Install Intelligence 2017 Update 1 (or prior version), then install System Platform 2020 R2.

  1. Install Intelligence 2017 Update 1 and configure it.
  2. Install System Platform 2020 R2. System Platform will upgrade shared components such as Licensing during the installation process.
  3. Run the Configurator for System Platform 2020 R2 and restart the system.
  4. Run the Intelligence 2017 Update 1 Repair module (setup.exe). This will upgrade the Intelligence Configurator.
  5. Configure Intelligence using the upgraded Configurator.

TFS 1249251

Upgrading to System Platform 2020 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 has been 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):

  1. Detach the galaxy databases through SQL Server Management Studio.
  2. Back up the database files by copying the Galaxy folder in the path:
    C:\Program Files (x86)\ArchestrA\Framework\FileRepository\
  3. Uninstall the 32-bit version of SQL Server Express.
  4. Launch the System Platform 2020 installation program (setup.exe), and allow it to install SQL Server Express 2017 (64-bit).
  5. Restore the Galaxy folder to the path:
    C:\Program Files (x86)\ArchestrA\Framework\FileRepository\
  6. Attach the previously detached Galaxy database files.
  7. Restart the aaGR and Watchdog services.
  8. 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):

  1. Detach the galaxy databases through SQL Server Management Studio and make a backup (see Considerations for SQL Server for information about SQL Server Management Studio).
  2. Uninstall the existing 32-bit version of SQL Server.
  3. Install a supported 64-bit version SQL Server.
  4. Attach the previously detached Galaxy database files.
  5. Launch the System Platform 2020 installation program (setup.exe) and allow it to upgrade your products.
  6. After upgrade is complete, launch the IDE, then connect to the galaxy and migrate it.

    Galaxy migration should succeed without any issues.

TFS 1224058

When a galaxy with an ITMEViewApp object is migrated to System Platform 2020, an “ArchestrAObjectSupport” error message is logged.

Note: This issue has been corrected in AVEVA™ Edge 2020.

Workaround: You can avoid this issue by contacting AVEVA Customer Support for a patch compatible with your System Platform release. Before migrating your galaxy to System Platform 2020, import the ITMEViewApp Object patch.

If you have already migrated your galaxy to SP 2020 and are seeing an error message, import the ITMEViewApp Object included in the AVEVA™ Edge 2020 release.

TFS 1135229 TFS 1157116

If InBatch 2014 R3 or InBatch 2014 R3 SP1 is installed on the same node as System Platform 2017 or 2017 Update 1, upgrading to System Platform Update 3 SP1 may result in a compatibility issue that stops the IDE from working.

Workaround: Upgrade InBatch to version 2017 or later before upgrading to System Platform 2017 Update 3 SP1. InBatch 2017 and later versions are compatible with System Platform 2017 Update 3 SP1.


Issue Number


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:

  1. Open the Windows Control Panel and select Region.
  2. Select the Administration tab when the Region popup opens. The Administration tab contains two buttons:
    • Copy settings
    • Change system locale
  3. Select Copy settings and then mark the checkboxes to copy current settings to “Welcome screen and system accounts,” and “New user accounts.”
  4. 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:

  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:Computer Configuration > Administrative Templates > System > User Profiles
  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).
  4. Replace the NavTree object with the new NavTreeControl.
    1. Search for NavTreeControl under the Toolbox tab.
    2. 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:

  1. Launch the IDE and open the “Find” dialog.
  2. 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.

  3. Double-click the NavTree search result, which will select the NavTree object in the Graphic Toolbox.
  4. Delete the NavTree object from the Graphic Toolbox.
  5. 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 System 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:

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

Application Server Issues

Issue Number


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.

InTouch HMI Issues

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

Issue Number



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=, 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.


On Windows Server 2012 R2, when the TeamWork widget is opened as ShowSymbol animation, the InTouch HMI WindowViewer stops working.

Workaround: Use Windows Server 2016 or Windows 10.

InTouch Access Anywhere Issues

The following known issue is in addition to those documented in the InTouch Access Anywhere Readme.

Issue Number


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


.NET Apps

When importing AVEVA .NET Apps that use AVEVA Historian Client controls, some of the required files are not imported correctly.


  1. Import the App using the System Platform IDE by selecting Import from the Galaxy menu.
  2. Select AVEVA App.
  3. Select the folder containing the App to be imported.
  4. The App is imported and all the dependent files are copied to a new folder, C:\Program Files (x86)\ArchestrA\Framework\FileRepository\<GalaxyName>\ObjectFileStorage2\xxx, where xxx is a 3-digit number.

    Tip: Sorting the ObjectFileStorage2 folder by date modified can make it easier to locate the correct numbered folder.

  5. Some of the required files for AVEVA Historian Client controls may not be copied. For each of the controls your imported App uses, locate the corresponding folder(s) from the following list, and copy all the files from those folders into the folder from step 4:
    • Query control: C:\Program Files (x86)\ArchestrA\Framework\Bin\AVEVA_Software__LLC__aaHistClientQueryControl.dll
    • Tag Picker: C:\Program Files (x86)\ArchestrA\Framework\Bin\AVEVA_Software__LLC__aaHistClientTagPicker.dll
    • Time Range Picker: C:\Program Files (x86)\ArchestrA\Framework\Bin\AVEVA_Software__LLC__aaHistClientTimeRangePicker.dll
    • Trend control: C:\Program Files (x86)\ArchestrA\Framework\Bin\AVEVA_Software__LLC__aaHistClientTrendControl.dll

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:

  1. After migration, delete the renamed Historian Client Control. Note the name of this control as you will need it to rename the new control with the same name.
  2. Import the latest Historian Client Control aaPKG file from the following folder:
    C:\Program Files (x86)\ArchestrA\Framework\Bin
    File name: aaHistClientTrendControl.aaPKG
  3. Rename the imported client control with its original name (from step 1).

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:

  1. Delete the Historian Client Control with its original name (aaTrendControl).
  2. Rename one of the other Historian Client Controls to the original name (aaTrendControl).
  3. Delete the control you renamed in step 2. Note: This rename/delete process is required to maintain references that use the control.
  4. Repeat as many times as necessary until you have deleted the controls.
  5. Import the latest Historian Client Control aaPKG file from the following folder:
    C:\Program Files (x86)\ArchestrA\Framework\Bin
    File name: aaHistClientTrendControl.aaPKG

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.

Licensing Issues

Issue Number


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:
C:\ProgramData\Schneider Electric\Licensing\TrialLicensePool

For System Platform 2020, the file path for the TrialLicensePool folder is:

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

System Monitor Issues

The following known issues are in addition to those documented in the AVEVA System Monitor Readme.

Issue Number



On a fresh install, the Rule Overview page shows a Current Manifest Version value other than 1. The Manifest version listed on the Rules grid should show the value 1 because the out-of-the-box manifest is immediately published. However, the UI shows that the manifest has already been published more than once.


Machines are added to the Monitored Machines list with an inaccurate date/time value under the Discovered Date column.


Users can create multiple rules with the same name.


Manually specifying a proxy server in the Local Area Network (LAN) Settings configuration dialog results in inability to access the Sentinel Manager login screen.

Workaround: Use an automatic configuration script (provided by your IT department) to configure a proxy server.


On creating a rule to monitor a file or folder with a path longer than 100 characters, the rule is partially stored in the database and not published in the agent manifest.


On undeploying a platform that is being monitored, the Runtime Provider is stopped. On redeploy of the platform, the Runtime Provider does not resume until the Galaxy is rediscovered.

Workaround: Following redeploy of a platform, manually rediscover the Galaxy (in the Galaxy Diagram area). Alternatively, stop and restart the Sentinel Agent Service.


I’m Alive Emails are not sent consistently until 24 hours after enabling the notification.


On Reports with date parameters, the data returned is not inclusive of the end-date.


Distorted UI when downsizing browser window or viewing UI in a resolution less than 1440×900.


Start Menu with the option to open AVEVA System Monitor Manager is installed on non-Manager nodes.


On uninstall, System Monitor start menu options are not removed.


It may take up to five minutes for the Galaxy Diagram to reflect Alert changes to the Galaxy shape in Sentinel Manager.

Workaround: Refresh the page for the updated galaxy diagram after 5 minutes of change in the galaxy shape.


Email alerts cannot be sent through secured SMTP.


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.

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.

Citect SCADA Co-Existence Issues

We do not recommend installing System Platform 2020 R2 on the same the node where Citect SCADA is installed. To avoid issues, we recommend that you install System Platform and Citect SCADA on separate nodes.

Issue Number


TFS 1377931

If System Platform 2020 R2 is installed on a machine that already has Citect SCADA 2018 R2 installed, you cannot browse Citect SCADA 2018 R2 tags from the System Platform IDE.

Workaround: Install Citect SCADA 2018 R2 and System Platform 2020 R2 on separate nodes.

Leave a Reply

Your email address will not be published. Required fields are marked *

9 + 1 =