HiTek Software Home
 Automated FTP and SFTP software you can trust

FTP Status and Error Codes

When you run your Ftp tasks, you will receive various numbered return codes from Ftp servers.  Automize, AbleFtp and JaSftp display these codes in the log window.  Some codes represent errors.  Others codes represent the status of the connection. Here are brief explanations for the most common status and error codes.  These codes and description are taken from RFC 959 - FILE TRANSFER PROTOCOL.




Status or Error Description

100 Series - Positive Preliminary Reply
(The user-process sending another command before the completion reply would be in violation of protocol; but server-FTP processes should queue any commands that arrive while a preceding command is in progress.) This type of reply can be used to indicate that the command was accepted and the user-process may now pay attention to the data connections, for implementations where simultaneous monitoring is difficult. The server-FTP process may send at most, one 1yz reply per command.


Restart marker reply.
In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm Where yyyy is User-process data stream marker, and mmmm server's equivalent marker (note the spaces between markers and "=").


Service ready in nnn minutes.


Data Connection already open, transfer starting.


File status okay, about to open data connection.  




200 Series - Positive Completion reply 
The requested action has been successfully completed. A new request may be initiated.


Command okay.


Command not implemented, superfluous at this site.


System status, or system help reply.


Directory status.


File status.


Help message.  On how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user.


NAME system type. (Where NAME is an official system name from the list in the Assigned Numbers document.)


Service ready for new user.


Service closing control connection. Logged out if appropriate.


Data connection open; no transfer in progress.


Closing data connection. Requested file action successful (for example; file transfer or file abort). 


Entering Passive Mode.


User logged in, proceed.  


Requested file action okay, completed.


"PATHNAME" created.




300 Series - Positive Intermediate reply
The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information. The user should send another command specifying this information. This reply is used in command sequence groups


User name okay, need password.  


Need account for login.


Requested file action pending further information.




400 Series - Transient Negative Completion reply
The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. The user should return to the beginning of the command sequence, if any. It is difficult to assign a meaning to "transient", particularly when two distinct sites (Server- and User-processes) have to agree on the interpretation. Each reply in the 4yz category might have a slightly different time value, but the intent is that the user-process is encouraged to try again. A rule of thumb in determining if a reply fits into the 4yz or the 5yz (Permanent Negative) category is that replies are 4yz if the commands can be repeated without any change in command form or in properties of the User or Server (e.g., the command is spelled the same with the same arguments used; the user does not change his file access or user name; the server does not put up a new implementation.)


Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.  This error may be due to service not available, closing control connection, user limit reached, or you are not authorized to make the connection, or the maximum number of connections have been exceeded.


Can't open data connection.  


Connection closed; transfer aborted.  The command opens a data connection to perform an action, but that action is canceled, and the data connection is closed.


Requested file action not taken. File unavailable (e.g., file busy).


Requested action aborted: local error in processing.


Requested action not taken. Insufficient storage space in system.




500 Series - Permanent Negative Completion reply
The command was not accepted and the requested action did not take place. The User-process is discouraged from repeating the exact request (in the same sequence). Even some "permanent" error conditions can be corrected, so the human user may want to direct his User-process to reinitiate the command sequence by direct action at some point in the future (e.g., after the spelling has been changed, or the user has altered his directory status.)


Syntax error in parameters or arguments.  This may include errors such as command line too long.


Command not implemented. The server does not support this command.


Bad sequence of commands.


Command not implemented for that parameter.


Not logged in.  


Need account for storing files.


Requested action not taken. File unavailable (e.g., file not found, no access).  


Requested file action aborted. Exceeded storage allocation (for current directory or dataset).


Requested action not taken. File name not allowed.