AVEVA™ Historian 2023 Patch 03 Readme

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:

1. Shut down and disable the Historian.
2. Create a backup of the Runtime database.
3. Execute the following SQL script in the Runtime database, replacing the value of SFPath with the path to the folder where you want AutoSummary replication data to be stored:

   UPDATE _AutoReplicationServer

   SET SFPath = 'D:\Historian\StoreForward\LocalAutoSummaryReplication'

4. Enable and restart the Historian.

Issue

If you have configured replication to AVEVA Data Hub using AVEVA Historian 2023, the connection in AVEVA Data Hub will be listed as a legacy connection on the OMF Connections (Legacy) page. Legacy OMF connections are currently scheduled to stop working after April 30, 2023.

Workarounds

There are two workarounds:

The following workaround can be used whether or not this patch has been applied:

1. In the AVEVA Data Hub portal, locate your connection on the OMF Connections (Legacy) page, and migrate it to the OMF Connections page. For more details, see https://docs.aveva.com/bundle/data-hub/page/adh-content-portal-overview.html

The following workaround is available after applying this patch:

1. Locate the entry for your replication server in the OCMC.
2. Right-click and select Properties.
3. Select Register. Follow the prompts to re-register the connection to AVEVA Data Hub.

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.

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:

1. Shut down and disable the Historian.
2. Create a backup of the Runtime database.
3. Execute the following SQL script in the Runtime database, replacing the value of SFPath with the path to the folder where you want AutoSummary replication data to be stored:

   UPDATE _AutoReplicationServer

   SET SFPath = 'D:\Historian\StoreForward\LocalAutoSummaryReplication'

4. Enable and restart the Historian.

Issue

If you have configured replication to AVEVA Data Hub using AVEVA Historian 2023, the connection in AVEVA Data Hub will be listed as a legacy connection on the OMF Connections (Legacy) page. Legacy OMF connections are currently scheduled to stop working after April 30, 2023.

Workarounds

There are two workarounds:

The following workaround can be used whether or not this patch has been applied:

1. In the AVEVA Data Hub portal, locate your connection on the OMF Connections (Legacy) page, and migrate it to the OMF Connections page. For more details, see https://docs.aveva.com/bundle/data-hub/page/adh-content-portal-overview.html

The following workaround is available after applying this patch:

1. Locate the entry for your replication server in the OCMC.
2. Right-click and select Properties.
3. Select Register. Follow the prompts to re-register the connection to AVEVA Data Hub.

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.

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:

1. Shut down and disable the Historian.
2. Create a backup of the Runtime database.
3. Execute the following SQL script in the Runtime database, replacing the value of SFPath with the path to the folder where you want AutoSummary replication data to be stored:

   UPDATE _AutoReplicationServer

   SET SFPath = 'D:\Historian\StoreForward\LocalAutoSummaryReplication'

4. Enable and restart the Historian.

Issue

If you have configured replication to AVEVA Data Hub using AVEVA Historian 2023, the connection in AVEVA Data Hub will be listed as a legacy connection on the OMF Connections (Legacy) page. Legacy OMF connections are currently scheduled to stop working after April 30, 2023.

Workarounds

There are two workarounds:

The following workaround can be used whether or not this patch has been applied:

1. In the AVEVA Data Hub portal, locate your connection on the OMF Connections (Legacy) page, and migrate it to the OMF Connections page. For more details, see https://docs.aveva.com/bundle/data-hub/page/adh-content-portal-overview.html

The following workaround is available after applying this patch:

1. Locate the entry for your replication server in the OCMC.
2. Right-click and select Properties.
3. Select Register. Follow the prompts to re-register the connection to AVEVA Data Hub.

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.

Issue:

When the Historian runs out of disk space, an emergency shutdown is performed. After freeing space or specifying an alternate storage location, restarting the Historian may not correctly resume data acquisition.

Workaround:

1. Launch the Operations Control Management Console.
2. In the console tree, expand a server group and then expand a server.
3. Right-click Management Console, point to All Tasks, and then click Shutdown (and disable) Historian. A confirmation dialog appears.
4. Click OK, and wait for the shutdown process to complete.
5. Right-click Management Console, point to All Tasks, and then click Enable (allow to run) Historian. A confirmation dialog box appears.
6. Click OK, and wait for the Historian to be enabled.
7. If the Historian does not start automatically after being enabled, right-click Management Console and then click Start Historian.

