The Site FTP log
When you connect to a server using Dreamweaver's FTP feature, Dreamweaver generates an FTP log. This log lists the transactions which occurred between Dreamweaver and the server during the connection. To explain the transactions, the log displays line-by-line standard codes and commands.
Many FTP problems can be identified by reading the codes and commands in this log. Below you'll find information which will assist you in reviewing and interpreting FTP logs, as well as links to Macromedia TechNotes which offer troubleshooting tips for specific FTP difficulties:
Accessing the Site FTP log
In the Site window, chooseWindow > Site FTP Log.
In the Document window, chooseWindow> Site FTP Log.
An FTP log example
In the sample FTP log below, you'll see numbers (such as 220) which are referred to as "series codes." Interspersed throughout the series codes are commands (such as MKD).
220 ftp.macromedia.com FTP server (ms-ftpd(16) Thu Feb 27 18:32:59 EST 1997) ready.
331 Password required for jmacro
230-Checking disk usage, please wait.
230- Your disk quota is: 5.00 megabytes.
230- Your disk usage is:
230- Home/WWW: 1.23 megabytes
230- FTP: 0.00 megabytes
230- Total: 1.23 megabytes (25% of quota)
230 User email@example.com logged in.
215 UNIX Type: L8 Version: BSD-198911
257 "/jmacro" is current directory.
257 MKD command successful.
200 Type set to A.
200 PORT command successful.
150 Opening ASCII mode data connection for /bin/ls
FTP codes and actions
The series code (the number) at the beginning of some lines of the FTP log describes the action that took place between your computer and the server in the FTP process. The table below offers a description of these FTP codes and actions.
FTP series codes
|100 Series Codes
||The requested action is being initiated, expect another reply before proceeding with a new command.
||Restart marker reply.
||Service ready in nnn minutes.
||Data connection already open, transfer starting.
||File status okay, about to open data connection.
|200 Series Codes
||The requested action has been successfully completed.
||Command not implemented, superfluous at this site.
||System status, or system help reply.
||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.
|300 Series Codes
||The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information.
||User name okay, need password.
||Need account for login.
||Requested file action pending further information.
|400 Series Codes
||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.
||This service is not accepting users now. User quota filled. Try again later.
||Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.
||Can't open data connection.
||Connection closed; transfer aborted.
||Log-in unsuccessful. User name and/or password invalid.
||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.
||File transfer incomplete. Insufficient storage space.
|500 Series Codes
||The command was not accepted and the requested action did not take place.
||Syntax error, command unrecognized. This may include errors such as command line too long.
||Syntax error in parameters or arguments.
||Command not implemented.
||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.
Note:Bear in mind that some of these codes may have different meanings with different servers.
Common FTP commands
There are also text commands that describe actions, as explained in the table below:
FTP commands and actions
||abort a file transfer
||change working directory
||delete a remote file
||list remote files
||return the modification time of a file
||make a remote directory
||name list of remote directory
||enter passive mode
||open a data port
||print working directory
||terminate the connection
||retrieve a remote file
||remove a remote directory
||return the size of a file
||store a file on the remote host
||set transfer type
FTP; errors; FTP codes; FTP commands; tn_14536