AVEVA™ Historian Client 2023 R2 Patch 01 Readme

Last revision: 6/6/2024

In This Document

About this Readme - 2023 R2 Patch 01

Resolved Issues - 2023 R2 Patch 01

AVEVA™ Historian Client 2023 R2 Readme

About this Readme - 2023 R2 Patch 01

This document describes the resolved issues and known issues in AVEVA Historian Client 2023 R2 Patch 01. It also includes the entire AVEVA Historian Client 2023 R2 Readme after the Patch 01 Resolved Issues.

Known Issues

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.
-	Issue 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.
-	Issue 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 Create a backup of the existing galaxy. 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 Install AVEVA System Platform 2023 R2 or later. Open the System Platform IDE. Create a new galaxy with the same name as the previous galaxy. Select the default_empty.cab type. Close the System Platform IDE. Copy the binaries saved from the previous version of AVEVA System Platform (from step 2) to: %ProgramFiles(x86)%\Common Files\ArchestrA\Framework\Bin Open aaSMC and restore the galaxy. 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: Import the App using the System Platform IDE by selecting Import from the Galaxy menu. Select AVEVA App. Select the folder containing the App to be imported. 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. 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

Resolved Issues - 2023 R2 Patch 01

Issue ID	Related Issues	SR/Case Number	Description
IMS-2996637		960373381	In Historian Client Trend, the options for tags display incorrectly.
IMS-2987403		960333105	Historian Client control tooltip may fail to work sometimes.
IMS-2995299		960369817	When an alarm is inhibited then uninhibited, the entire curve is highlighted in yellow.
IMS-2995897		960372801	Discrete values are not displayed in the Query client when the "ALL" tab is selected in the tag picker for history values.
IMS-3018608		960379143	The FROM clause disappears from the SQL query code if you uncheck either the QualityDetail or QualityDescription option for "Live Values" when using Historian Client Query.
IMS-2960326	IMS-3025318	960364301	Historian Client Trend and Query hang on opening.
IMS-3053957		960386657	The event tag isn't displaying in Trend when non-event tags are also displayed.
IMS-3025741		960378382	When creating a new galaxy, the client controls aaHistClientTrendControl, aaHistClientActiveDataGrid, aaHistClientSingleValueEntry, aaTagPicker, and aaTimeRangePicker are missing.
IMS-3186974		960393140	An error occurs when retrieving tag values from Historian Server 2017 Update 3 SP1.
IMS-3198534		960396138	After migrating a galaxy from SP2023 P02 to 2023 R2, scripts time out. This is particularly prevalent with scripts that call out a Namespace attribute.
IMS-3207981		960397172	In the Query tool, text pasted into the filter fields "Tag Name", "Description", and "I/O Address" pastes twice.
IMS-3258436		960396124	When switching from Windows to SQL authentication in the Excel add-in, the following Visual Basic error occurs: "Run-time error '-2147467261 (80004003)' Object reference not set to an instance of an object".
IMS-3265360		960390581	In the Query tool, queries fail with the error "Error executing query: Invalid column name 'wwUnit'."
IMS-3314949		960414166	When using AVEVA Window Maker, the follow error occurs: "Unhandled exception (Micorsoft .NET Framework) - ArchestrA.HistClient.UI.TrendAction.LicenseTimer_Tick".
IMS-3338549			The aaTrendClient control doesn't show tag properties.

--- End of 2023 R2 Patch 01 Readme ---

AVEVA Historian Client 2023 R2

Last revision: 11/30/2023

About This Readme

This Readme provides information about AVEVA Historian Client 2023 R2.

For information about using the product, see the AVEVA Historian Client documentation.

Known Issues in This Release

Issue ID	Description
-	Issue 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.
-	Issue Under certain circumstances, when migrating a CAB file to AVEVA System Platform 2023 R2 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 Create a backup of the existing galaxy. 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 Install AVEVA System Platform 2023 R2. Open the System Platform IDE. Create a new galaxy with the same name as the previous galaxy. Select the default_empty.cab type. Close the System Platform IDE. Copy the binaries saved from the previous version of AVEVA System Platform (from step 2) to: %ProgramFiles(x86)%\Common Files\ArchestrA\Framework\Bin Open aaSMC and restore the galaxy. 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: Import the App using the System Platform IDE by selecting Import from the Galaxy menu. Select AVEVA App. Select the folder containing the App to be imported. 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. 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

New features in Historian Client 2023 R2

Ad-Hoc expressions in Trend

Historian Client Desktop Trend control and its embedded ActiveX controls now support Ad-Hoc expressions. The Expression application and pane now appear in the Tag Picker with the Textbox editor.

For embedded ActiveX controls, scripting is supported for ad-hoc expressions in InTouch applications.

