Known Issues and Limitations | Historian 2023 Documentation

Table 1. Known IssuesThe following issues are unresolved in this release.
Description	Tracking ID
You will be able to access Advance Configuration in Configuration Hub only with Historian 2023.	DE195195
The alarms show in the Alarms grid when the linked Data Collector is selected. However, the close alarm action does not work with Data Collector selection. Workaournd: Select the corresponding A&E Collector from the filter section. Select close alarm. The quality on all open alarmss will be set to bad.	DE194868
In some non-English operating Systems like German, when you try to upgrade Web clients to Historian 2023, you will see port conflicts that do not allow you to proceed. Workaround: Use Silent Installation to install the Historian Web components.	DE194621
In a Primary Mirror installation, all Proficy Authentication users who do not have the ihSecurityAdmins Windows Security group added to the Windows user, will encounter an error while accessing the System details in Configuration Hub. Users can proceed to perform other actions. There is no workaround.	DE194610
It is not possible to uninstall Historian Server 9.1 with Excel Add-in version 11.0. Workaround: Stop the services and delete the files (or) upgrade the server.	DE194363
While using the pre-built functions or insert function wizard, you cannot browse tags when the Calculation collector is running on a remote machine.	DE194325
Upgrading collectors to 2023 with Historian Server 9.1 causes opening issues with Historian Administrator and in accessing the System in Configuration Hub. Workaround: Upgrade the Historian Client Tools to 2023.	DE194063
When using the OPC UA collector on Windows Server 2022, you cannot browse tags when the OPC UA source is on the remote machine.	DE193985
Spare Fields Labels configured for a system will be lost when the system is added to another Configuration Hub.	DE193890
If you are upgrading from 2022 to 2023, once the Hab collector is instantiated, you need to manually create a registry entry SamplerID for this instance in the following registry. The datatype is String. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\GE Digital\iHistorian\Services\HabCollector\	DE193880
If you use an alias during the installation of the web-based clients, on the FQDN screen, the Historian Configuration Hub plugin fails to load. This is due to not having the respective certificates for aliases which validates the Configuration Hub plugin.	DE193789
After a Start or Stop action is performed, the Hab Collector's status takes some time to reflect on the Configuration Hub UI.	DE189053
If a SCADA (Habitat) system does not have MRID logics, then the user can use the Hab collector for data collection. However, the tags cannot be renamed or deleted /disabled automatically. Any tag is renamed in the SCADA system, then Hab collector will treat as a new tag instead of renaming.	DE185516
All Audited Actions performed from Configuration hub do not have the Username. There is currently no workaround.	DE182243
You cannot back up an archive at a command prompt using the following command: `ihArchiveBackup.exe -a <archive name>` However, this issue does not occur if the archive is associated with the default data store. Workaround: When you back up an archive, include the data store name as follows: `ihArchiveBackup.exe -d <data store name> -a <archive name>`	DE188825
After you upgrade Historian, the Historian Remote Collector Management Agent does not start automatically. Workaround: Restart the computer.	DE175062
If you install only Historian without installing iFIX, you may find some iFIX-related files in the C drive. You can ignore/delete them. If, however, you plan to install iFIX later, you must reinstall Historian Client Tools after installing iFIX.
If using Windows server 2022 or Window 11, you cannot connect to the Historian OPC UA HDA server using a remote OPC HDA client.	DE174953
If you install iFIX SCADA with the Historian server and Historian collectors on a remote machine using the iFIX integrated installer, then install License Client, and then uninstall Historian, an error message appears after you restart the machine and try to access iFIX.	DE174741
If you install iFIX SCADA with Historian Client Tools on a remote machine using the iFIX integrated installer, and then if you uninstall Client Tools, License Client is uninstalled as well.	DE174737
In a distributed node that is part of a mirror location, sometimes, you cannot back up an archive file. In addition, you cannot remove an archive file either from the primary node or a distributed node of a mirror location.	DE174808
If using a Historian web client or Historian Administrator of an older version with Historian 2022 server, you cannot perform actions on data stores or archives.	DE174355
If you are upgrading the Historian server on a passive node, an error message may appear behind the installer screen, stating that the Archives directory is not created. Workaround: You can ignore this message, or you can make the node active before upgrading the Historian server.
The OPC UA DA collector stops working for unsolicited tags after you disconnect and reconnect to the source.	DE135433
For a collector instance whose destination is Azure IoT Hub, you cannot restart the collector using the Save and Restart button in Configuration Hub. You cannot restart the collector using the Windows service either. Workaround: Use the Restart Collector API to restart the collector.	DE151454
After you delete a collector instance, the Windows service and the registry entry for the collector are not deleted. Workaround: Delete the Windows service and the registry entry manually.	DE151169
If the version of Historian collectors is different from that of Client Tools, ihSQL does not work. Workaround: Ensure that you have the same version of Client Tools and collectors.	DE149550
Using Configuration Hub, if you add a system by specifying its host name, and then add the same system by specifying its IP address, or vice versa, no validation error appears.	DE146366
When Configuration Manager is down, you cannot browse for tags in a horizontally scalable system.	DE141885
If you register the Configuration Hub plugin with a remote Configuration Hub container, the local instance of the connection is not unregistered. Workaround: Run the Web_Clients_Configuration_Tool.exe file located in the following folder: C:\Program Files\GE Digital\Historian Config In the Config Hub Configuration section, in the External Server name box, enter the local host name, and then select Unregister.	DE150907
If you install Configuration Hub and the Web Admin console on the same machine, and use self-signed certificates for both of them, the login page for Configuration Hub does not appear. Workaround: Disable the domain security policies: Access the following URL: chrome://net-internals/#hsts In the Domain Security Policy section, in the Delete domain security policies field, enter the domain name for Configuration Hub, and then select Delete.	DE151105
You cannot create multiple instances of the File collector on a single machine.	DE151715
Using Configuration Hub, you cannot restart an OPC collector whose destination is Azure IoT Hub. Workaround: Restart the collector from the Collectors section in Configuration Hub, modify the registry entry for the collector instance and restart manually, or restart the collector machine.	DE151454
When you change the destination of a collector from Historian to Predix TimeSeries, no success message appears although the destination is changed. In addition, the collector is not started automatically.	DE151859
Even after you uninstall collectors and Web-based Clients, the corresponding Windows services and registry entries are not removed.	DE151169
When you upgrade iFIX collectors to version 9.0, the custom registry folders are deleted.	DE151435
In Configuration Hub, for a stand-alone Historian system, when you select a server, the Diagnostics Manager service does not appear in the Details section.	DE151711
If you upgrade Historian from a version earlier than 8.1, by default, storing future data is enabled. Workaround: Stop the Historian DataArchiver service. Open Command Prompt with elevated privileges or administrator privileges. Navigate to the folder in which the ihDataArchiver_x64.exe file is located. By default, it is C:\Program Files\Proficy\Proficy Historian\x64\Server. Run the following command: `ihDataArchiver_x64 OPTION.<data store name> ihArchiverAllowFutureDataWrites 0`	DE149376
If you upgrade Historian server from a single-server installation to a primary mirror installation, and if you then add a distributed machine to the Historian system using Configuration Hub, you may see issues in connecting the distributed machine to the primary machine. Workaround: Restart all the Historian server services on Primary Mirror server and Distributed/Mirror server machine.	DE152582
In a horizontally scalable system, if Client Manager is down, Web-Based Clients do not failover to the other Client Managers in the system. And, the following error message appears in Web-Based Clients: Service call to central buffer server fail.	DE152830
In a horizontally scalable system, instead of adding a distributed machine, if you add a primary mirror machine or a monolithic (stand-alone) machine, no validation message appears, but causes issues later.	DE153191
If you upgrade Historian server to 9.0, the machine is restarted abruptly when the installation is still in progress. The installation will, however, resume after the machine is restarted.	DE151125
If you upgrade Historian server from a mirror system to a horizontally scalable system in 9.0, you cannot query data from the distributed machine when the distributed machine is removed from the DefaultMirror location.	DE152677
If you install iFIX on a machine that has Historian Web-based Clients, sometimes, the reverse proxy service stops working. Workaround: Restart the reverse proxy service - GE Operations Hub Httpd Reverse Proxy.	DE151157
If you reinstall collectors and Web-based Clients, the size of the Historian server and Web-based Clients appears as decreased in the Programs and Features page, although there is no functional impact.	DE152484
When you install Client Tools, incorrect installation pages appear, although the installation is successful. Workaround: Ignore the incorrect installation pages, and proceed with the installation of Client Tools.	DE153175
If you change the destination of a collector instance, the destination is not updated in the older machine, although the destination is updated in the new machine.	DE153176
When you attempt to fetch a list of OPC servers using the Get OPC Server API, an error occurs. This is applicable to the following OPC servers: OPC Data Access OPC Historical Data Access OPC Alarms and Events Workaround: Add collector instances using the RemoteCollectorConfigurator utility.	DE147276
Even if you install Web-based Clients using an alias name, you cannot access Configuration Hub using the alias name.	DE148939
While connecting to a remote Historian, you cannot add an instance of the File collector unless Client Tools are installed.	DE152330
After you install Client Tools in an iFIX system, the Configure Historian Server option is disabled in iFIX 6.5. Workaround: Reinstall Client Tools, and restart the machine.	DE149001
In Configuration Hub, for a horizontally scalable system, in the Collectors section, you cannot access an offline collector; a blank error message appears. Workaround: Ensure that the URI registry entry is the same for all the machines in a horizontally scalable system.	DE151380
If you upgrade collectors, an error occurs when you access Historian Administrator. Workaround: Install Client Tools.	DE151932
If you upgrade collectors, you cannot manage the OPC collectors. An error message appears in the CollectorManager.shw file. Workaround: Refer to Troubleshooting Remote Collector Management Issues.	DE151366
While installing Web-based Clients, after the connection to the external UAA is successful, if you change the UAA details, you can proceed to the next step even without testing the connection. Because of this, you will not be able to connect to the UAA server if the UAA details are incorrect (although you can install Web-based Clients). Workaround: Test the connection to the external UAA again, and only after the connection is successful, proceed to the next step.	DE155570
When you try to upgrade Web clients to Historian 2023, you will see port conflicts that do not allow you to proceed. Workaround: Use Silent Installation to install the Historian Web components.	DE194621
In a Primary Mirror installation, all Proficy Authentication users who do not have the ihSecurityAdmins Windows Security group added to the Windows user, will encounter an error while accessing the System details in Configuration Hub. Users can proceed to perform other actions. There is no workaround.	DE194610

