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
|
– |
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
|
– |
When importing AVEVA .NET Apps that use AVEVA Historian Client controls, some of the required files are not imported correctly. Workaround:
|
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. |
This document describes the resolved issues and known issues in AVEVA Historian 2023 R2 Patch 01. It also includes the entire AVEVA Historian 2023 R2 Readme after the Patch 01 Resolved Issues.
Known Issues
Issue ID |
Description |
– |
Issue The store and forward path for AutoSummary replication cannot be changed using the configurator or management console. Workaround The store and forward path for AutoSummary replication is stored in the _AutoReplicationServer table of the runtime database. Use the following steps to change the path:
|
– |
Issue Secure communication from Historian Client nodes to Historian server nodes may fail in workgroup setups with DNS enabled. This includes cloud-based environments such as Azure. Workaround In the hosts file on the Historian Client node, add an entry for the IP address of the the machine name (not the FQDN) of the Historian server. For example (where “10.x.x.x” is replaced with the IP address of your Historian server, and “HISTORIANSERVER1” is replaced with the name of that machine): 10.x.x.x HISTORIANSERVER1 |
Resolved Issues – 2023 R2 Patch 01
This patch resolves the following issues:
Issue ID |
Related Issues |
SR/Case Number |
Description |
---|---|---|---|
IMS-2966258 |
|
960343330 |
SQL Server memory consumption increases, and Historian queries take longer. |
IMS-2968797 |
|
960365321 |
Insight Publisher does not correctly publish discrete values from Intouch 2023 |
IMS-2997661 |
|
960373670 |
The in-program help doesn’t work. |
IMS-2982098 |
|
960370481 |
The Configurator fails with the message “Object reference not set to an instance of an object.” |
IMS-2895591 |
|
960355209 |
The auto summary backfill stalls. |
IMS-2996548 |
|
960373266 |
Each time a full reimport is executed, tagimporter increments the value by one for MaxEU and MaxRaw. |
IMS-3029223 |
|
960381994 |
ConfigStatusPending table is overruns the INT Size on the table identity. |
IMS-3281342 |
IMS-2997831 |
960407831 960372728 |
The time zone for analogsummary queries is not provided and is considered as local. |
IMS-3028192 |
|
960381805 |
In work group networks, when accessing Historian Client Web in SSO mode when Historian is configured with Flex license mode, the application loads in demo mode. |
IMS-3061742 |
IMS-3190476 |
960389860 |
Security has been enhanced in Historian Client Web. |
IMS-3103049 |
|
960386536 |
When configuring IDAS in the configurator, the user name and password fields aren’t editable. |
IMS-3188323 |
|
960387013 |
Line charts on the dashboard change to column charts for shared links. |
IMS-3238886 |
|
960399586 |
When running an “Average” retrieval query, it fails with an aaRetrieval access violation. |
IMS-2997831 |
|
960372728 |
The Minutely API (- /apis/Historian/v2/Tags(‘TagName’)/Minutely) shows the wrong start and end time. |
IMS-3289466 |
|
960410095 |
Queries on [Runtime].[dbo].[StringHistory] show deviating results. |
IMS-3309400 |
|
960410783 |
In Historian Client Web, when a URL includes tags, the content can’t be saved. When saving, the error “The content couldn’t be saved” occurs. |