User Guide

Using FileTransfer2
24
FileTransfer2
Transfer Errors and Definitions
The following table describe the most common error messages that might be displayed in the Error
column of the Transfer Status Window.
Error String Meaning
• Failure generic/unclassified failure.
• Success generic success.
• File does not exist the file supplied on the cmdline doesn't exist.
• Failed to create temporary file couldn't create a required temporary file.
• Failed to connect with
FileTransfer application
console app couldn't connect to running instance of
FileTransfer2 application.
• Invalid phone number supplied console parameter is invalid.
• Invalid flow control supplied console parameter is invalid.
• Invalid stopbits supplied console parameter is invalid.
• Invalid parity supplied console parameter is invalid.
• Invalid databits supplied console parameter is invalid.
• Invalid baudrate supplied console parameter is invalid.
• Invalid communications port supplied console parameter is invalid.
• Invalid VNM settings supplied console parameter is invalid.
• Invalid TCP/IP settings supplied console parameter is invalid.
• Invalid file type the file supplied on the cmdline is an unknown file type.
• Unknown Error generic/unknown error.
• Not enough arguments not enough console parameters supplied to do anything.
• Unable to install handler! Ctrl+C, Break console handler couldn't be installed.
• Invalid Option! Expected -
U=<user>:<password>
console security option is incorrect.
• <option> is an invalid option! invalid/unknown option passed to console.
• <option> is not a valid device
mapping or option!
console expected a device mapping or an option but found
something else.
• File: <filename> does not exist
and cannot be transferred!
file does not exist at location specified.
• File: <filename> is currently
opened by another application
and cannot be transferred!
this can happen if another application has an exclusive lock on
a file.
• Nothing to transfer!
• [Project Identifier invalid?]
• [System Identifier invalid?]
After processing all supplied parameters and options, there
was nothing to transfer. That is, no files could be found or
nothing was specified for transfer. Additionally, if you specified
a project identifier and/or a system identifier, you may have
inadvertently requested an empty or nonexistent set of files.
• Failed to open workspace! Failed to open workspace!
• No APW file AXW file does not contain an APW.