You will be able to access Advance Configuration in Configuration Hub only with Historian 2023.

DE195195

The alarms show in the Alarms grid when the linked Data Collector is selected. However, the close alarm action does not work with Data Collector selection.

Workaournd: Select the corresponding A&E Collector from the filter section. Select close alarm. The quality on all open alarmss will be set to bad.

DE194868

In some non-English operating Systems like German, when you try to upgrade Web clients to Historian 2023, you will see port conflicts that do not allow you to proceed.

Workaround: Use Silent Installation to install the Historian Web components.

DE194621

In a Primary Mirror installation, all Proficy Authentication users who do not have the ihSecurityAdmins Windows Security group added to the Windows user, will encounter an error while accessing the System details in Configuration Hub. Users can proceed to perform other actions. There is no workaround.

DE194610

It is not possible to uninstall Historian Server 9.1 with Excel Add-in version 11.0.

Workaround: Stop the services and delete the files (or) upgrade the server.

DE194363

While using the pre-built functions or insert function wizard, you cannot browse tags when the Calculation collector is running on a remote machine.

DE194325

Upgrading collectors to 2023 with Historian Server 9.1 causes opening issues with Historian Administrator and in accessing the System in Configuration Hub.

Workaround: Upgrade the Historian Client Tools to 2023.

