Home > HowTo > FTP error codes

FTP error codes

Comprehensive List of FTP Status and Error Codes

During your FTP sessions, you’ll receive various numbered codes
from servers.  CuteFTP displays these codes in the log window.
 Some codes represent errors.  Most others simply communicate the
status of the connection. Here are brief explanations for the most common status
and error codes.

Code

Description

100
Series

The requested action is being initiated, expect another
reply before proceeding with a new command.

110

Restart marker reply.

120

Service ready in nn
minutes.

125

Data Connection already open, transfer starting.

150

File status okay, about to open data connection.  FTP uses two ports: 21 for sending
commands, and 20 for sending data. A status code of 150 indicates that
the server is about to open a new connection on port 20 to send some
data.

 

Description

200
Series

The requested action has been successfully completed.

200

Command okay.

202

Command not implemented, superfluous at this site.

211

System status, or system help reply.

212

Directory status.

213

File status.

214

Help message.

215

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

220

Service ready for new user.

221

Service closing control connection. Logged out if
appropriate.

225

Data connection open; no transfer in progress.

226

Closing data connection. Requested file action
successful (for example; file transfer or file abort). The command opens a data connection on
port 20 to perform an action, such as transferring a file. This action
successfully completes, and the data connection is closed.

227

Entering Passive Mode.

230

User logged in, proceed.  This status code appears after the client
sends the correct password. It indicates that the user has
successfully logged on.

250

Requested file action okay, completed.

257

"PATHNAME" created.

 

 

300
Series

The command has been accepted, but the requested action
is on hold, pending receipt of further information.

331

User name okay, need password.  You see this status code after the client
sends a user name. This same status code appears regardless of whether
the user name that is provided is a valid account on the system.

332

Need account for login.

350

Requested file action pending further information.

 

 

400
Series

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.

421

Error 421 Service not available, closing control
connection.
Error 421 User limit reached

Error 421 You are not authorized to make the connection
Error 421 Max connections reached
Error 421 Max connections exceeded


Possible Solutions:

You may receive a 421 error if the FTP server you are
connected to limits the total number of connections available or limits
the connections available to one user.  There are three things you
can do:

1. Limit the number of connections to any one FTP site
by selecting Tools > Global
Options > Connection
and set "Per site max
connections / transfers" to 1 (By default it will be set to 2).

2. Remove items from the Transfer Queue.  The
Transfer Queue is where you see items ready for transfer, in
transit, or just transferred.  Sometimes the Queue Pane can
become cluttered with unfinished transfers.  To clear the
queue, right-click inside it and choose Remove
All
.

3. Make sure only one instance of CuteFTP is running on
your system.  Open the Windows Task Manager and see if CuteFTP
is listed more than once.

425

Can’t open data connection.  

Possible Solutions:

1. Try changing from PASV to PORT mode.

2. Check your firewall settings.

3. Try making an HTTP connection.

426

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.

450

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

451

Requested action aborted: local error in processing.

452

Requested action not taken. Insufficient storage space
in system.

 

 

500
Series

The command was not accepted and the requested action
did not take place.

501

Syntax error in parameters or arguments.

502

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

503

Bad sequence of commands.

504

Command not implemented for that parameter.

530

Not logged in.  Your
password is being rejected, contact the server administrator

This status code indicates that the user
cannot log on because the user name and password combination is not
valid. If you use a user account to log on, you may have mistyped the
user name or password, or the server may be configured to allow only Anonymous
access. 

532

Need account for storing files.

550

Requested action not taken. File unavailable (e.g., file
not found, no access).  Contact
the server administrator
.  The command is not executed because the
specified file is not available. For example, this status code occurs
when you try to download (GET) a file that does not exist, or when you try to
upload (PUT)
a file in a directory for which you do not have Write access.

552

Requested file action aborted. Exceeded storage
allocation (for current directory or data set). Contact
the server administrator
.

553

Requested action not taken. File name not allowed.
 Try changing the file name, or
getting rid of spaces in the file name
.

 

 

10,000
series

Common Winsock Error Codes (complete
list of Winsock error codes
)

10054

Connection reset by peer. The connection was forcibly
closed by the remote host.

10060

Can’t connect to remote server (Generally a time-out
error).  Try switching from
PASV to PORT mode
, or try increasing the time-out value
(See
Reconnect and resume in
Transfer
settings
).

10061

Can’t connect to remote server. The connection is
actively refused by the server.  Try
switching the
connection port
.

10066

Directory not empty. The server will not delete this
directory while there are files/folders in it.

10068

Too many users, server is full. Try
connecting later. If the problem persists,
Contact
the server administrator
.



Categories: HowTo Tags:
  1. No comments yet.
  1. No trackbacks yet.

VAMOVE *

*