Here are some of the most common reasons why the Hyperview data collector is failing to register to the Hyperview application.

The registration token from the application hasn't been saved.

When you click the add data collector button in Hyperview a pop-up window will appear that provides you with a registration token that must be copied into the data collector configuration tool. If the pop-up window is not closed by clicking the OK button before registering the data collector, then the registration will fail.

The registration token from the application has expired.

When a registration token is generated by the Hyperview application, it is only active for a 72 hour period. If that registration token has expired prior to attempting to use it to register a data collector, then the registration will fail.

The HTTPS advanced setting is toggled incorrectly.

Open advanced options in the Hyperview data collector configuration tool and ensure that use https is toggled on / off depending on the URL of your Hyperview instance. A default Hyperview instance will use HTTPS.

The Firewall rules have not been configured.

In order for the data collector to communicate to the Hyperview instance, the firewalls must be configured in the environment to allow that network traffic over the various ports. By default a Hyperview instance will use HTTPS which requires TCP port 443 to be open. If the Hyperview instance has been configured as HTTP, then TCP port 80 would need to be allowed.

The proxy settings have not been configured.

Check to see if you are using a network proxy script, service, or server. If you are, then configure the proxy settings in the data collector configuration tool advanced options.