Known Issues and Limitations

Limitations

The following features available in Proficy Historian (on-premises) are not available in Proficy Historian for Cloud:
  • Messages and alerts.
  • Configuration Hub
  • Enumerated data sets, user-defined data types (UDTs), and array tags
  • Collector redundancy
  • Alarms and events archiver
  • Diagnostics Manager
  • Historian as an OPC HDA server
  • The Calculation collector, the Cygnet collector, the File collector, the iFIX Alarms and Events collector, the HAB collector, the ODBC collector, the OPC Classic Alarms and Events collector, the Server-to-Server distributor, and the Wonderware collector.
  • The Windows version of public REST APIs.

    Note that the Rest APIs supported for Proficy Historian for Cloud are Predix Timeseries-based REST APIs (that is, the REST Query service used in the Linux version of Proficy Historian); these APIs are different from the ones used by Proficy Historian (used on Windows).

In general, any features/components for which information is not available in the Proficy Historian for Cloud documentation are not supported.

In addition:
  • The performance of Historian Administrator when connected to Proficy Historian for Cloud is not good. We recommend using the Web Admin console, Excel Add-in for Historian, or the REST Query service instead of Historian Administrator.
  • Using the Server-to-Server collector, you can only send data from an on-premises Historian server to the Historian server deployed on cloud; you cannot send data if both the servers are on cloud.
  • You cannot back up and restore data using any of the clients. This is because the backup and restore functions are performed using Elastic File System (EFS).
  • Although you can install collectors on-premises or on an EC2 instance in a VPC, you cannot install the on-premises and cloud versions of collectors on the same machine. You can choose a different machine or uninstall the existing version of collectors.

Known Issues

Description Tracking ID
Regardless of the security group to which a user belongs, the user has full privileges to the Web Admin console. DE182555
The context-sensitive Help embedded in the Web Admin console provides information on unsupported features as well. For the most accurate information on the supported features for the Web Admin console, refer to About the Web Admin Console. DE182556
The uaa_config_tool utility displays NullReferenceException until you enter a command and begin using it. DE182557
If you try to change the destination of a collector from an on-premises Historian server to the cloud counterpart, an error occurs, stating, "Unable To Start the Collector Instance...Please check the parameters provided are valid and edit the Collector Instance...Press any key to exit the Application".

This issue occurs only if the collector name does not contain a prefix of the collector type.

Workaround:
  1. Access the registry entry for the collector instance.
  2. Rename the instance as follows, and close the registry: <collector type>-<original name of the instance>

    For example, if the instance name of a Simulation collector is sim1, rename it SimulationCollector-sim1.

    Use one of the following prefixes based on the collector type:
    • SimulationCollector-
    • OPCCollector-
    • OPCUACollector-
    • OPCHDACollector-
    • PiCollector-
    • PIDistributor-
    • iFixCollector-
    • ServerToServerCollector-
    • MQTTCollector-
  3. Change the destination of the collector instance. When asked for the name of the collector instance, provide the original name (without the prefix). In the case of the previous example, enter sim1.

    An error message appears, but it is expected; you can ignore it.

  4. Close the CloudHistorianConfigurationUtility.exe tool.
  5. Access the registry entry for the collector instance, and undo the changes you made in step 2 (that is, the collector instance should now contain the original name).
  6. Close the registry, and start the collector instance.
 DE184118