About this Readme

Description

Please note the following limitations of runtime language switching:

• Runtime language switching is not supported for embedded Query controls.

• For the Query tool, runtime language switching is only applicable to the Description field.

• For SQL connections, runtime language switching is only available for SQL-supported languages.

• If multiple connections are configured and one of the connections is Cloud (OData), when on an active cloud connection, the user will be prompted to log in each time the language is switched.

When using the Historian Client Report add-in for Microsoft Word, macros must be enabled when running a query from the Historian tab or a runtime error occurs.

Under certain circumstances, when migrating a CAB file to AVEVA System Platform 2023 R2 or later from a Galaxy older than System Platform 2020 that contains ArchestrA Graphics and utilizes the Historical Trend control, the migration may stall and be unable to recover. No error message is displayed.

In this situation:

1. Create a backup of the existing galaxy.

2. Save a copy of the following Historian Client binaries from an installation of AVEVA System Platform that matches the version your Galaxy is migrating from:

   • %ProgramFiles(x86)%\Common Files\ArchestrA\aaHistClientDatabase.dll

   • %ProgramFiles(x86)%\Common Files\ArchestrA\aaAFCommonTypes.dll

   • %ProgramFiles(x86)%\Common Files\ArchestrA\aaHistClientUtil.dll

3. Install AVEVA System Platform 2023 R2 or later.

4. Open the System Platform IDE.

5. Create a new galaxy with the same name as the previous galaxy. Select the Blank Galaxy type.

6. Close the System Platform IDE.

7. Copy the binaries saved from the previous version of AVEVA System Platform (from step 2) to: %ProgramFiles(x86)%\Common Files\ArchestrA\Framework\Bin

8. Open the Operations Control Management Console, and restore the Galaxy.

9. Open the System Platform IDE, and connect to the galaxy. This completes the migration.

   Note: These instructions assume that the default installation path was used. If a non-default path was used, copy the files from the applicable path.

   After successful migration, there may be errors reported from the aahEventEnum and aahEventSvc components, and warnings from the aahReplication component. These errors and warnings can be ignored.