SCM Upload Instructions - Application Log Messages

Troubleshooting SCM > SCM Upload Instructions - Application Log Messages

The following topics explain messages that may appear in the Application Log for the eMessage Connector when an SCM package containing an Upload instruction is deployed to an eMessage agent asset:

• Asset delivery target not found (SCM Upload)

• Could not activate transfer job (SCM Upload)

• Delivery target must be in one of the following states (SCM Upload)

• File does not exist (SCM Upload)

• Instruction with ordinal # for package not found (SCM Upload)

• Invalid child path: Child path failed validation (SCM Upload)

• Invalid directory: Directory path contains encoded characters (SCM Uploadl)

• No relative paths are permitted (SCM Upload)

• No transfer job found for Upload (SCM Upload)

• Reservation submitted in metadata must be valid and external (SCM Upload)

• setDeliveryTargetState: Trying to update the state when already in a final state (SCM Upload)

• Target Repository is not a valid FileRepository or this user does not have permission to view it (SCM Upload)

• Target repository '"Target Repository" does not exist (SCM Upload)

• The filename, directory name, or volume label syntax is incorrect (SCM Upload)

• Thing "target repository" does not exist (SCM Upload)

• Transfer job associated with delivery target is inactive (SCM Upload)

• Unable to load data table entry - key does not exist (SCM Upload)

• Odd Behavior (SCM Upload)

◦ Same file included in uploaded archive multiple times (SCM Upload)

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".

Was this helpful?