Data Expedition, Inc. ®

Move Data Faster

Support

Support
Tech Notes
Reference
Error Messages
Application Security
Files Used By DEI
Registration Errors
Transport Integrity
Calculators

Application Security

Page Index:
Format
Network
MTP/IP
Application
DOC
SEQ
Tech Note History
Mar282011Updated for 3.15
Jun032010Updated for 3.14
Jun262009Updated for 3.13.6
Numerical Values
Dec222008Updated for 3.13.4
Dec042008Clarifications
Oct222008First Post MTP 3.13.2

MTP/IP Error Messages

All MTP/IP software products share a core set of error messages related to common network and application tasks.  The following index provides a quick reference for what these may indicate.  Please refer to the product pages and their manuals for application specific information.

Note that this information applies to MTP version 3.15.0 and later.  Earlier versions may differ.  For instructions on how to determine the MTP version of your software, see tech note 0001.

Numerical Codes

The MTP/IP software development kits and some application logs use a pair of numbers to indicate error conditions.  The first number, called the error class, is a positive or negative integer indicating the origin of the error.  The second number, called the error code, gives the specific error within that class.  The numerical values are defined in the mtp.h file of the MTP Core SDK, and are also given below for the latest MTP/IP release.

Error Text

Standard MTP/IP errors are usually presented as human readable text strings.  The text describes the source of the error, followed by a description of the error, in the following format:

<Local|Remote> <Type>: <Message>

The first element indicates whether the message was generated by software on the local system, or software running remotely.  This corresponds to a negative or positive numerical error class.

 - Local
The message was generated by the local software that is reporting it.
 + Remote
The message was generated by remote software across the network.  Note that receipt of a remote message indicates that there was at least enough network connectivity for the error message to get through.

The second element indicates the type of error.  This corresponds to the absolute value of the error class.

 2 Network
The error was generated by ICMP or the operating system in relation to a network operation.
 3 MTP
The error was generated by Core MTP/IP
 4 Application
The error was generated by another SDK or the parent application.

The third element shows the error message.  The numerical error code for the message depends on the class.  For example:

Local Network: No Response

This corresponds to an error class of -2 and an error code of 7.

Common MTP/IP error messages may be accompanied by additional details describing exactly what happened or what to do about it.  It is vital that you record all error text and logs when requesting technical support.

Network Errors

Error class 2 indicates a problem reported by a network device or an operating system network related function.  Most indicate a problem with routing or connectivity.  ICMP related errors are reported as Local if the ICMP message was received locally and as Remote if the ICMP message was received at the remote host.

 0 Unspecified
No specific error message was given.
 1 Insufficient Privileges
The process did not have sufficient access rights to perform an operation.
 2 System Call
A low-level operating system function failed.
 3 Memory Fault
A memory fault occurred while reading or writing data on the network.
 4 Datagram Too Large
The operating system truncated an outgoing datagram.
 5 Buffer Overflow
A network buffer overflowed.
 6 Unable to Allocate
MTP ran out of memory while trying to deliver network data.
 7 No Response
Network connectivity appears to be down or lost.  This may be caused by firewall or routing issues.  At the start of a transaction, this may indicate that the remote address is wrong or is not running MTP/IP software.  If this occurs during a transaction, it likely indicates that the network or remote host has gone down.  See Tech Note 0009 for a list of network devices which can affect connectivity.
 8 Invalid Address
An IP address is not in a valid format.
 9 Invalid Port
A port number is out of range.
13 Host Down
An ICMP "Host Down" message was received.  This likely indicates that the peer system is turned off or not online, or that the IP address being used is not correct.  It can also indicate a routing problem, particularly if NAT port mapping is being used.
14 No Application at Given Port
An ICMP "Port Down" message was received.  This likely means that the peer application was not started or has quit.  It may also indicate that the IP address or port number are incorrect.  If NAT port mapping is being used, it could indicate a routing or port mapping problem.
10 ICMP Redirect
11 TTL Exceeded
12 Network Down
15 ICMP Need Frag
16 ICMP Net Unknown
17 ICMP Host Unknown
18 ICMP Prohibited
19 Other ICMP Error
These rare ICMP errors may indicate a network routing or connectivity problem.
20 Slow Down
A network device has requested that MTP/IP reduce its speed.  MTP/IP will treat this the same as a packet loss or network congestion event.

MTP/IP Errors

Error class 3 is generated by the MTP/IP Core Software Development Kit.  Most indicate either a problem with the application or an incompatibility between different application versions.

 0 Unspecified
No specific error message was given.
 1 Invalid Parameter
An MTP/IP function was called with invalid parameters.
 2 System Call
An operating system function returned an unexpected error.
 3 Invalid Action