Ad-hoc expressions are supported with both SQL and REST connections.

Expanded ad-hoc expression functions

New functions added to ad hoc expressions make results simpler and more valuable.

Runtime language switching

Runtime language switching is supported for Trend Control, Query Control, Embedded control, and the Excel and Word ActiveX controls. It's supported for the following fields:

Description
EngineeringUnit
Message On/Message Off
Alias

If there is no value for the requested language for a field, the default language is used.

Improved Trend control for InTouch

Configuration is simplified for the Trend control within InTouch. The control is available in the graphic editor and can be placed in InTouch directly.

AVEVA Identity Manager Server login

Trend and Query support single sign-on authentication with AVEVA Identity Manager. This is restricted to REST-based connections and is not available for SQL-based connections.

Additional script functions for OMI Trend App and Graphic Editor support

The event tags TagAdded and TagRemoved have been added and are available at the Graphic level and in the HistoricalTrendApp control.

General performance improvements

Performance has been improved across the Historian Client controls.

Microsoft Office Historian Client Workbook improvements

The classic Historian Client Workbook add-in has been updated. Note the following:

Microsoft Office is optional. If you install Office after installing Historian Client, the Historian Client add-ins do not appear in the list of Office add-ins. Run the Historian Client installation program and repair the installation to load the Office add-ins.
When you perform a custom installation of Microsoft Office (32-bit), you must install Office Shared Features and Office Tools so that the Historian add-ins for Workbook or Report can be loaded.
Note: Make sure that you are not using the 64-bit version of Microsoft Office.

Tool for migrating from Historian Client Workbook to the newer Excel task pane add-in

The Excel Migration Tool updates Excel workbooks created in Historian Client Workbook to formulas compatible with the newer Historian Excel task pane add-in.

This tool is supported for files created in Excel 2016 or later.

For more details, see the Migrate data from Historian Client Workbook to the Excel add-in section in the AVEVA Historian Client User Guide.

Resolved issues in Historian Client 2023 R2

This release resolves the following issues:

Issue ID	Related Issues	SR/Case Number	Description
IMS-2868362		960348145	The Historian Client Trend MovingAverage retrieval style fails. The following warning message appears in the SMC log: "Error creating dataview: System.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near the keyword 'AND..."
IMS-2829074		960338977	Trend Client refresh does not work as expected.
IMS-1434259		960200215 960274781 960277990 960273174	The Servers.xml file was encrypted, so couldn't be shared between user profiles. To address this issue, now only the password is encrypted for SQL authentication. The non-sensitive information is no longer encrypted.
Bug-2600099			If servers.xml is upgraded from a previous version, the Historian Client Trend control crashes.
IMS-2616467		960329790	Setting a tag to a moving average in Historian Trend causes all other tag trends to disappear.
IMS-2599739	IMS-2590504	960322009	Windows that open from built-in buttons on the Trend App are not brought to the front.
IMS-2842698	IMS-2635827	960324888	When the the properties of an engineering unit are changed, the changes don't propagate to retrieval until the Historian services are restarted.
IMS-2510162		960305816	Unable to retrieve discrete live or historical values from Historian Client Query.
IMS-2602879	IMS-1500586	960327042	OMI times out when opening a window with Historian Client Trend.
IMS-2412412		960276859	HistClient 2023 VBA function ActiveFactoryWorkbook.Addserver fails with the error Runtime error 5, Invalid procedure call or argument.
IMS-2361029		960254917	ShowGraphic function to open an embedded Historian Client trend in the application from a saved aatrend file is very slow.
IMS-2447731	IMS-2426902 IMS-2457568 IMS-2473685	960284737	aaTrend & aaQuery client tool buttons are purple.
IMS-2468523		960293562	When using the Historical Trend App, if more than one instance is opened at a time, the settings affect each other.
IMS-2111271		960223078	When Start Date, End Date, or Duration is changed, Update To Current Time is enabled.
IMS-2221595		960244148	Historian Client (Query & Trend) “File” menu item not visible if the Format in the Regional settings is set different from “English (United States)”
IMS-2200586		960237237	Historian Client Trend application always prompts for unnecessary save dialog for last added trend
IMS-2260942		960249515	Historian Client aaTrendControl does not accept the Bottom value entered for Value Axis Range
IMS-2201698		960239189	The trend duration is not properly applied to trends in a trend set
IMS-2308959		960256488	Trend control buttons disappear when the control is used within InTouch Access Anywhere
			When using the Trend application on a tablet PC, the Annotate Chart and Annotate Application options are missing from the Tools menu.
IMS-2333570		960264275	When using the aaHistClientActiveDataGrid ActiveX control in InTouch with a SQL login, the control fails to connect to the server.