Errors are reported to the application with the error object and by firing the Error event. ErrorConstants fall into two classes: design-time errors and run-time errors. The Error event always fires when any error occurs. When Timeout is 0, however, run-time errors are not thrown back to the container. This allows applications that use only non-blocking operation to localize all error handling in the Error event. To summarize:
Errors are marked as INFO or FATAL. An INFO error does not affect the State property. A FATAL error performs an Abort and releases all resources.
| Member | Value | Description |
|---|---|---|
| ptAbort | 11103 | The Abort method was called. FATAL. |
| ptAddressInUse | 10048 | 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. |
| ptAddressNotAvailable | 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. 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. |
| ptAuthentication | 12012 | Authentication with the server failed. FATAL. |
| ptBlocked | 12011 | User thread is blocking in another method. INFO. |
| ptCompile | 12013 | File could not be compiled. INFO. |
| ptConnected | 12014 | A connection already exists |
| ptConnectionAborted | 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. FATAL. |
| ptConnectionRefused | 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 (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. |
| ptConnectionReset | 10054 | 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. |
| ptError | 11100 | Unexpected general error. FATAL. |
| ptFile | 11102 | Error accessing local file storage. FATAL. |
| ptFormatError | 12015 | The server was unable to interpret the query |
| ptHeader | 12101 | The header is not properly terminated. Occurs when a proper termination (usually a CRLFCRLF) is not found in the header. |
| ptHostNotFound | 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. FATAL. |
| ptHostUnreachable | 10065 | Remote host could not be reached. |
| ptHttpInvalidUrl | 12005 | The Url is unspecified or invalid. |
| ptInvalidMailAddress | 12021 | The Email address specified is not valid. |
| ptInvalidParam1 | 12001 | Parameter #1 is invalid. INFO |
| ptInvalidParam2 | 12002 | Parameter #2 is invalid. INFO |
| ptInvalidParam3 | 12003 | Parameter #3 is invalid. INFO |
| ptInvalidParam4 | 12004 | Parameter #4 is invalid. INFO |
| ptInvalidProperty | 12009 | Invalid property assignment. INFO |
| ptNetworkDown | 10050 | 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. |
| ptNetworkReset | 10052 | 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. |
| ptNetworkUnreachable | 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. FATAL. |
| ptNoAccess | 10013 | The user does not have the proper permissions |
| ptNoBufferSpace | 10055 | 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. |
| ptNoCertificate | 12020 | There was an error in creating credentials |
| ptNoData | 11004 | 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. |
| ptNoRecovery | 11003 | 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. |
| ptNoSecurity | 12022 | Secure communications is not available on this machine |
| ptNotConnected | 10057 | 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. |
| ptNotFound | 12017 | The name referred to in the query does not exist |
| ptNotImplemented | 12018 | The server does not support the request type of query |
| ptNotInitialized | 10093 | Network interface could not be initialized. FATAL. |
| ptOk | 0 | No error |
| ptOperationRefused | 12019 | The server refused to perform the specified operation |
| ptOptionNotSupported | 10042 | The specified socket option is not supported by the system. INFO. |
| ptProtocol | 11101 | Unexpected protocol error. FATAL. |
| ptServerError | 12016 | There was a failure on the server |
| ptSocks4DifferentUserID | 12093 | The SOCKS4 server rejected the connection because the client program and identd report different user-ids |
| ptSocks4NoAcceptableMethods | 12024 | The SOCKS5 server will not accept any of the requested methods |
| ptSocks4NoIdentd | 12092 | The SOCKS4 server rejected the connection because it was unable to connect to identd on the client |
| ptSocks4RequestRejected | 12091 | The SOCKS4 server rejected the connection (No reason given) |
| ptSocks5AddressTypeNotSupported | 12038 | The SOCKS5 server reported that the address type is not supported |
| ptSocks5AuthFailed | 12039 | The SOCKS5 server rejected the connection because authorization failed |
| ptSocks5CommandNotSupported | 12037 | The SOCKS5 server reported that the command is not supported |
| ptSocks5ConnectionRefused | 12035 | The SOCKS5 server reported that the host connection was refused |
| ptSocks5HostUnreachable | 12034 | The SOCKS5 server reported that the host was unreachable |
| ptSocks5NetworkUnreachable | 12033 | The SOCKS5 server reported that the network was unreachable |
| ptSocks5NoRuleSet | 12032 | The SOCKS5 server reported that the connection was not allowed by the ruleset |
| ptSocks5ServerFailure | 12031 | The SOCKS5 server reported a general failure |
| ptSocks5TTLExpired | 12036 | The SOCKS5 server reported that the TTL has expired |
| ptTimeout | 10060 | 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. |
| ptTryAgain | 11002 | Non-authoritative: hostname could not be resolved. 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. |
| zipError | 14001 | An error has occurred during file compression/decompression. |