The remote application did not support a requested action.  This may indicate incompatible software versions.
 4 Bad Delivery Target
A data source or destination could not be accessed.  This may be caused by filesystem errors (such as disk full), memory exceptions, or a problem with the application.
 5 Response Too Large
A data response was larger than supported for the given delivery target.  MTP/IP supports memory buffers up to 1 terabyte, files up to 8 exabytes, and dynamic data streams up to 16 exabytes.
 6 Feature Not Supported
The remote application did not support a requested action.  This may indicate incompatible software versions.
 7 Insufficient Resources
MTP/IP ran out of internal resources.  This usually indicates that the number of concurrent transactions exceeds the licensed capacity of the software.  Contact DEI for assistance.
 8 Request Too Large
The amount of data in a request exceeded MTP's capacity to deliver it.  This may happen if some element of your transaction is very large, such as a very long pathname.
 9 Protocol Violation
This may indicate that another application is attempting to send data to the same UDP port that MTP/IP using.
10 Checksum Failure
A packet checksum was invalid.
11 Re-entry Violation
The application attempted to access the MTP/IP library in a manner not permitted.
12 Not Initialized
The application tried to use MTP/IP before the library was initialized.
13 Transaction Aborted
A transaction ended because the application requested that it be aborted.
14 Transaction Paused
A transaction is currently paused and may be resumed later.
15 Invalid License Code
A license code was required, but the proper one was not given.  Check that your software is using the correct license code.  See Tech Note 0027 for details about license registration errors.
16 Invalid License Configuration
A valid license code was given or not required, but the license configuration is not valid for this hardware.  Make sure that you are using the correct license code for the software and hardware that you are using.  See Tech Note 0027 for details about license registration errors.
17 Encryption Error
A problem occurred while trying encrypt or decrypt data.
18 Internal State Error
An internal MTP problem occurred, likely indicating a bug.
19 License Expired
A trial or temporary license has expired.  See Tech Note 0027 for details about license registration errors.

General Application Errors

Error class 4 is used by MTP/IP applications to describe general error conditions.  They will usually be accompanied by descriptive text that provides more details specific to the application.  Additional error messages, not included here, may be reported by other SDKs or applications.  See the individual product documentation for details.

 0 Unspecified
No specific error message was given.
 1 Unknown
An unexpected error occurred.
 2 Unknown Action
An unsupported action was requested.  This may indicate incompatible software versions.
 3 Invalid Object ID
The state of a transaction has been lost. 
 4 Invalid Flag
An unsupported feature was requested.  This may indicate incompatible software versions.
 5 Invalid Address
An attempt was made to access data out of bounds.
 6 Invalid Object Description
A request could not be understood.
 7 End of Data (Address Beyond Object Size)
An attempt was made to access data out of bounds.  This may indicate that a file shrank while it was being read.
 8 Object Too Large
The data being transferred is larger than the application supports.  MTP/IP supports memory buffers up to 1 terabyte, files up to 8 exabytes, and dynamic data streams up to 16 exabytes.  However, individual applications may have smaller limits.
 9 Object Unavailable
