Troubleshooting Issues with Collectors

This topic contains solutions/workarounds to some of the common issues encountered with Configuration Hub. This list is not comprehensive. If the issue you are facing is not listed on this page, refer to Troubleshooting the Historian Server.
Proxy Timeout Error While Adding a Collector Instance
Description
When you attempt to add a collector, sometimes, a proxy error appears even if the error occurs because of an API timeout.
Workaround
  1. Access the historian-httpd.conf file located at C:\Program Files\GE\Operations Hub\httpd\conf\app-specific.d.
  2. Increase the timeout value (for example, 250). If the timeout parameter is not available, enter it as follows: ProxyTimeout <value>
  3. Restart the Proficy Historian Tomcat Server and the Proficy Operations Hub Httpd Reverse Proxy services.
Unable to Use the Windows login User and Password During the Destination Historian Server Configuration When Adding a Collector Instance
Description
During Collector instance creation, for some reason, if you are unable to use the Windows login user and password during the Destination Historian server configuration, you can perform the following workaround.
Workaround
  • Edit the Password and UserName registries and add the predefined user, that is, <hostname>.admin and its password in the Collector Manager registry at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\GE DIGITAL\Historian Remote Management Agents\Collector Manager.
  • Check if the predefined user, that is, <hostname>.admin was added to the Local users & Group. If not, add the predefined user and its password to the Local users & Group. For more information on how to add a user to Local users & Group, refer to Adding Users to Windows Security Group.
Receiving a Collector Configuration Error
Description
A single ihConfigurationGetProperties[-2] error appears in the collector.LOG file.
Workaround
The error most likely occurred as a result of the collector connecting and querying for changes in the tag database immediately, getting a timeout, and then immediately querying again and succeeding.
Polled-based Collector performance improvements leading to "Load on source" and "Increase Overruns"
Description
From Historian 2022 onwards, the performance of polled-based collectors has been enhanced by introducing a higher number of polled threads, set to a default of 4, compared to the previous default of 1. While this enhancement has a positive impact on the collector performance, it may cause a decrease in performance on the source side due to increased load and also cause potential overruns. Therefore, if you are facing any performance issue on the source side, you can modify the number of polled threads using the following workaround.
Workaround
  1. Open Registry Editor.
  2. Create REG_NumPolledReadThreads as a new DWORD (32-bit) Value in the following registry paths, and then change its value to 1.

    32-bit collector registry path for Proficy products:

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Intellution, Inc.\iHistorian\Services

    32-bit collector registry path:

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

    64-bit collector registry path:

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

    For example,

    iFIX Collector

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Intellution, Inc.\iHistorian\Services\iFixCollector

    Simulation Collector

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GE Digital\iHistorian\Services\SimulationCollector

    OPC Collector

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intellution, Inc.\Historian OPC Collector

  3. Ensure to restart the corresponding collector.