Known issues

Description

If after installing SP2023 R2 SP1 Patch 03, the Add External Groups button in the Historian > Security settings of the Configurator is disabled (grayed out), relaunch the Configurator.

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

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.

In this situation:

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 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.

When the Historian node license mode is set to the connected experience and the Historian's REST connection is configured with the Require trusted connections (clients must trust this certificate) option, the Excel Add-In fails to load and does not function as expected.

If the Stream datatype of a replicated tag is changed and the change deployed, the tag is removed from the replication list and will not be updated in the next tier Historian, PI Server, and CONNECT Data Services.

The unmodified tag remains valid for data already stored in Historian, and cannot be deleted. Re-add the modified tag using a new destination tag name when replicating to PI Server and CONNECT Data Services. Re-add the modified tag with its existing destination tag name when replicating to a next tier Historian.