Monitoring and Troubleshooting the eMessage Connector > Troubleshooting the eMessage Connector > Exceptions Observed in the Log for the ThingWorx Platform > ThingWorx Exception 1: Invalid Thing token property
ThingWorx Exception 1: Invalid Thing token property
This exception appears if a Thing was communicating for a long time no longer appears to be communicating. A symptom could be that its lastConnected property is not updating or that expected data updates are not showing up. Note that if a Thing name is null, token authentication always fails.
For more information, refer to Observation 2: The lastConnection property of the Thing does not update and Observation 3: Asset that was communicating earlier, no longer communicates.
Here is the scenario that will result in this exception:
1. Start ThingWorx Platform.
2. Start eMessage Connector.
3. Create a Thing on the ThingWorx Platform, using the AxedaStandaloneModel Thing Template and set the token property to bogus.
4. Start an Axeda Connector agent that is configured to send data updates to the Connector.
In this scenario, ThingWorx Platform rejects the token sent by the agent or eMessage Connector and logs the following exceptions:
...
Unable to dispatch [ uri = /Authenticators/TokenPropertyAuthenticator/Services/ValidateToken/]:
Unable to Invoke Service ValidateToken on TokenPropertyAuthenticator : Tokens do not match.
...
error executing APIRequest Message:
Unable to dispatch [ uri = /Authenticators/TokenPropertyAuthenticator/Services/ValidateToken/]:
Unable to Invoke Service ValidateToken on TokenPropertyAuthenticator : Tokens do not match.,
sending ERROR ResponseMessage to caller!
Was this helpful?