SFTP Return Codes Overview

This section outlines the list of SFTP return codes currently implemented by Titan FTP Server.


Ok - Indicates successful completion of the operation.


End of file - An attempt to read past the end-of-file was made, or there are no more directory entries to return.


No such file - A reference was made to a file which does not exist.


Permission denied - The user does not have sufficient permissions to perform the operation.


Failure - An error occurred, but no specific error code exists to describe the failure.


Bad message - A badly formatted packet or other SFTP protocol incompatibility was detected.


No connection - There is no connection to the server.


Connection lost - The connection to the server was lost.


Operation unsupported - An attempted operation could not be completed by the server because the server does not support the operation.


Invalid handle - The handle value was invalid.


No such path - The file path does not exist or is invalid.


File already exists - The file already exists.


Write protect - The file is on read-only media, or the media is write protected.


No media - The requested operation cannot be completed because there is no media available in the drive.


No space on filesystem - The requested operation cannot be completed because there is no free space on the filesystem.


Quota exceeded - The operation cannot be completed because it would exceed the user's storage quota.


Unknown principal - A principal referenced by the request was unknown (either the owner, group, or who field of an ACL).


Lock conflict - The file could not be opened because it is locked by another process.


Directory not empty - The directory is not empty.


Not a directory - The specified file is not a directory.


Invalid filename - The filename is not valid.


Link loop - Too many symbolic links encountered.


Cannot delete - The file cannot be deleted. One possible reason is that the advisory READONLY attribute-bit is set.


Invalid parameters - One of the parameters was out of range, or the parameters specified cannot be used together.


File is a directory - The specified file was a directory in a context where a directory cannot be used.


Byte range lock conflict - A read or write operation failed because the mandatory byte-range lock of another process overlaps with the request.


Byte range lock refused - A request for a byte range lock was refused.


Delete pending - An operation was attempted on a file for which a delete operation is pending.


File corrupt - The file is corrupt; an filesystem integrity check should be run.