SCM Upload Instructions — Delivery Target Status Messages
Delivery Target Status Messages fall into two categories: generic status and eMessage agent-specific status. Since they are displayed in the SCM Extension user interface for the status of deployments, the generic status messages are described in the section, Managing Assets > ThingWorx Software Content Management (Admin Only), of the ThingWorx Utilities Help Center. The table below lists the eMessage agent-specific messages, their meaning, and possible root cause(s).
 |
There are many error messages from the eMessage Agents. If you do not see the error message you are looking for, refer to the user guide for your Axeda Agent. The chapter, "Monitoring Devices and Troubleshooting the Agent," has tables of error and status messages. For SCM, there is a section called, "Agent-Generated Package Status Codes".
|
|
Status Message
|
Meaning
|
Possible Root Cause (s)
|
|---|---|---|
|
ec = 9
|
An Axeda agent reported an error about the upload files.
|
An explicitly named file in an upload instruction
|
|
ec = 10
|
An Axeda agent reported an error about the upload files.
|
An explicitly named file in an Upload instruction (no wildcards) does not exist on the agent machine.
|
|
ec = 12
|
An Axeda agent reported an error about the upload files.
|
The Axeda agent does not have sufficient permissions to a file that is requested in an Upload instruction.
|
|
ec = 14, x = 404
|
An Axeda agent reported that it received an unexpected HTTP status code.
|
The wrong path is specified for eMessage agents to use for uploads in the following property of the configuration file for the eMessage Connector:
cxserver.emessage.file-transer.upload.url
|
|
ec = 14, xc = 500
|
An Axeda agent reported that it received an unexpected HTTP status code.
|
There are many potential root causes for this message. If this error appears, additional log entries in the Application Log can help. Refer to SCM Upload Instructions - Application Log Messages for more information about errors in the Application Log. Alternatively, consult the log of the eMessage Connector for any related error messages.
|
|
ec = 16, xc = 4
|
An Axeda agent reported that a network error occurred.
|
During the upload the Axeda agent was disconnected from the eMessage Connector for a period of time that was long enough that the agent exhausted all of its agent-side retries and could not upload the file.
|
|
ec = 16, xc = 9
|
An Axeda agent reported that a network error occurred.
|
The wrong host or port is specified for the eMessage agents to use for uploads in the following property in the eMessage Connector configuration file (emessage.conf):
cxserver.emessage.file-transer.upload.url
|