DE194063

When using the OPC UA collector on Windows Server 2022, you cannot browse tags when the OPC UA source is on the remote machine.

DE193985

Spare Fields Labels configured for a system will be lost when the system is added to another Configuration Hub.

DE193890

If you are upgrading from 2022 to 2023, once the Hab collector is instantiated, you need to manually create a registry entry SamplerID for this instance in the following registry. The datatype is String.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\GE Digital\iHistorian\Services\HabCollector\

DE193880

If you use an alias during the installation of the web-based clients, on the FQDN screen, the Historian Configuration Hub plugin fails to load. This is due to not having the respective certificates for aliases which validates the Configuration Hub plugin.

DE193789

After a Start or Stop action is performed, the Hab Collector's status takes some time to reflect on the Configuration Hub UI.

DE189053

If a SCADA (Habitat) system does not have MRID logics, then the user can use the Hab collector for data collection.

However, the tags cannot be renamed or deleted /disabled automatically. Any tag is renamed in the SCADA system, then Hab collector will treat as a new tag instead of renaming.

DE185516

All Audited Actions performed from Configuration hub do not have the Username. There is currently no workaround.

DE182243

You cannot back up an archive at a command prompt using the following command:

ihArchiveBackup.exe -a <archive name>

However, this issue does not occur if the archive is associated with the default data store.

