Connector Exception 18: Unable to Invoke Service <service_name> on <Thing>
If you pervasive errors in the logs of the eMessage Connector and ThingWorx Platform that contain the words “Not authorized for” and “Unable to invoke”, 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 scenario generates this exception:
1. Start ThingWorx Platform.
2. Update the configuration of the Connector to use an application key for a non-Administrator user. The use must not have the full set of ThingWorx Permissions to execute Connector functionality.
3. Start the Connector.
4. Start an agent that polls and checks for download egress.
The solution to this issue is to add all the required permissions as mentioned in the topic,
Setting Up Permissions and Visibility for the eMessage Connector.
The following error messages are returned in this scenario:
...failureMessage=Throwable resulted from trying to get the ThingName
and Identifier for the eMessage device with modelNumber= and serialNumber=.
...Server returned an error with status STATUS_INTERNAL_ERROR and message:
Unable to dispatch [ uri = ...
Unable to Invoke Service GetThingNameAndIdentifierByModelAndSerial
on Emessage-cxserver- : Not authorized for ServiceInvoke on
GetThingNameAndIdentifierByModelAndSerial in Emessage-cxserver-
...