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.

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

227

Entering Passive Mode.

230

User logged in, proceed.

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.

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 can receive that 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:  Click Tools, click Global Options, then click the Connection node. Set Per site max connections /transfers to 1. (By default it is set to 2.)

2. Remove items from the queue. The Queue pane displays 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 within it, then click 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

Cannot open data connection. Try changing from PASV to PORT mode. Check your firewall settings. Try making an HTTP connection.

426

Connection closed; transfer aborted.

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.

532

Need account for storing files.

550

Requested action not taken. File unavailable (e.g., file not found, no access) or permission denied. This error is not caused by CuteFTP. If you believe that your FTP account privileges or permissions are configured incorrectly, contact the technical support department at the remote FTP site or your Web hosting company for help.

552

Requested file action aborted. Exceeded storage allocation (for current directory or data set). This error is not caused by CuteFTP. There is not enough disk space available to you on the remote FTP server. The most common cause for this error is that the limited disk space allocated for your individual FTP account is already in use. This error may also appear when disk space appears to be available but the file being uploaded is large enough so that if it were uploaded, it would cause your disk space quota to be exceeded. To resolve this error, you can increase the space available by deleting unnecessary files from the remote server or by making arrangements with your Web hosting provider or FTP account administrator for additional disk space.

553

Requested action not taken. File name not allowed. Try changing the file name, or getting rid of spaces in the file name. This error is not caused by CuteFTP.  The file name is not allowed by your server. Many FTP servers have restrictions on file names. If your file name contains special characters, symbols, or spaces in the file name, it might be rejected by the remote FTP server. The remote FTP site may also be rejecting a particular file based on the file type or extension. To resolve this error, if the file name contains special characters, symbols, or spaces, you will need to rename the file before you can upload it. Rename the file using only alpha-numeric characters and no spaces. For more information, refer to Opening, Editing, Renaming, and Deleting Files. Note: If you change the file name, you will also need to change links in Web pages that point to that file name.

10,000 series

Winsock error codes

10054

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

10060

Cannot 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

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