Monitoring and Troubleshooting the eMessage Connector
>
Troubleshooting the eMessage Connector
> Scenarios for Common Problems
Scenarios for Common Problems
Follow the links below to view the possible actions that an end user and/or an administrator can take to resolve these issues:
•
Observation 1: eMessage Connector does not show up on the Monitoring > Connection Servers page
•
Observation 2: The lastConnection property of the Thing does not update
•
Observation 3: Asset was communicating earlier, but now it does not communicate
•
Observation 4: Data items sent by the asset do not reach ThingWorx Platform
•
Observation 5: Alarms sent by the asset do not reach ThingWorx Platform
•
Observation 6: Events sent by the asset do not reach ThingWorx Platform
•
Observation 7: Agent-initiated file uploads do not reach ThingWorx Platform
•
Observation 8: Platform-initiated file uploads do not reach ThingWorx Platform
•
Observation 9: Platform-initiated file downloads are not downloaded by asset
•
Observation 10: The asset never appears connected to the ThingWorx Platform
•
Observation 11: Connector stops processing agent messages completely
•
Observation 12: Connector websocket connection errors with ThingWorx Platform
•
Observation 13: Connector does not start due to full disk
•
Observation 14: ThingWorx platform stops responding to connector SDK (websocket) requests
•
Observation 15: Old Gateway Agents (5.3.1) cannot ping the Connector
•
Observation 16: Pervasive ‘Not authorized for’ and ‘Unable to Invoke’ Errors in the Connector and ThingWorx Platform Logs
•
Observation 17: Connector fails to start due to invalid keystore password
•
Observation 18: Connector fails to start due to missing keystore file
Related Topics
Troubleshooting the eMessage Connector
Exceptions Observed in the Log for eMessage Connector
Exceptions Observed in the Log for the ThingWorx Platform
Was this helpful?
This site works best with JavaScript enabled