About this Readme - 2023 R2 SP1

Issue ID

Description

-

In the Historian Database Export/Import Utility, an error occurs when importing a database file from Historian SP2023 R2 or earlier with saved content or dashboards.

Workaround

To import a Historian database file with saved content or dashboards, update the Historian from which the file is being exported to SP2023 R2 P01 or later.

-

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.

-

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

-

When two assets with the same contained name are pushed to PI, only one asset is shown.

Workaround

If two assets have the same contained name, rename one of them before pushing to PI.

-

In the Historian Web Client modern look, when adding a comment to a line chart, the Asset field in the Add Comment dialog does not function.

Due to recent Microsoft updates, users may experience issues with Excel Add-In custom functions in 2023 R2 SP1.

Workaround

Choose one of the workarounds below based on your configuration of Historian:

When Historian is configured with option: "Favor trusted connections permit untrusted connection" in Rest Configuration:

5. Install Historian and configure with "Favor trusted connections permit untrusted connection" in Rest Configuration.

6. After configuration, navigate to the folder C:\ProgramData\Historian\InsightAddIn

7. Open the file named Insight_OnPrem_Office_Addin_<SERVERNAME>.xml with Notepad.
   For example, if the Historian server name is “SNRN1”, the file you're looking for would be named Insight_OnPrem_Office_Addin_SNRN1.xml.

8. Search (CTRL + F) for "VersionOverridesV1_1" in the file and replace (CTRL + H) it with "VersionOverridesV1_0".

9. Replace all instances (CTRL + H) of http://<SERVERNAME>:<HTTP Port> with https://<SERVERNAME>:<HTTPS Port>.

   1. Update the ports according to Historian’s REST configuration.
      For example, replace http://SNRN1:32569 with https://SNRN1:32573.

10. Save the file.

NOTE: Do not modify entries in AppDomains section, such as: “<AppDomain>http://localhost:32569</AppDomain>”.

When Historian is configured with option: "Require trusted connections (Clients must trust this certificate)" in Rest Configuration:

11. Install Historian and configure with "Require trusted connections (Clients must trust this certificate)" in Rest Configuration.

12. After configuration, navigate to the folder C:\ProgramData\Historian\InsightAddIn.

13. Open the file named Insight_OnPrem_Office_Addin_<SERVERNAME>.xml with Notepad.
    For example, if the Historian server name is “SNRN1”, the file will be named Insight_OnPrem_Office_Addin_SNRN1.xml.

14. Search (CTRL + F) for "VersionOverridesV1_1" in the file and replace (CTRL + H) it with "VersionOverridesV1_0".

15. Save the file.

NOTE: Do not modify entries in AppDomains section, such as: "<AppDomain>http://localhost:32569</AppDomain>"