Issue:

The Historian Search feature is used by the InTouch Web Client and OMI Web Client. If you install AVEVA Application Server or AVEVA InTouch on the same system as AVEVA Historian, and then later uninstall AVEVA Historian, the Historian Search feature is uninstalled, breaking some functionality.

Workaround:

Reinstall the Historian Search feature using one of the following methods.

Either:

• Reinstall AVEVA Historian, and then use the Configurator to configure the Historian Search feature.

or:

• Run the System Platform installation in repair mode, and then use the Configurator to configure the Historian Search feature.

Issue:

IDAS redundancy is no longer supported in AVEVA Historian version 2023. Any legacy IDAS already configured for failover can continue using the feature, but after connecting the IDAS to a Historian 2023 server, or upgrading the IDAS to version 2023, the failover configuration can no longer be modified through the management console.

Workaround:

To continue using IDAS redundancy, you can choose not to upgrade your existing IDAS to version 2023, or you can install an older version of the remote IDAS, such as version 2020 R2.

Then, to configure failover settings, run the following SQL script. Replace MyIDAS with the name of the IDAS node, and MyAltComputer with the name of the failover node:

UPDATE _IODriver

SET StoreForwardMode=0, Classic=1, AltComputerName='MyAltComputer'

WHERE ComputerName='MyIDAS'

After running the script, launch the Operations Control Management Console, right-click the Configuration Editor node for your Historian server in the console tree, and select Commit Pending Changes.

Issue ID

Related Issues

SR/Case Number

Description

IMS-612640

IMS-827279

960008509

Unable to authenticate replication server using an Active Directory user group.

IMS-1040483

After rebooting, the Historian is only licensed for 50 tags until the license is manually refreshed.

IMS-1135073

Historian 2020 SDK does not synchronize all tags, sometimes leaving tags in a pending state.

IMS-1112480

960041118

Attempting to import tag history values from a .CSV file fails. SQL Server reports "Arithmetic overflow error for data type tinyint" in the error message.

IMS-1225911

IMS-1388484

960070605

960064036

Historian Client Web tag search via description does not return the expected results.

IMS-1411912

IMS-1209531

960063741

Store/forward folders in redundant engines sometimes fail to synchronize and may also fail to forward to Historian.

IMS-1417655

960079593

Timeout error occurs while migrating alarms and events from A2ALMDB to history blocks using aahBlockMigrator.exe.

IMS-1514084

960111772

Replication stops working, with the following error message logged: RegisterTags encountered communication exception: System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages has been exceeded.

IMS-1527737

960108099

Application Server Engines indicate they are connected, but most tags are coming in as bad quality.

IMS-1502294

960103374

Slow changing tag shows 'NULL' value after restart of Historian, instead of the current value.

IMS-1536919

960050342

HCAL leaks memory when hosted in AppEngine.

IMS-597356

960015055

Unable to share Historian Client Web shortcut with team members.

IMS-1595100

960113247

Historian Client Web lists each item twice in the saved content list.

IMS-1575207

960099865

New HierarchicalName extended property entries take a very long time to populate.

IMS-1720972

960146566

History blocks deleted after performing time synchronization on the server.

IMS-1758406

960153744

Tier-1 does not replicate all the values to Tier-2, resulting in a NULL being recorded as the last value in Tier-2.

IMS-1840845

IMS-1927907

960168921

960187957

The aahEventStorage process consumes a large amount of memory while merging alarms.

IMS-1864791

960174868

Historian stops logging data from AppServer.

IMS-1747174

960150935

Trend Pen is unable to connect and display data.

IMS-1842786

960168027

Query using v_EventHistory doesn't return results for a specific user, but does for multiple users using wildcards.

IMS-1863235

960169310

Frequent crashing of the aahEventStorage.exe process.

IMS-1862162

960167599

Incorrect store/forward start value injected, causing a tag value from the previous day to be stored in error.