An error occurred while trying to access an object.
10 Bad Credentials, Username, or Password
An authentication error occurred, probably due to an invalid username or password.  Verify that the credentials are correct and that the server software is configured to check the appropriate authentication sources.  See the product documentation for details.
11 Object Busy: Try again later
A server resource could not be accessed because something else is using it.  This may indicate an attempt to access a file that is in use by another process or transaction.
12 Waiting for Server: Will Keep Trying
The transaction has been paused, probably while waiting for data to be generated or for the user to respond to a prompt.
13 Operation Timed Out
It has been a long time since there was any activity on a transaction, so it has been abandoned.  This usually indicates a network connectivity or firewall problem.  See Tech Note 0002 for information about configuring firewalls.
14 Condition Not Met
A conditional request failed because the condition was not met.
15 Redirect to a Different Sever
The transaction should be repeated at a different address.
16 Duplicate Transaction
The requested transaction duplicates an earlier state-dependent transaction.
17 Unsupported Version
The application versions are not compatible.
18 Invalid Argument
An internal function or transaction did not provide proper parameters.
19 Skip Data
A portion of the requested data is not available, but the rest may be.
20 Lost Transaction
State information about a transaction has been lost.  This usually indicates that software was restarted in the middle of a transaction.  In rare cases, it can indicate that an NAT routing problem has suddenly redirected traffic from one MTP/IP host to another.
21 Encryption Required
The software had been configured to refuse unencrypted transactions.  Try enabling encryption.
22 Encryption Unavailable
Encryption has been requested but is not available.  This may indicate that you are using an export restricted version with encryption disabled.
23 Invalid Encryption Key
The encryption key requested is not valid or is not available.  This may indicate an incompatibility between different software versions or different customer key sets.
24 Request Denied
A transaction is not permitted due to software configuration or user input.
25 Invalid Pathname
A filesystem pathname is not valid.
26 Invalid Host
A DNS name or address related to the transaction is invalid.
27 Permission Denied
The requested action was denied due to insufficient privileges.  This usually indicates that a user does not have permission to access a given file.
28 Unsupported Feature
A feature was requested that is not supported or not enabled.
29 Operating System Error
An unexpected error was reported by the operating system.
30 Server Capacity Exceeded
The software has exceeded its load capacity.  This may indicate that the number of concurrent transactions exceeds the licensed capacity of the software.  Contact DEI if you wish to increase your transaction capacity.
31 Resource Quota Exceeded
A resource limit determined by software configuration or user system limits has been exceeded.
32 Session Aborted
A transaction has been terminated, probably by user request.
33 Out of Memory
The application has run out of memory or is receiving memory errors from the operating system.
34 Object Already in Requested State
The target of an action is already in the state requested by that action.  For example, you may be trying to create a folder that already exists.
35 Slow Down
An application requests that MTP/IP reduce its speed.  MTP/IP will treat this the same as a packet loss or network congestion event.
36 Object Incomplete
The data object cannot be accessed because portions are missing.  For example, a file upload may have been interrupted.
37 Object Corrupt
The data object or information about it is corrupt or missing.
38 Object Does Not Match
The operation cannot proceed because the data object does not appear to match the necessary criteria.  For example, you may be attempting to resume a data transfer on a file which has changed.

DOC Errors

The following class 4 messages may be reported by Document Exchange, the SDK responsible for session management in most MTP/IP applications.  Most are similar to the generic application errors above.

72 DOC Unknown Error
An unexpected error occurred.
73 DOC Incompatible Version
The application versions are not compatible.
74 DOC Internal Error
An internal problem occurred, likely indicating a bug.
75 DOC Document or Meta Too Large
A file or its description was larger than supported.
76 DOC Out of Memory
The application has run out of memory or is receiving memory errors from the operating system.
77 DOC Idle Timeout
It has been a long time since there was any activity on a transaction, so it has been abandoned.  This usually indicates a network connectivity or firewall problem.  See Tech Note 0002 for information about configuring firewalls.
78 DOC Duplicate Request
A request has been repeated after it was already begun.
79 DOC Invalid Argument
An internal function or transaction did not provide proper parameters.
80 DOC Denied by Configuration
A transaction is not permitted due to software configuration or user input.
81 DOC Lost Transaction (Server Restarted?)
State information about a transaction has been lost.  This usually indicates that software was restarted in the middle of a transaction.  In rare cases, it can indicate that an NAT routing problem has suddenly redirected traffic from one MTP/IP host to another.
82 DOC Capacity Exceeded
The software has exceeded its load capacity.  This may indicate that the number of concurrent transactions exceeds the licensed capacity of the software.  Contact DEI if you wish to increase your transaction capacity.
83 DOC Shutting Down
An attempt was made to begin a request after the application began shutting down.
84 DOC MTP Call Failed
An unexpected MTP/IP error occurred.
85 DOC Not Initialized
The application tried to use DOC before the library was initialized.
86 DOC Re-entry Error
The application attempted to access the DOC library on a manner not permitted.
87 DOC Invalid Delivery Target
A data source or destination could not be accessed.

SEQ Errors

The following messages may be reported by MTP Streaming, the SDK responsible for managing dynamic content processing in most MTP/IP applications.  If you encounter these errors, it is likely related to compression, packaging plug-ins, or the piping of input or output streams.

64 SEQ Re-entry Error
The application attempted to access the SEQ library on a manner not permitted.
65 SEQ Invalid Stream Pointer
The application attempted to operate on an invalid stream.
66 SEQ Invalid Argument
An internal function or transaction did not provide proper parameters.
67 SEQ Capacity Exceeded
The software has exceeded its load capacity.  This is not related to server license capacity and instead indicates excessive network loss rates.  Contact DEI for assistance.
68 SEQ Internal Error
An internal problem occurred, likely indicating a bug.
69 SEQ Stream Already Freed
The application attempted to free a stream that was already freed.
70 SEQ Out of Memory
The application has run out of memory or is receiving memory errors from the operating system.

Additional Errors

Other applications, SDKs, and future releases may use error codes which are not listed here.  If you see the error text "Unknown Error Code", it likely indicates a version compatibility problem between two network nodes.

For additional assistance interpreting MTP/IP errors, please contact DEI Technical Support or your local reseller.