Workaround: When you back up an archive, include the data store name as follows:

ihArchiveBackup.exe -d <data store name> -a <archive name>

DE188825

After you upgrade Historian, the Historian Remote Collector Management Agent does not start automatically.

Workaround: Restart the computer.

DE175062

If you install only Historian without installing iFIX, you may find some iFIX-related files in the C drive. You can ignore/delete them. If, however, you plan to install iFIX later, you must reinstall Historian Client Tools after installing iFIX.

If using Windows server 2022 or Window 11, you cannot connect to the Historian OPC UA HDA server using a remote OPC HDA client.

DE174953

If you install iFIX SCADA with the Historian server and Historian collectors on a remote machine using the iFIX integrated installer, then install License Client, and then uninstall Historian, an error message appears after you restart the machine and try to access iFIX.

DE174741

If you install iFIX SCADA with Historian Client Tools on a remote machine using the iFIX integrated installer, and then if you uninstall Client Tools, License Client is uninstalled as well.

DE174737

In a distributed node that is part of a mirror location, sometimes, you cannot back up an archive file. In addition, you cannot remove an archive file either from the primary node or a distributed node of a mirror location.

DE174808

If using a Historian web client or Historian Administrator of an older version with Historian 2022 server, you cannot perform actions on data stores or archives.

DE174355

If you are upgrading the Historian server on a passive node, an error message may appear behind the installer screen, stating that the Archives directory is not created.

Workaround: You can ignore this message, or you can make the node active before upgrading the Historian server.

The OPC UA DA collector stops working for unsolicited tags after you disconnect and reconnect to the source.

DE135433

For a collector instance whose destination is Azure IoT Hub, you cannot restart the collector using the Save and Restart button in Configuration Hub. You cannot restart the collector using the Windows service either.

Workaround: Use the Restart Collector API to restart the collector.

DE151454

After you delete a collector instance, the Windows service and the registry entry for the collector are not deleted.

Workaround: Delete the Windows service and the registry entry manually.

DE151169

If the version of Historian collectors is different from that of Client Tools, ihSQL does not work.

Workaround: Ensure that you have the same version of Client Tools and collectors.

DE149550

Using Configuration Hub, if you add a system by specifying its host name, and then add the same system by specifying its IP address, or vice versa, no validation error appears.

DE146366

When Configuration Manager is down, you cannot browse for tags in a horizontally scalable system.

DE141885

If you register the Configuration Hub plugin with a remote Configuration Hub container, the local instance of the connection is not unregistered.

Workaround:

Run the Web_Clients_Configuration_Tool.exe file located in the following folder: C:\Program Files\GE Digital\Historian Config
In the Config Hub Configuration section, in the External Server name box, enter the local host name, and then select Unregister.

DE150907

If you install Configuration Hub and the Web Admin console on the same machine, and use self-signed certificates for both of them, the login page for Configuration Hub does not appear.

Workaround: Disable the domain security policies:

Access the following URL: chrome://net-internals/#hsts
In the Domain Security Policy section, in the Delete domain security policies field, enter the domain name for Configuration Hub, and then select Delete.

DE151105

You cannot create multiple instances of the File collector on a single machine.

DE151715

Using Configuration Hub, you cannot restart an OPC collector whose destination is Azure IoT Hub.

Workaround: Restart the collector from the Collectors section in Configuration Hub, modify the registry entry for the collector instance and restart manually, or restart the collector machine.

DE151454

When you change the destination of a collector from Historian to Predix TimeSeries, no success message appears although the destination is changed. In addition, the collector is not started automatically.

DE151859

Even after you uninstall collectors and Web-based Clients, the corresponding Windows services and registry entries are not removed.

DE151169

When you upgrade iFIX collectors to version 9.0, the custom registry folders are deleted.

DE151435

