Troubleshooting the eMessage Connector

Monitoring and Troubleshooting the eMessage Connector > Troubleshooting the eMessage Connector

The Axeda Gateway and Connector agents do not have one flag to operate in debug mode. Rather, each component of the agents can be set to run in debug mode. For example, the SoftwareManagement (ESM or xgSM) can be set to run in debug mode in Axeda Builder. Alternatively, you can add the following flag to the configuration file for the component (xgSM.xml or ESM.xml):

Other components that you may want to run in Debug mode include the EnterpriseProxy component that manages communications between the agent and the destination platform, EEnterpriseProxy or xgEnterpriseProxy. You can also set up the WebClient component to run in Debug mode from Builder. If you are troubleshooting problems such as data items sent to the destination, put the EnterpriseProxy and Logger components in Debug mode.

The following topics provide troubleshooting information for events and error messages as well as scenarios for common problems and assistance for error messages that you may find in the log for the eMessage Connector or in the log for the ThingWorx Platform.

• Event Notifications

◦ Invalid Data Item Type Event (ProtocolError)

◦ Event: Identifier Used as Name of a Thing (UserError)

• Missing Root or Intermediate Certificates

• Resetting a Token

• Invoking ClearCacheEntry for the ThingNameStash

• Capturing Thread Dumps

• Correcting SSL certificate CN to contain the correct host name

• Issues when eMessage Connector is run by a Non-Administrator User

• Scenarios for Common Problems

• Exceptions Observed in the Log for eMessage Connector

• Exceptions Observed in the Log for the ThingWorx Platform