Windows Sockets 错误码
Windows Sockets 错误码
2010年07月22日
Windows Sockets 错误码及出错原因
转载 windows sockets在头文件winsock.h中定义了所有的错误码，它们包括以“wsa”打头的windows sockets实现返回的错误码和berkeley sockets定义的错误码全集。定义berkeley sockets错误码是为了确保原有软件的可移植性。 表a.1列出了wsagetlasterror()函数返回的可能错误码和它们的解释，它们可分为四个部分。
错误码的第一部分是用来解决在不同的c编译中对标准c错误码的不一致的定义。错误码的第二部分是标准berkeley sockets错误码的windows sockets版本。错误码的第三部分包括特定windows sockets扩充的错误码。错误码的第四部分由windows sockets的getxbyy()和wsaasyncgetxbyy()函数返回，相当于berkeley软件中由变量h_errno返回的错误（事实 上，windows sockets在头文件winsock.h中已将h_error定义成其值为wsagetlasterror()的一个宏），它们相当于由域名服务 （domain name service）返回的各种失败。假如windows sockets实现没有使用域名服务，它将使用最合适的代码。一般地，windows sockets应用程序应该将错误wsahost_not_found和wsano_data解释为指示要害字（名字，地址等）没有找着，而错误 wsatry_again和wsano_recovery是提醒名字服务自身是非操作的。
错误码由windows sockets 规范定义，在所有同一版本规范的windows sockets兼容实现中，它们是一致的。
表a.1 windows sockets错误码
下面给出wsagetlasterror()函数返回的可能错误码按字母顺序排列的列表，同时给出简要的扩展描述。
wsaeacces (10013) permission denied.
试图使用被禁止的访问权限去访问套接字。例如，在没有使用函数setsockopt()的so_broadcast命令设置广播权限的套接字上使用函数sendto()给一个广播地址发送数据。
wsaeaddrinuse (10048) address already in use.
正常情况下每一个套接字地址（协议／ip地址／端口号）只答应使用一次。当应用程序试图使用bind()函数将一个被已存在的或没有完全关闭的 或正在关闭的套接字使用了的ip地址／端口号绑扎到一个新套接字上时，该错误发生。对于服务器应用程序来说，假如需要使用bind()函数将多个套接字绑 扎到同一个端口上，可以考虑使用setsockopt()函数的so_reuseaddr命令。客户应用程序一般不必使用bind()函数―― connect()函数总是自动选择没有使用的端口号。当bind()函数操作的是通配地址（包括addr_any）时，错误wsaeaddrinuse 可能延迟到一个明确的地址被提交时才发生。这可能在后续的函数如connect()、listen()、wsaconnect()或 wsajoinleaf()调用时发生。
wsaeaddrnotavail (10049) cannot assign requested address.
被请求的地址在它的环境中是不合法的。通常地在bind()函数试图将一个本地机器不合法的地址绑扎到套接字时产生。它也可能在 connect()、sendto()、wsaconnect()、wsajoinleaf()或wsasendto()函数调用时因远程机器的远程地址 或端口号非法（如0地址或0端口号）而产生。
wsaeafnosupport (10047) address family not supported by protocol family.
使用的地址与被请求的协议不兼容。所有的套接字在创建时都与一个地址族（如ip协议对应的af_inet）和一个通用的协议类型（如 sock_stream）联系起来。假如在socket()调用中明确地要求一个不正确的协议，或在调用sendto()等函数时使用了对套接字来说是错 误的地址族的地址，该错误返回。
wsaealready (10037) operation already in progress.
当在非阻塞套接字上已经有一个操作正在进行时，又有一个操作试图在其上执行则产生此错误。如：在一个正在进行连接的非阻塞套接字上第二次调用connect()函数；或取消一个已经被取消或已完成的异步请求（wsaasyncgetxbyy()）。
wsaeconnaborted (10053) software caused connection abort.
一个已建立的连接被你的主机上的软件终止，可能是因为一次数据传输超时或是协议错误。
wsaeconnrefused (10061) connection refused.
因为目标主机主动拒绝，连接不能建立。这通常是因为试图连接到一个远程主机上不活动的服务，如没有服务器应用程序处于执行状态。
wsaeconnreset (10054) connection reset by peer.
存在的连接被远程主机强制关闭。通常原因为：远程主机上对等方应用程序忽然停止运行，或远程主机重新启动，或远程主机在远程方套接字上使用了 “强制”关闭（参见setsockopt(so_linger)）。另外，在一个或多个操作正在进行时，假如连接因“keep-alive”活动检测到一 个失败而中断，也可能导致此错误。此时，正在进行的操作以错误码wsaenetreset失败返回，后续操作将失败返回错误码 wsaeconnreset。
wsaedestaddrreq (10039) destination address required.
在套接字上一个操作所必须的地址被遗漏。例如，假如sendto()函数被调用且远程地址为addr_any时，此错误被返回。
wsaefault (10014) bad address.
系统检测到调用试图使用的一个指针参数指向的是一个非法指针地址。假如应用程序传递一个非法的指针值，或缓冲区长度太小，此错误发生。例如，参数为结构sockaddr，但参数的长度小于sizeof(struct sockaddr)。
wsaehostdown (10064) host is down.
套接字操作因为目的主机关闭而失败返回。套接字操作碰到不活动主机。本地主机上的网络活动没有初始化。这些条件由错误码wsaetimedout指示似乎更合适。
wsaehostunreach (10065) no route to host.
试图和一个不可达主机进行套接字操作。参见wsaenetunreach。
wsaeinprogress (10036) operation now in progress.
一个阻塞操作正在执行。windows sockets只答应一个任务（或线程）在同一时间可以有一个未完成的阻塞操作，假如此时调用了任何函数（不管此函数是否引用了该套接字或任何其它套接字），此函数将以错误码wsaeinprogress返回。
wsaeintr (10004) interrupted function call.
阻塞操作被函数wsacancelblockingcall ()调用所中断。
wsaeinval (10022) invalid argument.
提供了非法参数（例如，在使用setsockopt()函数时指定了非法的level）。在一些实例中，它也可能与套接字的当前状态相关，例如，在套接字没有使用listen()使其处于监听时调用accept()函数。
wsaeisconn (10056) socket is already connected.
连接请求发生在已经连接的套接字上。一些实现对于在已连接sock_dgram套接字上使用sendto()函数的情况也返回此错误（对于sock_stream套接字，sendto()函数的to参数被忽略），尽管其它一些实现将此操作视为合法事件。
wsaemfile (10024) too many open files.
打开了太多的套接字。不管是对整个系统还是每一进程或线程，windows sockets实现都可能有一个最大可用的套接字句柄数。
wsaemsgsize (10040) message too long.
在数据报套接字上发送的一个消息大于内部消息缓冲区或一些其它网络限制，或者是用来接受数据报的缓冲区小于数据报本身。
wsaenetdown (10050) network is down.
套接字操作碰到一个不活动的网络。此错误可能指示网络系统（例如winsock dll运行的协议栈）、网络接口或本地网络本身发生了一个严重的失败。
wsaenetreset (10052) network dropped connection on reset.
在操作正在进行时连接因“keep-alive”检测到失败而中断。也可能由setsockopt()函数返回，假如试图使用它在一个已经失败的连接上设置so_keepalive。
wsaenetunreach (10051) network is unreachable.
试图和一个无法到达的网络进行套接字操作。它经常意味着本地软件不知道到达远程主机的路由。
wsaenobufs (10055) no buffer space available.
由于系统缺乏足够的缓冲区空间，或因为队列已满，在套接字上的操作无法执行。
wsaenoprotoopt (10042) bad protocol option.
在getsockopt()或setsockopt()调用中，指定了一个未知的、非法的或不支持的选项或层（level）。
wsaenotconn (10057) socket is not connected.
因为套接字没有连接，发送或接收数据的请求不被答应，或者是使用sendto()函数在数据报套接字上发送时没有提供地址。任何其它类型的操作也可以返回此错误，例如，使用setsockopt()函数在一个已重置的连接上设置so_keepalive。
wsaenotsock (10038) socket operation on non-socket.
操作试图不是在套接字上进行。它可能是套接字句柄参数没有引用到一个合法套接字，或者是调用select()函数时，一个fd_set中的成员不合法。
wsaeopnotsupp (10045) operation not supported.
对于引用的对象的类型来说，试图进行的操作不支持。通常它发生在套接字不支持此操作的套接字描述符上，例如，试图在数据报套接字上接收连接。
wsaepfnosupport (10046) protocol family not supported.
协议簇没有在系统中配置或没有支持它的实现存在。它与wsaeafnosupport有些微的不同，但在绝大多数情况下是可互换的，返回这两个错误的所有windows sockets函数的说明见wsaeafnosupport的描述。
wsaeproclim (10067) too many processes.
windows sockets实现可能限制同时使用它的应用程序的数量，假如达到此限制，wsastartup()函数可能因此错误失败。
wsaeprotonosupport (10043) protocol not supported.
请求的协议没有在系统中配置或没有支持它的实现存在。例如，socket()调用请求一个sock_dgram套接字，但指定的是流协议。
wsaeprototype (10041) protocol wrong type for socket.
在socket()函数调用中指定的协议不支持请求的套接字类型的语义。例如，arpa internet udp协议不能和sock_stream套接字类型一同指定。 wsaeshutdown (10058) cannot send after socket shutdown. 因为套接字在相应方向上已经被先前的shutdown()调用关闭，因此该方向上的发送或接收请求不被答应。通过调用shutdown()函数来请求对套接字的部分关闭，它发送一个信号来停止发送或接收或双向操作。
wsaesocktnosupport (10044) socket type not supported.
不支持在此地址族中指定的套接字类型。例如，socket()调用中选择了可选的套接字类型sock_raw，但是实现却根本不支持sock_raw类型的套接字。
wsaetimedout (10060) connection timed out.
连接请求因被连接方在一个时间周期内不能正确响应而失败，或已经建立的连接因被连接的主机不能响应而失败。
wsatype_not_found (10109) class type not found
指定的类没有找到。
wsaewouldblock (10035) resource temporarily unavailable.
此错误由在非阻塞套接字上不能立即完成的操作返回，例如，当套接字上没有排队数据可读时调用了recv()函数。此错误不是严重错误，相应操作 应该稍后重试。对于在非阻塞sock_stream套接字上调用connect()函数来说，报告wsaewouldblock是正常的，因为建立一个连 接必须花费一些时间。
wsahost_not_found (11001) host not found.
主机未知。此名字不是一个正式主机名，也不是一个别名，它不能在查询的数据库中找到。此错误也可能在协议和服务查询中返回，它意味着指定的名字不能在相关数据库中找到。
wsa_invalid_handle (os dependent) specified event object handle is invalid.
应用程序试图使用一个事件对象，但指定的句柄非法。
wsa_invalid_parameter (os dependent) one or more parameters are invalid.
应用程序使用了一个直接映射到win32函数的winsock函数，而win32函数指示一个或多个参数有问题。
wsainvalidproctable (os dependent) invalid procedure table from service provider.
服务提供者返回了一个假的ws2_32.dll程序（procedure）表。这通常是由一个或多个函数指针为空引起。
wsainvalidprovider (os dependent) invalid service provider version number.
服务提供者返回一个不同于2.2的版本号。
wsa_io_incomplete (os dependent) overlapped i/o event object not in signaled state.
应用程序试图检测一个没有完成的重叠操作的状态。应用程序使用函数wsagetoverlappedresult()（参数fwait设置为false）以轮询模式检测一个重叠操作是否完成时将得到此错误码，除非该操作已经完成。
wsa_io_pending (os dependent) overlapped operations will complete later.
应用程序已经初始化了一个不能立即完成的重叠操作。当稍后此操作完成时将有完成指示。
wsa_not_enough_memory (os dependent) insufficient memory available.
应用程序使用了一个直接映射到win32函数的winsock函数，而win32函数指示缺乏必要的内存资源。
wsanotinitialised (10093) successful wsastartup() not yet performed.
应用程序没有调用wsastartup()函数，或函数wsastartup()调用失败了。应用程序可能访问了不属于当前活动任务的套接字（例如试图在任务间共享套接字），或调用了过多的wsacleanup()函数。
wsano_data (11004) valid name, no data record of requested type.
请求的名字合法并且在数据库中找到了，但它没有正确的关联数据用于解析。此错误的通常例子是主机名到地址（使用gethostbyname() 或wsaasyncgethostbyname()函数）的dns转换请求，返回了mx（mail exchanger）记录但是没有a（address）记录，它指示主机本身是存在的，但是不能直接到达。
wsano_recovery (11003) this is a non-recoverable error.
此错误码指示在数据库查找时发生了某种不可恢复错误。它可能是因为数据库文件（如bsd兼容的hosts、services或protocols文件）找不到，或dns请求应服务器有严重错误而返回。
wsaproviderfailedinit (os dependent) unable to initialize a service provider.
服务提供者的dll不能加载（loadlibrary()失败）或提供者的wspstartup/nspstartup函数失败。
wsasyscallfailure (os dependent) system call failure..
当一个不应该失败的系统调用失败时返回。例如，假如waitformultipleobjects()调用失败，或注册的api不能够利用协议／名字空间目录。
wsasysnotready (10091) network subsystem is unavailable.
此错误由wsastartup()函数返回，它表示此时windows sockets实现因底层用来提供网络服务的系统不可用。用户应该检查：
是否有合适的windows sockets dll文件在当前路径中。
是否同时使用了多个winsock实现。假如有多于一个的winsock dll在系统中，必须确保搜索路径中第一个winsock dll文件是当前加载的网络子系统所需要的。
查看winsock实现的文档以确保所有必须的部件都正确地安装并配置好了。
wsatry_again (11002) non-authoritative host not found.
此错误通常是在主机名解析时的临时错误，它意味着本地服务器没有从授权服务器接收到一个响应。稍后的重试可能会获得成功。
wsavernotsupported (10092) winsock.dll version out of range.
当前的winsock实现不支持应用程序指定的windows sockets规范版本。检查是否有旧的windows sockets dll文件正在被访问。
wsaediscon (10101) graceful shutdown in progress.
由wsarecv()和wsarecvfrom()函数返回，指示远程方已经初始化了一个“雅致”的关闭序列。
wsa_operation_aborted (os dependent) overlapped operation aborted.
因为套接字的关闭，一个重叠操作被取消，或是执行了wsaioctl()函数的sio_flush命令。
以下英文解释来自msdn: the following is a list of possible error codes returned by the wsagetlasterror call, along with their extended explanations. errors are listed in alphabetical order by error macro. some error codes defined in winsock2.h are not returned from any function - these have not been listed here. wsaeacces
(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).
wsaeaddrinuse
(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, consider using setsockopt(so_reuseaddr). client applications usually need not call bind at all - connect will choose an unused port automatically. when bind is called with a wild-card address (involving addr_any), a wsaeaddrinuse error could be delayed until the specific address is "committed." this could happen with a call to other function later, including connect, listen, wsaconnect or wsajoinleaf.
wsaeaddrnotavail
(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 can also result from connect, sendto, wsaconnect, wsajoinleaf, or wsasendto when the remote address or port is not valid for a remote machine (e.g. address or port 0).
wsaeafnosupport
(10047)
address family not supported by protocol family.
an address incompatible with the requested protocol was used. all sockets are created with an associated "address family" (i.e. af_inet for internet protocols) and a generic protocol type (i.e. sock_stream). this error will be returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, e.g. in sendto.
wsaealready
(10037)
operation already in progress.
an operation was attempted on a non-blocking socket that already had an operation in progress - i.e. calling connect a second time on a non-blocking socket that is already connecting, or canceling an asynchronous request (wsaasyncgetxbyy) that has already been canceled or completed.
wsaeconnaborted
(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.
wsaeconnrefused
(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 application running.
wsaeconnreset
(10054)
connection reset by peer.
a 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 setsockopt for more information on the so_linger option 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 wsaenetreset. subsequent operations fail with wsaeconnreset.
wsaedestaddrreq
(10039)
destination address required.
a required address was omitted from an operation on a socket. for example, this error will be returned if sendto is called with the remote address of addr_any.
wsaefault
(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 application 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).
wsaehostdown
(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.
wsaehostunreach
(10065)
no route to host.
a socket operation was attempted to an unreachable host. see wsaenetunreach
wsaeinprogress
(10036)
operation now in progress.
a blocking operation is currently executing. windows sockets only allows a single blocking operation to be outstanding per task (or thread), and if any other function call is made (whether or not it references that or any other socket) the function fails with the wsaeinprogress error.
wsaeintr
(10004)
interrupted function call.
a blocking operation was interrupted by a call to wsacancelblockingcall.
wsaeinval
(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.
wsaeisconn
(10056)
socket is already connected.
a connect request was made on an already connected socket. some implementations also return this error if sendto is called on a connected sock_dgram socket (for sock_stream sockets, the to parameter in sendto is ignored), although other implementations treat this as a legal occurrence.
wsaemfile
(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.
wsaemsgsize
(10040)
message too long.
a message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
wsaenetdown
(10050)
network is down.
a socket operation encountered a dead network. this could indicate a serious failure of the network system (i.e. the protocol stack that the winsock dll runs over), the network interface, or the local network itself.
wsaenetreset
(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. it can also be returned by setsockopt if an attempt is made to set so_keepalive on a connection that has already failed.
wsaenetunreach
(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.
wsaenobufs
(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.
wsaenoprotoopt
(10042)
bad protocol option.
an unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
wsaenotconn
(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.
wsaenotsock
(10038)
socket operation on 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.
wsaeopnotsupp
(10045)
operation not supported.
the attempted operation is not supported for the type of object referenced. usually this occurs when a socket descriptor to a socket that cannot support this operation, for example, trying to accept a connection on a datagram socket.
wsaepfnosupport
(10046)
protocol family not supported.
the protocol family has not been configured into the system or no implementation for it exists. has a slightly different meaning to wsaeafnosupport, but is interchangeable in most cases, and all windows sockets functions that return one of these specify wsaeafnosupport.
wsaeproclim
(10067)
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.
wsaeprotonosupport
(10043)
protocol not supported.
the requested protocol has not been configured into the system, or no implementation for it exists. for example, a socket call requests a sock_dgram socket, but specifies a stream protocol.
wsaeprototype
(10041)
protocol wrong type for socket.
a protocol was specified in the socket function call that does not support the semantics of the socket type requested. for example, the arpa internet udp protocol cannot be specified with a socket type of sock_stream.
wsaeshutdown
(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.
wsaesocktnosupport
(10044)
socket type not supported.
the support for the specified socket type does not exist in this address family. for example, the optional type sock_raw might be selected in a socket call, and the implementation does not support sock_raw sockets at all.
wsaetimedout
(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.
wsatype_not_found
(10109)
class type not found.
the specified class was not found.
wsaewouldblock
(10035)
resource temporarily unavailable.
this error is returned from operations on non-blocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. it is a non-fatal error, and the operation should be retried later. it is normal for wsaewouldblock to be reported as the result from calling connect on a non-blocking sock_stream socket, since some time must elapse for the connection to be established.
wsahost_not_found
(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.
wsa_invalid_handle
(os dependent)
specified event object handle is invalid.
an application attempts to use an event object, but the specified handle is not valid.
wsa_invalid_parameter
(os dependent)
one or more parameters are invalid.
an application used a windows sockets function which directly maps to a win32 function. the win32 function is indicating a problem with one or more parameters.
wsainvalidproctable
(os dependent)
invalid procedure table from service provider.
a service provider returned a bogus proc table to ws2_32.dll. (usually caused by one or more of the function pointers being null.)
wsainvalidprovider
(os dependent)
invalid service provider version number.
a service provider returned a version number other than 2.0.
wsa_io_incomplete
(os dependent)
overlapped i/o event object not in signaled state.
the application has tried to determine the status of an overlapped operation which is not yet completed. applications that use wsagetoverlappedresult (with the fwait flag set to false) in a polling mode to determine when an overlapped operation has completed will get this error code until the operation is complete.
wsa_io_pending
(os dependent)
overlapped operations will complete later.
the application has initiated an overlapped operation which cannot be completed immediately. a completion indication will be given at a later time when the operation has been completed.
wsa_not_enough_memory
(os dependent)
insufficient memory available.
an application used a windows sockets function which directly maps to a win32 function. the win32 function is indicating a lack of required memory resources.
wsanotinitialised
(10093)
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.
wsano_data
(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 (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.
wsano_recovery
(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 (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.
wsaproviderfailedinit
(os dependent)
unable to initialize a service provider.
either a service provider's dll could not be loaded (loadlibrary failed) or the provider's wspstartup/nspstartup function failed.
wsasyscallfailure
(os dependent)
system call failure.
returned when a system call that should never fail does. for example, if a call to waitformultipleobjects fails or one of the registry functions fails trying to manipulate theprotocol/namespace catalogs.
wsasysnotready
(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. 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.
wsatry_again
(11002)
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.
wsavernotsupported
(10092)
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.
wsaediscon
(10094)
graceful shutdown in progress.
returned by wsarecv and wsarecvfrom to indicate the remote party has initiated a graceful shutdown sequence.
wsa_operation_aborted
(os dependent)
overlapped operation aborted.
an overlapped operation was canceled due to the closure of the socket, or the execution of the sio_flush command in wsaioctl.
我的异常网推荐解决方案：The server encountered an internal error () that prevented it from fulfilling this request.,http://www.myexception.cn/java-web/317.html
