Connector Exception 17: Start Connector with application key — No service invocation permission
If the logs for the eMessage Connector and ThingWorx Platform show pervasive messages that include “Not authorized for” and “Unable to invoke” errors, you have encountered this exception. For more information, refer to
Observation 16: Pervasive ‘Not authorized for’ and ‘Unable to Invoke’ Errors in the Connector and ThingWorx platform Logs.
The following steps generate this exception:
1. Start ThingWorx Platform.
2. Edit the configuration file of the Connector to use an application key for a non-Administrator user. This user must not have the run-time permission, Service Execute on the ConnectionServicesHub Thing Template.
3. Start eMessage Connector.
This scenario produces the following error message:
Error injecting constructor, com.Thingworx.connectionserver.protocol.services.
hub.HubChannelException: Unable to create Connection Server Hub Thing named
ConnectionServicesHub