List of error messages generated during FTP/Internet transfer of back-up files

Modified on: 2017-08-07 13:50:43 -0400


Value
Constant
Description
10042
ptOptionNotSupported
The specified socket option is not supported by the system. INFO.
10048
ptAddressInUse
Address already in use. Only one usage of each socket address (protocol/IP address/port) is normally permitted. This error occurs if an application 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 applications that need to bind() multiple sockets to the same port number, the ReuseAddress property can be used. FATAL.
10049
ptAddressNotAvailable
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. This may also result from connect(), sendto(), WSAConnect(), WSAJoinLeaf(), or WSASendTo() when the remote address or port is not valid for a remote machine (for example, address or port 0). FATAL.
10050
ptNetworkDown
Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (for example,. the protocol stack that the Winsock DLL runs over), the network interface, or the local network itself. FATAL.
10051
ptNetworkUnreachable
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. FATAL.
10052
ptNetworkReset
Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. FATAL.
10053
ptConnectionAborted
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. FATAL.
10054
ptConnectionReset
Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a 'hard close' (see Abort method) on the remote socket. This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with ptNetworkReset. Subsequent operations fail with ptConnectionReset. FATAL.
10055
ptNoBufferSpace
No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. FATAL.
10057
ptNotConnected
Socket is not connected. A request to send or receive data was disallowed because the socket is not connected or allocated. Any other type of operation might also return this error. FATAL.
10060
ptTimeout
Timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because connected host has failed to respond. Alternatively, a blocked method failed to return within the period specified by the Timeout property. FATAL.
10061
ptConnectionRefused
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 (for example,. one with no server application running). May also be generated by a Daemon that refuses a connection because its resources have been exhausted. FATAL.
10065
ptHostUnreachable
Remote host does not exist
10093
ptNotInitialized
Network interface could not be initialized. FATAL.
11001
ptHostNotFound
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. FATAL.
11002
ptTryAgain
Non-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. FATAL.
11003
ptNoRecovery
This is a non-recoverable error. This indicates some sort of non-recoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES or PROTOCOLS files) could not be found, or a DNS (Domain Name Server) request was returned by the server with a severe error. FATAL.
11004
ptNoData
Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a hostname -> address translation attempt which uses the DNS, and an MX record is returned but no A record - indicating the host itself exists but is not directly reachable. FATAL.
11100
ptError
Unexpected general error. FATAL.
11101
ptProtocol
Unexpected protocol error. FATAL.
11102
ptFile
Error accessing local file storage. FATAL.
11103
ptAbort
The Abort method was called. FATAL.
12005
ptHttpInvalidUrl
The Url is unspecified or invalid.
12011
ptBlocked
User thread is blocking in another method. INFO.
12012
ptAuthentication
Authentication with the server failed. FATAL.
12013
ptCompile
MIB file could not be compiled. INFO.
12014
ptConnected
A connection already exists.
12015
ptFormatError
The server was unable to interpret the query.
12016
ptServerError
There was a failure on the server.
12017
ptNotFound
The name referred to in the query does not exist.
12018
ptNotImplemented
The server does not support the request type of query.
12019
ptOperationRefused
The server refused to perform the specified operation.
12020
ptNoCertificate
There was an error in creating credentials.
12021
ptInvalidMailAddress
The Email address specified was not valid.
12022
ptNoSecurity
Secure communications is not available on this machine.
12026
ptSecurity
User does not have proper rights to directory.
12101
ptHeader
Occurs when a proper termination (usually a CRLFCRLF) is not found in the header.
14001
zipError
An error has occurred during file compression/decompression.




Did you find this helpful? Yes No

Can you please tell us how we can improve this article?