前言
在项目中为了方便调试及客户反馈，需要Socket错误数字的中文解释，MSDN上只有英文版，同时也想自己学习而且方便将来更新ErrorCode的实际发生的情景，顾有此博文。
MSDN:https://msdn.microsoft.com/zh-cn/library/ms740668(v=vs.85).aspx
映射表
| ErrorCode | en-US Info | zh-CN Info | Details |
| 6 | Specified event object handle is invalid. | 指定事件对象句柄无效 | An application attempts to use an event object, but the specified handle is not valid. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. |
| 8 | Insufficient memory available. | 可用内存不足 | An application used a Windows Sockets function that directly maps to a Windows function. The Windows function is indicating a lack of required memory resources. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. |
| 87 | One or more parameters are invalid. | 一个或多个参数无效 | An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. |
| 995 | 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. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. |
| Overlapped I/O event object not in signaled state. | 重复的I/O事件还未完成 | 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, get this error code until the operation is complete. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. | |
| 997 | Overlapped operations will complete later. | 重复操作即将完成 | The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. |
| 10004 | Interrupted function call. | （阻塞）函数中断 | A blocking operation was interrupted by a call to WSACancelBlockingCall. |
| 10009 | File handle is not valid. | 文件句柄无效 | The file handle supplied is not valid. |
| 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). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option. |
| 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 sockaddr structure, is smaller than the sizeof(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. |
| 10035 | Resource temporarily unavailable. | 资源暂时不可用 | This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established. |
| 10036 | Operation now in progress. | 操作正在执行 | A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, 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. |
| 10037 | Operation already in progress. | 操作已在执行队列中 | An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed. |
| 10038 | Socket operation on nonsocket. | 尝试在一个非套接字上操作 | 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. |
| 10039 | Destination address required. | 无目标地址 | A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY. |
| 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 was smaller than the datagram itself. |
| 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. |
| 10042 | Bad protocol option. | 错误的协议操作 | An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call. |
| 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. |
| 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. |
| 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 is trying to accept a connection on a datagram socket. |
| 10046 | Protocol family not supported. | 系统不支持此协议（同10043） | The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify 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 (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is 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, for example, in sendto. |
| 10048 | Address already in use. | 绑定地址已存在 | Typically, only one usage of each socket address (protocol/IP address/port) is 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 was not 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 chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf. |
| 10049 | Cannot assign requested address. | 不可分配地址 | The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0). |
| 10050 | Network is down. | 网络断开 | A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets 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 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. |
| 10053 | Software caused connection abort. | 软件导致连接中止 | An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error. |
| 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, the host or remote network interface is disabled, or the remote host uses 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. |
| 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. |
| 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. |
| 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 have been discontinued. |
| 10059 | Too many references. | 过多的引用 | Too many references to some kernel object. |
| 10060 | Connection timed out. | 连接超时 | A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond. |
| 10061 | Connection refused. | 尝试连接被拒绝或服务未启动 | No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running. |
| Cannot translate name. | 不能翻译名称 | Cannot translate a name. | |
| 10063 | Name too long. | 名称过长 | A name component or a name was too long. |
| 10064 | Host is down. | 主机中止 | A socket operation failed because the destination host is 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. |
| 10066 | Directory not empty. | 不能移除非空目录 | Cannot remove a directory that is not empty. |
| 10067 | Too many processes. | 进程数目超出限制 | A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached. |
| 10068 | User quota exceeded. | 用户超出配额 | Ran out of user quota. |
| 10069 | Disk quota exceeded. | 磁盘超出配额 | Ran out of disk quota. |
| 10070 | Stale file handle reference. | 不可用的文件句柄 | The file handle reference is no longer available. |
| 10071 | Item is remote. | 本地不可用 | The item is not available locally. |
| 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. |
| 10092 | Winsock.dll version out of range. | Winsock.dll版本超出支持范围 | 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. |
| Successful WSAStartup not yet performed. | 当前进程无法使用套接字资源 | Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times. | |
| 10101 | Graceful shutdown in progress. | 正在关闭 | Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence. |
| 10102 | No more results. | 没有更多的返回值 | No more results can be returned by the WSALookupServiceNext function. |
| 10103 | Call has been canceled. | 调用被取消，由于其正在运行 | A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled. |
| Procedure call table is invalid. | 过程调用表无效 | The service provider procedure call table is invalid. A service provider returned a bogus procedure table to Ws2_32.dll. This is usually caused by one or more of the function pointers being NULL. | |
| Service provider is invalid. | 服务提供者无效 | The requested service provider is invalid. This error is returned by the WSCGetProviderInfo and WSCGetProviderInfo32 functions if the protocol entry specified could not be found. This error is also returned if the service provider returned a version number other than 2.0. | |
| Service provider failed to initialize. | 服务提供者的DLL加载失败 | The requested service provider could not be loaded or initialized. This error is returned if either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup or NSPStartup function failed. | |
| 10107 | System call failure. | 系统调用失败 | A system call that should never fail has failed. This is a generic error code, returned under various conditions. Returned when a system call that should never fail does fail. For example, if a call to WaitForMultipleEvents fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs. Returned when a provider does not return SUCCESS and does not provide an extended error code. Can indicate a service provider implementation error. |
| 10108 | Service not found. | 在指定的命名空间中找不到服务 | No such service is known. The service cannot be found in the specified name space. |
| 10109 | Class type not found. | 找不到指定的类 | The specified class was not found. |
| 10110 | No more results. | 没有更多的返回值 | No more results can be returned by the WSALookupServiceNext function. |
| 10111 | Call was canceled. | 调用被取消，由于其正在运行 | A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled. |
| 10112 | Database query was refused. | 数据库查询被拒绝 | A database query failed because it was actively refused. |
| 11001 | Host not found. | 指定的主机名未找到 | No such host is known. The name is not an official host name 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 that the specified name could not be found in the relevant database. |
| 11002 | Nonauthoritative host not found. | 未收到授权主机响应 | This is usually a temporary error during host name 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 | This is a nonrecoverable error. | 在查找数据中出现未知错误 | This indicates that some sort of nonrecoverable 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 request was returned by the server with a severe error. |
| 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 host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable. | |
| QoS receivers. | 至少收到一个或多个QoS预约 | At least one QoS reserve has arrived. | |
| QoS senders. | 至少一个QoS发送路径已经到来 | At least one QoS send path has arrived. | |
| No QoS senders. | 没有QoS发送者 | There are no QoS senders. | |
| QoS no receivers. | 没有QoS接收者 | There are no QoS receivers. | |
| QoS request confirmed. | QoS请求被确认 | The QoS reserve request has been confirmed. | |
| QoS admission error. | QoS缺乏资源 | A QoS error occurred due to lack of resources. | |
| QoS policy failure. | QoS请求策略资源被拒绝 | The QoS request was rejected because the policy system couldn't allocate the requested resource within the existing policy. | |
| QoS bad style. | 未知或冲突的QoS样式 | An unknown or conflicting QoS style was encountered. | |
| QoS bad object. | 错误的QoS对象 | A problem was encountered with some part of the filterspec or the provider-specific buffer in general. | |
| QoS traffic control error. | QoS流量控制器错误 | An error with the underlying traffic control (TC) API as the generic QoS request was converted for local enforcement by the TC API. This could be due to an out of memory error or to an internal QoS provider error. | |
| QoS generic error. | 一般的QoS错误 | A general QoS error. | |
| QoS service type error. | QoS服务类型错误 | An invalid or unrecognized service type was found in the QoS flowspec. | |
| QoS flowspec error. | QoS数据流说明错误 | An invalid or inconsistent flowspec was found in the QOS structure. | |
| Invalid QoS provider buffer. | 一个无效的QoS缓存 | An invalid QoS provider-specific buffer. | |
| Invalid QoS filter style. | 无效的QoS过滤风格 | An invalid QoS filter style was used. | |
| Invalid QoS filter type. | 无效的QoS过滤类型 | An invalid QoS filter type was used. | |
| Incorrect QoS filter count. | 不正确的QoS过滤器数量 | An incorrect number of QoS FILTERSPECs were specified in the FLOWDESCRIPTOR. | |
| Invalid QoS object length. | 无效的QoS对象长度 | An object with an invalid ObjectLength field was specified in the QoS provider-specific buffer. | |
| Incorrect QoS flow count. | 不正确的QoS流量数 | An incorrect number of flow descriptors was specified in the QoS structure. | |
| Unrecognized QoS object. | 在QoS缓存中发现未识别对象 | An unrecognized object was found in the QoS provider-specific buffer. | |
| Invalid QoS policy object. | 一个无效的QoS策略对象 | An invalid policy object was found in the QoS provider-specific buffer. | |
| Invalid QoS flow descriptor. | 无效的QoS流量描述符 | An invalid QoS flow descriptor was found in the flow descriptor list. |
|
| Invalid QoS provider-specific flowspec. | 无效的QoS数据流说明符 | An invalid or inconsistent flowspec was found in the QoS provider-specific buffer. | |
| Invalid QoS provider-specific filterspec. | 无效的QoS过滤说明符 | An invalid FILTERSPEC was found in the QoS provider-specific buffer. | |
| Invalid QoS shape discard mode object. | 无效的QoS图形模式 | An invalid shape discard mode object was found in the QoS provider-specific buffer. | |
| Invalid QoS shaping rate object. | 无效的QoS图像对象 | An invalid shaping rate object was found in the QoS provider-specific buffer. | |
| Reserved policy QoS element type. | 保留的QoS对象类型 | A reserved policy element was found in the QoS provider-specific buffer. |
更新说明
后记
文中标红色的部分是翻译不确定的项目（请原谅本人英文水平有限），还请各位看官不吝指教，以后也方便大家查找，谢谢。
引用
https://msdn.microsoft.com/zh-cn/library/ms740668(v=vs.85).aspx
https://msdn.microsoft.com/zh-cn/library/system.net.sockets.socketerror(v=vs.110).aspx