In Configuration Hub, for a stand-alone Historian system, when you select a server, the Diagnostics Manager service does not appear in the Details section.

DE151711

If you upgrade Historian from a version earlier than 8.1, by default, storing future data is enabled.

Workaround:

Stop the Historian DataArchiver service.
Open Command Prompt with elevated privileges or administrator privileges.
Navigate to the folder in which the ihDataArchiver_x64.exe file is located. By default, it is C:\Program Files\Proficy\Proficy Historian\x64\Server.

Run the following command:

ihDataArchiver_x64 OPTION.<data store name> ihArchiverAllowFutureDataWrites
                    0

DE149376

If you upgrade Historian server from a single-server installation to a primary mirror installation, and if you then add a distributed machine to the Historian system using Configuration Hub, you may see issues in connecting the distributed machine to the primary machine.

Workaround: Restart all the Historian server services on Primary Mirror server and Distributed/Mirror server machine.

DE152582

In a horizontally scalable system, if Client Manager is down, Web-Based Clients do not failover to the other Client Managers in the system. And, the following error message appears in Web-Based Clients: Service call to central buffer server fail.

DE152830

In a horizontally scalable system, instead of adding a distributed machine, if you add a primary mirror machine or a monolithic (stand-alone) machine, no validation message appears, but causes issues later.

DE153191

If you upgrade Historian server to 9.0, the machine is restarted abruptly when the installation is still in progress. The installation will, however, resume after the machine is restarted.

DE151125

If you upgrade Historian server from a mirror system to a horizontally scalable system in 9.0, you cannot query data from the distributed machine when the distributed machine is removed from the DefaultMirror location.

DE152677

If you install iFIX on a machine that has Historian Web-based Clients, sometimes, the reverse proxy service stops working.

Workaround: Restart the reverse proxy service - GE Operations Hub Httpd Reverse Proxy.

DE151157

If you reinstall collectors and Web-based Clients, the size of the Historian server and Web-based Clients appears as decreased in the Programs and Features page, although there is no functional impact.

DE152484

When you install Client Tools, incorrect installation pages appear, although the installation is successful.

Workaround: Ignore the incorrect installation pages, and proceed with the installation of Client Tools.

DE153175

If you change the destination of a collector instance, the destination is not updated in the older machine, although the destination is updated in the new machine.

DE153176

When you attempt to fetch a list of OPC servers using the Get OPC Server API, an error occurs. This is applicable to the following OPC servers:

OPC Data Access
OPC Historical Data Access
OPC Alarms and Events

Workaround: Add collector instances using the RemoteCollectorConfigurator utility.

DE147276

Even if you install Web-based Clients using an alias name, you cannot access Configuration Hub using the alias name.

DE148939

While connecting to a remote Historian, you cannot add an instance of the File collector unless Client Tools are installed.

DE152330

After you install Client Tools in an iFIX system, the Configure Historian Server option is disabled in iFIX 6.5.

Workaround: Reinstall Client Tools, and restart the machine.

DE149001

In Configuration Hub, for a horizontally scalable system, in the Collectors section, you cannot access an offline collector; a blank error message appears.

Workaround: Ensure that the URI registry entry is the same for all the machines in a horizontally scalable system.

DE151380

If you upgrade collectors, an error occurs when you access Historian Administrator.

Workaround: Install Client Tools.

DE151932

If you upgrade collectors, you cannot manage the OPC collectors. An error message appears in the CollectorManager.shw file.

Workaround: Refer to Troubleshooting Remote Collector Management Issues.

DE151366

While installing Web-based Clients, after the connection to the external UAA is successful, if you change the UAA details, you can proceed to the next step even without testing the connection. Because of this, you will not be able to connect to the UAA server if the UAA details are incorrect (although you can install Web-based Clients).

Workaround: Test the connection to the external UAA again, and only after the connection is successful, proceed to the next step.

DE155570

When you try to upgrade Web clients to Historian 2023, you will see port conflicts that do not allow you to proceed.

Workaround: Use Silent Installation to install the Historian Web components.

DE194621

In a Primary Mirror installation, all Proficy Authentication users who do not have the ihSecurityAdmins Windows Security group added to the Windows user, will encounter an error while accessing the System details in Configuration Hub. Users can proceed to perform other actions. There is no workaround.

DE194610