About this Readme - 2023 R2 Patch 01

Issue ID

Description

-

Client Controls which include any of the Historian Client Controls (Trend, Query, TimePicker, etc.) require an additional step to import correctly. Import the aaPKG files from C:\Program Files (x86)\ArchestrA\Framework\Bin first. The individual Client Control dll files can then be imported normally afterwards.

-

Runtime language switching limitations

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

-

When running a query from the Historian tab in Microsoft Word, a runtime error occurs if macros are not enabled.

Workaround

Macros must be enabled when using the Historian Client Report add-in for Microsoft Word.

-

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.

Workaround

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 default_empty.cab 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 aaSMC and restore the galaxy.

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

   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.

-

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

Workaround

10. Import the App using the System Platform IDE by selecting Import from the Galaxy menu.

11. Select AVEVA App.

12. Select the folder containing the App to be imported.

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

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