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 WSAESHUTDOWN 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 WSAETIMEDOUT 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 WSAECONNREFUSED 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 application running.
10064 WSAEHOSTDOWN 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 WSAEHOSTUNREACH No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH 10067 WSAEPROCLIM Too many processes.
A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. WSAStartup may fail with this error if the limit has been reached. 10091 WSASYSNOTREADY 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. Users should check:
that the appropriate Windows Sockets DLL file is in the current path,
that they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one WINSOCK DLL on your system, be sure the first one in the path is appropriate for the
network subsystem currently loaded.
the Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.
10092 WSAVERNOTSUPPORTED WINSOCK.DLL version out of range.
The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed. 10093 WSANOTINITIALISED Successful WSAStartup not yet performed.
Either the application hasn't called WSAStartup or WSAStartup failed. The application 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 WSAEDISCON Graceful shutdown in progress.
Returned by WSARecv and WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.
10109 WSATYPE_NOT_FOUND Class type not found. The specified class was not found.
11001 WSAHOST_NOT_FOUND 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 WSATRY_AGAIN 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. 11003 WSANO_RECOVERY 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 (e.g. BSD-compatible HOSTS, SERVICES or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error. 11004 WSANO_DATA 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 (using
gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server), and an MX record is returned but no A record - indicating the host itself exists, but is not directly reachable.
4.6 UNIX平台SOCKET错误码说明 错误码值 错误码标识 含义 HP平台
10001 EPERM Not super-user
10002 ENOENT No such file or directory 10003 ESRCH No such process 10004 EINTR interrupted system call 10005 EIO I/O error
10006 ENXIO No such device or address 10007 E2BIG Arg list too long 10008 ENOEXEC Exec format error 10009 EBADF Bad file number 10010 ECHILD No children 10011 EAGAIN No more processes 10012 ENOMEM Not enough core 10013 EACCES Permission denied 10014 EFAULT Bad address
10015 ENOTBLK Block device required 10016 EBUSY Mount device busy 10017 EEXIST File exists 10018 EXDEV Cross-device link 10019 ENODEV No such device 10020 ENOTDIR Not a directory 10021 EISDIR Is a directory 10022 EINVAL Invalid argument 10023 ENFILE File table overflow
10024 EMFILE Too many open files 10025 ENOTTY Not a typewriter 10026 ETXTBSY Text file busy 10027 EFBIG File too large
10028 ENOSPC No space left on device 10029 ESPIPE Illegal seek
10030 EROFS Read only file system 10031 EMLINK Too many links 10032 EPIPE Broken pipe 10033 10034
10035 ENOMSG No message of desired type 10036 EIDRM Identifier removed
10037 ECHRNG Channel number out of range 10038 EL2NSYNC Level 2 not synchronized 10039 EL3HLT Level 3 halted 10040 EL3RST Level 3 reset
10041 ELNRNG Link number out of range 10042 EUNATCH Protocol driver not attached 10043 ENOCSI No CSI structure available 10044 EL2HLT Level 2 halted
10045 EDEADLK A deadlock would occur
10046 ENOLCK System record lock table was full 10047 EILSEQ Illegal byte sequence 10048 10049
10050 ENONET Machine is not on the network 10051 ENODATA no data (for no delay io) 10052 ETIME timer expired
10053 ENOSR out of streams resources
10054 ENOSTR Device not a stream 10055 ENOPKG Package not installed 10056
10057 ENOLINK the link has been severed 10058 EADV advertise error 10059 ESRMNT srmount error
10060 ECOMM Communication error on send 10061 EPROTO Protocol error
10064 EMULTIHOP multihop attempted
10066 EDOTDOT Cross mount point (not really error) 10067 EBADMSG trying to read unreadable message 10068 EUSERS For Sun compatibilty, will not occur. 10069 EDQUOT Disc quota exceeded 10070 ESTALE Stale NFS file handle
10071 EREMOTE Too many levels of remote in path
10072 EOVERFLOW Value too large to be stored in data type 10152 ENOLOAD Cannot load required kernel module 10153 ERELOC Object file error in loading kernel module 10154 ENOMATCH Symbol matching given spec not found 10155 ENOUNLD Cannot unload kernel module
10156 EBADVER Version number mismatch for loadable kernel module 10157 ECONFIG Configured kernle resource exhausted 10158 ENOREG Cannot register required kernel module 10159 ENOUNREG Cannot unregister kernel module 10215 ENOSYM symbol does not exist in executable 10216 ENOTSOCK Socket operation on non-socket 10217 EDESTADDRREQ Destination address required 10218 EMSGSIZE Message too long
10219 EPROTOTYPE Protocol wrong type for socket 10220 ENOPROTOOPT Protocol not available