ThingWorx Exception 5: Start eMessage Connector with application key that does not exist on the ThingWorx Platform
This exception appears if eMessage Connector starts with an application key that does not exist on the ThingWorx Platform.
Here is a scenario that will result in this exception:
1. Update the configuration settings of eMessage Connector to use an application key that does not exist on the ThingWorx Platform.
2. Start eMessage Connector.
In this scenario, authentication fails and eMessage Connector does not start. The error message shows the cause:
...
Error [authenticating connection], Server websocket will be closed.
cause: Application key not found
...
To resolve this situation, check that the app-key that is specified in the emessage-ha-sample.conf file is valid. An administrator can create a new Application Key if required. That is specified in the emessage-ha-sample.conf file is valid. An administrator can create a new application key if required.