Last revision: 6/6/2024
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 |
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. |
--- End of 2023 R2 Patch 01 Readme ---
Latest revision: 12/15/2023
About This Readme
This Readme provides information about AVEVA Historian 2023 R2.
For information about using the product, see the AVEVA Historian documentation.
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 |
AVEVA Operations Control connected experience sign-on support
Historian supports the AVEVA Operations Control connected experience with AVEVA System Platform.
The server must be configured with an advanced license to retrieve data for expressions.
Note that the following still require Windows credentials:
Changes to default Historian communications protocol and ports
The Historian communications protocol has been updated. The port for the new protocol is 32565 by default. The previous port, 32568, is supported as a legacy port for connecting servers that are running older software that doesn’t support the new protocol.
Tier 1 Historians, AppEngines, and Platforms that support the new protocol and use the default 32568 port are updated automatically when the software is updated to the latest version. The local IDAS is also updated automatically. Existing connections that use legacy custom ports will need to be updated manually. External firewalls may need to be updated to allow connections on the new port.
Connecting servers that support the new protocol but are still using a custom legacy port will show as using the HCAL (Classic) protocol on the Data Acquisition page. (Note that connecting servers on older software will also use the HCAL (Classic) protocol. This is expected. Older software does not support the new protocol, and should still connect on the legacy port and use the classic protocol.)
If you have connecting servers that support the new protocol but still use the legacy port, the following warning appears once each hour in the Operations Control Logger:
The Historian Client Access Point running on XXX:XXX is an older version using a legacy protocol. Please update the port in the connection definition to point to the new Historian Client Access Point (port 32565 by default).
For more information, see the following sections in the Historian Administrator Guide:
Tags support multiple languages in Historian Client Web, Historian Client Query, and Historian Client Trend
You can now configure multiple translations for the same tag in Historian Client Web, Historian Client Query, and Historian Client Trend.
The language for these applications will be set automatically based on the operating system or browser language.
HTTPS-based communications
Internal Historian network communication is more secure and easily integrated with HTTP proxies.
Live data via iData
View latest historical values as the “live” values on OMI displays.
Alarm grid filter and sort in Historian Client Web
Browser-based alarm history in Historian Client Web supports more filtering and sorting options.
Historian Client Web / Excel integration
Easily transition from Historian Client Web charts to detailed analysis in Excel.
New look for Historian Client Web
The Historian Client Web interface is updated to be more powerful and easier to use.
Export / import Historian Client Web content
Include saved charts in CSV configuration import/export.
This release resolves the following issues:
Issue ID |
Related Issues |
SR/Case Number |
Description |
|---|---|---|---|
IMS-2633905 |
|
960334311 |
If an average() or total() expression includes cycles for which data is not yet available (typically cycles in the future, or cycles that are not available yet due to a network disruption), the cycles without data now won't impact the time-weighting of the last value. This resolves an issue where Total Expression returns an incorrect value for the current period. |
IMS-2638294 |
|
960333217 |
There is a one hour delay in the Alarms EventStamp (A2ALMDB). |
IMS-2637686 |
|
960326700 |
SQL query results are not filtered consistently depending on the order of AND statements. |
IMS-2482924 |
|
960296889 |
Rolling Sum chart doesn't display correctly when it's shared. |
IMS-2504652 |
|
960303657 |
Using aahBlockMigrator.exe to convert a2almcb results in the columns "operator" and "UserFullName" being swapped. |
IMS-2513233 |
IMS-2492540 |
960300539 |
There is an issue with the message events log in A2ALMDB when it's configured through the Configurator Utility. |
IMS-2489147 |
IMS-2455484 |
960264222 |
Endbound retrieval has an extremely long running time compared to startbound retrieval. |
IMS-2389867 |
IMS-2362433 |
960261473 |
An error shows in the configurator when configuring remote IDAS. |
IMS-2416708 |
IMS-2396761 |
960278834 |
Publisher fails during configuration with the error Invalid Value. The statement has been terminated. String or binary data would be truncated. |
IMS-2412336 |
|
960279736 |
IDAS Installation Conflict. |
IMS-2329328 |
|
960261568 |
Incorrect Values in Insight. |
IMS-2468109 |
IMS-2445491 |
960288997 |
Trends in Historian Client Web created prior to 2023 Patch 01 have color issues. |
IMS-2455226 |
|
960287532 |
AppEngine "Store forward threshold" doesn't prevent StoreForward block from growing. |
IMS-1984324 |
IMS-1974801 |
960174397 |
When alarms are migrated from alarm database to history blocks, the alarm duration field is not calculated correctly. |
IMS-2008742 |
|
960204912 |
CheckValue is NULL in v_AlarmEventHistory2 and v_EventHistory views when alarms and events are stored in history blocks. |
IMS-2046349 |
|
960211555 |
Retrieving data using OData in Power BI results in an error. |
IMS-2072197 |
|
960212595 |
Migrating a runtime database from AVEVA Historian 2012 R2 to the current version results in a failure. |
IMS-2094160 |
|
960220716 |
The Local Replication properties can't be edited. |
IMS-2164943 |
|
960229221 |
ValueCount changes significantly if query is for a time span longer then 5 hours. |
IMS-2178880 |
|
960234046 |
The path for xx:\Historian\StoreForward\LocalAutoSummaryReplication can't be edited via the user interface. |
IMS-2161218 |
|
960221324 |
Historian is one hour behind the System time. |
IMS-2181475 |
|
960237600 |
Migrating a runtime database from AVEVA Historian 2017 U3 SP1 to certain versions results in a failure. |
IMS-2086324 |
|
960218650 |
IDAS fails to configure after upgrading from AVEVA Historian 2020. |
IMS-2179860 |
IMS-2179861 |
960232900 |
URL-based charts always open to the status board. |
IMS-2204257 |
|
960223124 |
Retrieval using Integral with Auto Summary enabled produces errors. |
IMS-2254783 |
IMS-2138814 IMS-2178159 |
960228162 |
Certain queries cause a memory leak in aahStorage, resulting in performance issues and eventually a crash. |
IMS-2223710 |
|
960242318 |
Query with "Like" expression fails for certain History blocks. |
IMS-2136268 |
|
960209303 |
When replicating a large volume of tags, the extended properties don't replicate correctly. |
IMS-2290118 |
|
960209303 |
When replicating a large volume of tags, the error Main Metadata Server COM Exception caught, error = 38 occurred repeatedly. |
IMS-2198072 |
IMS-2164943 |
960229221 |
ValueCount changes significantly if a query is for a period longer than 5 hours. |
IMS-2311026 |
|
|
When automatic deletion of a history block is triggered by the Age Threshold setting, warnings and errors are recorded in the log. |
IMS-2866275 |
|
960347144 |
Historian replication is not possible for Data Hub and Insight using DMZ Secure Link. |
|
© 2015-2024 AVEVA Group Limited or its subsidiaries. All rights reserved. | Contact Us |