Troubleshooting Remote Collector Management Issues

Remote Collector Management does not work

Issue: If an iFIX collector instance created in version 9.0 exists, after you upgrade collectors, another instance of the iFIX collector is created. Because of this, the Remote Collector Manager (RCM) will not work correctly. This is applicable to the iFIX Alarms and Events collector as well.

Workaround: If you want to use RCM, you must delete one of the instances. If needed, you can manually create another instance of the iFIX collector using Configuration Hub or the RemoteCollectorConfigurator utility.

The ServiceName Registry Key is not Updated

Issue: When you attempt to manage collectors, sometimes, an error message appears in the CollectorManager.shw file.

Error message: Below are collectors in the registry without a service name. The String Registry value 'ServiceName' exists, but is blank. Collector Manager will not try to determine what the service name is. This will need to be manually configured.

Cause: When Remote Collector Management is started for the first time, the collector that you want to manage is not running. When this happens, the ServiceName registry key is not updated.

Workaround:
  1. Stop the Remote Collector Management service.
  2. Start the collector.
  3. Start the Remote Collector Management service.

The ServiceName Registry key is Updated Incorrectly

Workaround:
  1. Stop the Remote Collector Management service.
  2. Access the registry folder of the collector.
  3. Delete the ServiceName key.
  4. Start the collector.
  5. Start the Remote Collector Management service.
  6. Access the .shw file to verify that the ServiceName key has been updated.