Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Historian

About this Readme - 2023 R2 Patch 01

  • Last UpdatedApr 16, 2024
  • 1 minute read

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:

  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

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

In This Topic
TitleResults for “How to create a CRG?”Also Available in