97001 缺省解码失败 为防止以后消息错位，接口将断连 97002 消息头错误 为防止以后消息错位，接口将断连 97003 源缓冲区不够，不处理 继续接收消息
97004 目的缓冲区不够 为防止以后消息错位，接口将断连 97005 严重协议错误 为防止以后消息错位，接口将断连 97006 协议中某字段一般性错误 只删除此消息，不断开接口 97007 接收到NACK消息 为防止以后消息错位，接口将断连 97008 接收太多的握手 接口将断连
97009 地址错误，NPI、TON不支持 只删除此消息，不断开接口 97010 时间格式错误 只删除此消息，不断开接口 97011 DCS错误 只删除此消息，不断开接口 97012 协议不支持 只删除此消息，不断开接口 97013～97999 保留 例：
2001/05/28 15:31:03 2 ID为32的接口产生接口断连信息，对端地址：10.10.2.1 ErrCode:97001,ErrorType:0 4.3 握手或接收异常错误 错误码 原因分析 后续操作 19000 保留
19001 接收消息的Buff出了问题 接口将断连
19002 解码返回的值不对（只能是0/-1/>0） 接口将断连 19003 握手超时 接口将断连 19004 对端主动关闭Socket
19005 连接对方服务器的间隔时间，到时重连
19006 发送Login请求后，等待对方服务器的应答消息超时 19007 进行Socket底层的连接建立，等待connect函数的时间 19008 Dsmpfep read消息错误 4.4 TCP/IP的SOCKET关闭或产生异常
此情况是由于客户端主动关闭退出产生的提示信息，错误代码为―0‖； 例：
2001/05/28 15:32:14 2 ID为32的接口产生接口断连信息，对端地址：10.10.2.1 ErrCode:0,ErrorType:0 或者由于SOCKET底层的其它异常错误，导致接口断连，此时的错误码将有多种多样，详细描述请见WINDOWS平台SOCKET错误码说明及UNIX平台错误码说明。 例：
2001/05/30 15:49:32 2 ID为32的接口产生接口断连信息，对端地址：10.10.2.1 ErrCode:10054,ErrorType:0 4.5 WINDOWS平台SOCKET错误码说明 MSDN对于SOCKET异常ID的描述 错误码值 错误码标识 含义
10004 WSAEINTR Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall. 10013 WSAEACCES 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). 10014 WSAEFAULT 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). 10022 WSAEINVAL 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 WSAEMFILE 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 WSAEWOULDBLOCK 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.
10036 WSAEINPROGRESS 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. 10037 WSAEALREADY 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. 10038 WSAENOTSOCK 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. 10039 WSAEDESTADDRREQ 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. 10040 WSAEMSGSIZE 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. 10041 WSAEPROTOTYPE 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 WSAENOPROTOOPT Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call. 10043 WSAEPROTONOSUPPORT 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 WSAESOCKTNOSUPPORT 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 WSAEOPNOTSUPP 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.
10046 WSAEPFNOSUPPORT 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. 10047 WSAEAFNOSUPPORT Address family not supported by protocol family.
An address incompatible with the requested protocol was used. All sockets are created with an associated \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. 10048 WSAEADDRINUSE 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 \with a call to other function later, including connect, listen, WSAConnect or WSAJoinLeaf. 10049 WSAEADDRNOTAVAIL 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).
10050 WSAENETDOWN 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.
10051 WSAENETUNREACH 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 WSAENETRESET Network dropped connection on reset.
The connection has been broken due to \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 WSAECONNABORTED 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.
10054 WSAECONNRESET 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 \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 \operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
10055 WSAENOBUFS 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 WSAEISCONN 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 WSAENOTCONN Socket is not connected.