Back to product page

Error list


Below is the list of errors that can be fired by the component.

Value Description
30001 Cannot connect at this time. Use Disconnect first.
30002 Please set login/password combination.
30003 Invalid Hostname property value.
30004 Cannot change Hostname at this time. Use Disconnect first.
30005 Cannot change Port at this time. Use Disconnect first.
30006 Cannot [send/receive/make dir/remove dir/rename/get real path/delete file/list dir] at this time, not connected.
30007 Cannot [send/receive/make dir/remove dir/rename/get real path/delete file/list dir] at this time, component busy.
30008 Cannot use single DES with SSH2 protocol.
30009 Invalid local file name or path.
30010 Could not resolve given Hostname.
30011 Invalid data received from remote server. Protocol error.
30012 Protocol version mismatch error.
30013 Bad server public Diffie Hellman key value.
30014 Server signature does not match.
30015 Invalid username or password reported by server.
30016 SFTP subsystem on server unavailable.
30017 Server returned invalid response to [FXP_ATTRS/FXP_OPEN/FXP_READ/FXP_REALPATH/FXP_READDIR/FXP_LSTAT].
30018 Server returned an error: [SERVER ERROR #]
30019 Given path on the server is a directory.
30020 Server cannot write to a given path.
30021 LocalPath should specify a file, and such file does not exist.
30022 Error occurred trying to open local file.
30023 Error occurred trying to read local file.
30024 Error occurred trying to write to local file.
30025 Server replied with invalid response ID.
30026 Please set Hostname property.
30027 Component was busy and got disconnected.
30028 Invalid identification received from server. This is most probably not SSH server.
30029 Protocol error. Could not open channel on the server.
30030 No more authentication methods available. Giving up...
30031 Failed to set attributes. Invalid response from the server.
30032 Failed to create temporary file.
30033 Aborted by user.
30034 Private key type could not be determined.
30035 Cannot change buffer size at this time. Use Disconnect first.
30036 Invalid buffer size. Use at least 8kb buffers.
30037 Current method was aborted.
30038 Cannot set compression at this time. Use Disconnect first.
30039 Compression level should be between 0 and 9.
30040 Proxy server has closed the connection.
30041 Proxy server rejected supplied login credentials.
30043 Cannot use Append method when Resume property is set to True.
30044 Size cannot be 0.
30045 You cannot use IPv6 with proxy support.
30046 RemoteOpen was not called.
30047 Unknown variant type. Try to be more specific.
30048 Failed to set file time.
30049 GSSAPI authentication could not be initialized.
30050 No available encryption algorithms match with the server.
33001 Disconnect: Host not allowed to connect.
33002 Disconnect: Protocol error.
33003 Disconnect: Key exchange failed.
33004 Disconnect: Host authentication failed.
33005 Disconnect: MAC error.
33006 Disconnect: Compression error.
33007 Disconnect: Service not available.
33008 Disconnect: Protocol version not supported.
33009 Disconnect: Host key not verifiable.
33010 Disconnect: Connection lost.
33011 Disconnect: By application.
33012 Disconnect: Too many connections.
33013 Disconnect: Authentication canceled by user.
33014 Disconnect: No more authentication methods available.
33015 Disconnect: Illegal user name.
33016 Unable to load FIPS library.
33017 FIPS library failed to initialize.
33018 Cannot change FIPS library at this time. Disconnect first.
39999 License key missing. You can not use this component in design environment.


Winsock errors:

Value Description
10004 Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall.
10009 Generic error for invalid format, bad format.
10013 Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for "sendto" without broadcast permission being set using setsockopt (SO_BROADCAST).
10014 Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an program passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument which is a struct sockaddr is smaller than sizeof(struct sockaddr).
10022 Invalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket - for instance, calling accept on a socket that is not listening.
10024 Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process or per thread.
10025 The IP address provided is not valid or the host specified by the IP does not exist.
10038 Socket operation on a non-socket. An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.
10048 Address already in use. Only one usage of each socket address (protocol/IP address/port) is normally permitted. This error occurs if a program attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. For server programs that need to bind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Client programs usually need not call bind at all - connect will choose an unused port automatically.
10049 Cannot assign requested address. The requested address is not valid in its context. Normally results from an attempt to bind to an address that is not valid for the local machine, or connect/sendto an address or port that is not valid for a remote machine (e.g. port 0).
10050 Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (the protocol stack that the WinSock DLL runs over), the network interface, or the local network itself.
10051 Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.
10052 Network dropped connection on reset. The host you were connected to crashed and rebooted. May also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.
10053 Software caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error.
10054 Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer program on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close" (see setsockopt for more information on the SO_LINGER option on the remote socket.)
10057 Socket is not connected. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error - for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
10058 Cannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving or both has been discontinued.
10060 Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
10061 Connection refused. No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host - i.e. one with no server program running.
10063 Specified host name is too long.
10064 Host is down. A socket operation failed because the destination host was down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.
10065 No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH
10091 Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable.
10093 Successful WSAStartup not yet performed. Either the program has not called WSAStartup or WSAStartup failed. The program may be accessing a socket which the current active task does not own (i.e. trying to share a socket between tasks), or WSACleanup has been called too many times.
10094 Graceful shutdown in progress. Returned by recv, WSARecv to indicate the remote party has initiated a graceful shutdown sequence.
11001 Host not found. No such host is known. The name is not an official hostname or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means the specified name could not be found in the relevant database.
11002 Authoritative host not found. This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful.

Platforms

Windows