Monitoring and Troubleshooting the eMessage Connector > Troubleshooting the eMessage Connector > Exceptions Observed in the Log for the ThingWorx Platform > ThingWorx Exception 6: Start eMessage Connector with an application key that does not have service invocation permission
ThingWorx Exception 6: Start eMessage Connector with an application key that does not have service invocation permission
This exception appears if a user tries to start the eMessage Connector with an application key that does not have appropriate permissions on the Connection Services Hub of 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 for a non-administrator user that does not have Run Time Instance Permission for Service Execute on the ConnectionServicesHub Thing Template.
2. Start eMessage Connector.
In this scenario, the user is not authorized to start eMessage Connector. The following error is logged:
Unable to Invoke Service GetMetadata on ConnectionServicesHub :
Not authorized for ServiceInvoke on GetMetadata in ConnectionServicesHub
...error executing APIRequest Message: Unable to dispatch [ uri = ... ]:
Unable to Invoke Service GetMetadata on ConnectionServicesHub :
Not authorized for ServiceInvoke GetMetadata in ConnectionServicesHub,
sending ERROR ResponseMessage to caller!
...
Was this helpful?