============================================================================================
Defined Code Description
============================================================================================
WSAEINTR 10004 WSACancelBlockingCall()에 의해 블록화 호출이 취소: Interrupted system call)
WSAEBADF 10009 표준 C와 동일: Bad file number
WSAEACCES 10013 표준 C와 동일: Permission denied
WSAEFAULT 10014 표준 C와 동일: Bad address
WSAEINVAL 10022 표준 C와 동일: 소켓이 주소에 바인딩되지 않았습니다.(Invalid argument)
WSAEMFILE 10024 표준 C와 동일: Too many open files
WSAEWOULDBLOCK 10035 소켓이 비블록화 모드에 있고 요청된 오퍼레이션이 블록: NonBlocking)이고, 연결이 곧바로 종료될 수 없습니다.(Operation would block)
WSAEINPROGRESS 10036 블록화 함수가 진행되는 동안 부적절한 윈속 API함수가 호출. WSACancelBlockingCall 함수와 WSAIsBlocking 함수와 같이 일부 윈속 함수는 허용:Operation now in progress)
WSAEALREADY 10037 이미 완료된 비동기 오퍼레이션에 대한 취소가 시도됨: Operation already in progress
WSAENOTSOCK 10038 해당 애플리케이션에 대해 지정된 소켓 기술자가 유효하지 않음: Socket operation on non-socket)
WSAEDESTADDRREQ 10039 해당 함수에 대해 목적지 어드레스가 필요하지만 제공되지 않았음: (Destination address required)
WSAEMSGSIZE 10040 데이터 수신 시 데이터그램이 너무 길어서 제공된 버퍼에 맞지 않아 잘렸음. 데이터 전송 시 제공된 데이터그램이 윈도우즈 소켓 시스템에 의해 제공된 데이터그램의 최대 크기보다 더 김
WSAEPROTOTYPE 10041 지정된 프로토콜이 다른 파라미터와 일치하지 않음: Protocol wrong type for socket
WSAENOPROTOOPT 10042 프로토콜 옵션이 알려지지 않은 것이거나 유효하지 않음: Protocol not available
WSAEPROTONOSUPPORT 10043 지정된 프로토콜이 윈도우즈 소켓 시스템에 의해 지원되지 않음: Protocol not supported
WSAESOCKTNOSUPPORT 10044 지정된 소켓 타입이 지정된 어드레스 패밀리에 의해 지원도지 않음: Socket type not supported
WSAEOPNOTSUPP 10045 소켓이 지정된 어퍼레이션을 지원하지 않음. 예:listen함수가 데이터그램 소켓에서 호출: Operation not supported on socket
WSAEPFNOSUPPORT 10046 BSD와 동일: Protocol family not supported
WSAEAFNOSUPPORT 10047 지정된 어드레스 패밀리가 윈도우즈 소켓 시스템에 의해 지원되지 않거나 표시된 소켓과 사용될 수 없음: Address family not supported by protocol family
WSAEADDRINUSE 10048 지정된 어드레스가 이미 사용 중임: Address already in use)
WSAEADDRNOTAVAIL 10049 지정된 어드레스를 로컬 머신에서 사용할 수 없음: Can't assign requested address)
WSAENETDOWN 10050 네트워크 서브시스템과 문제가 있음: Network is down)
WSAENETUNREACH 10051 네크웍에 접근할 수 없습니다.(Network is unreachable)
WSAENETRESET 10052 연결이 끊어져서 재설정되어야 함: Network dropped connection on reset
WSAECONNABORTED 10053 타임아웃이나 다른 에러 상황으로 인해 연결이 중지되었음: Software caused connection abort(WSAECONNABORTED)
WSAECONNRESET 10054 연결이 원격 호스트에 의해 재설정되었음: Connection reset by peer
WSAENOBUFS 10055 윈도우즈 소켓 시스템이 버퍼 공간으 넘거나, 애플리케이션에 의해 API에게 제공된 공간이 너무 작아서 요청된 정보를 저장할 수 없음 :(No buffer space available)
WSAEISCONN 10056 지정된 소켓이 이미 연결되었음: Socket is already connected)
WSAENOTCONN 10057 지정된 소켓이 연결되지 않았음: Socket is not connected
WSAESHUTDOWN 10058 소켓에게 셧다운이 요청되었음: Can't send after socket shutdown
WSAETOOMANYREFS 10059 BSD와 동일: Too many references: can't splice
WSAETIMEDOUT 10060 연결이 이루어지기 전에 연결 시도가 타임아웃되었음: (Connection timed out)
WSAECONNREFUSED 10061 서버가 강제로 연결시도를 거절합니다.(Connection refused)
WSAELOOP 10062 BSD와 동일: Too many levels of symbolic links
WSAENAMETOOLONG 10063 BSD와 동일: File name too long
WSAEHOSTDOWN 10064 BSD와 동일: Host is down
WSAEHOSTUNREACH 10065 BSD와 동일: No route to host
WSAENOTEMPTY 네트워크 서브시스템이 아직 통신할 준비가 되어 있지 않음 WSAStartup에 의해 반환: Directory not empty
WSAEPROCLIM Too many processes
WSAEUSERS Too many users
WSAEDQUOT Disc quota exceeded
WSAESTALE Stale NFS file handle
WSAEREMOTE Too many levels of remote in path
WSAEDISCON Disconnect
WSASYSNOTREADY 네트워크 서브시스템이 아직 통신할 준비가 되어 있지 않음 WSAStartup에 의해 반환: Network sub-system is unusable
WSAVERNOTSUPPORTED 윈도우즈 소켓 DLL이 요청된 윈속 프로토콜 버전을 지원하지 않음. WSAStartUp에 의해 반환: WinSock DLL cannot support this application
WSANOTINITIALISED WSAStartup함수가 성공적으로 수행되기 전에 모든 윈속 API함수에 의해 반환: WinSock not initialized
WSAHOST_NOT_FOUND 요청된 데이터베이스 정보가 존재하지 않은. 공인 호스트에 의해 확인: Host not found
WSATRY_AGAIN 요청된 정보가 발견되지 않았지만 응답에 대한 공인도가 없음: Non-authoritative host not found
WSANO_RECOVERY 복구할 수 없는 에러가 발생하였음: Non-recoverable error
WSANO_DATA 제공된 이름이 유효하지만 요청된 타입의 정보가 데이터베이스에 없음: Valid name, no data record of requested type
============================================================================================
The following list describes the possible error codes returned by the WSAGetLastError function. Errors are listed in alphabetical order by error macro. Some error codes defined in Winsock2.h are not returned from any function?遊쿴ese are not included in this list.
Return Code/Value Description
WSAEINTR
10004
Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
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).
Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or 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 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
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 sockaddr structure, is smaller than the sizeof(sockaddr).
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?遊즣r instance, calling accept on a socket that is not listening.
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.
WSAEWOULDBLOCK
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.
WSAEINPROGRESS
10036
Operation now in progress.
A blocking operation is currently executing. Windows Sockets only allows a single blocking operation?遊칎r- task or thread?遊쿽 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.
WSAEALREADY
10037
Operation already in progress.
An operation was attempted on a nonblocking socket with an operation already in progress?遊쿴at 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.
WSAENOTSOCK
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.
WSAEDESTADDRREQ
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.
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 was smaller than the datagram itself.
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.
WSAENOPROTOOPT
10042
Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
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.
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.
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 is 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. 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.
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.
WSAEADDRINUSE
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??A class='MIME' class='MIME' href="connect_2.htm">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.
WSAEADDRNOTAVAIL
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).
WSAENETDOWN
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.
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.
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.
WSAECONNABORTED
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.
WSAECONNRESET
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.
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.
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.
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?遊즣r example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
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 have been discontinued.
WSAETIMEDOUT
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.
WSAECONNREFUSED
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?遊쿴at is, one with no server application running.
WSAEHOSTDOWN
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.
WSAEHOSTUNREACH
10065
No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAEPROCLIM
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.
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.
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.
WSANOTINITIALISED
10093
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.
WSAEDISCON
10101
Graceful shutdown in progress.
Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
WSATYPE_NOT_FOUND
10109
Class type not found.
The specified class was not found.
WSAHOST_NOT_FOUND
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.
WSATRY_AGAIN
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.
WSANO_RECOVERY
11003
This is a nonrecoverable error.
This indicates 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.
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 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?遊쬷dicating the host itself exists, but is not directly reachable.
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 Windows function. The Windows function is indicating a problem with one or more parameters.
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, 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 that cannot be completed immediately. A completion indication will be given later when the operation has been completed.
WSA_NOT_ENOUGH_MEMORY
OS dependent
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.
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.
WSAINVALIDPROCTABLE
OS dependent
Invalid procedure table from service provider.
A service provider returned a bogus procedure 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.
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.
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/name space catalogs.
Returned when a provider does not return SUCCESS and does not provide an extended error code. Can indicate a service provider implementation error.
Defined Code Description
============================================================================================
WSAEINTR 10004 WSACancelBlockingCall()에 의해 블록화 호출이 취소: Interrupted system call)
WSAEBADF 10009 표준 C와 동일: Bad file number
WSAEACCES 10013 표준 C와 동일: Permission denied
WSAEFAULT 10014 표준 C와 동일: Bad address
WSAEINVAL 10022 표준 C와 동일: 소켓이 주소에 바인딩되지 않았습니다.(Invalid argument)
WSAEMFILE 10024 표준 C와 동일: Too many open files
WSAEWOULDBLOCK 10035 소켓이 비블록화 모드에 있고 요청된 오퍼레이션이 블록: NonBlocking)이고, 연결이 곧바로 종료될 수 없습니다.(Operation would block)
WSAEINPROGRESS 10036 블록화 함수가 진행되는 동안 부적절한 윈속 API함수가 호출. WSACancelBlockingCall 함수와 WSAIsBlocking 함수와 같이 일부 윈속 함수는 허용:Operation now in progress)
WSAEALREADY 10037 이미 완료된 비동기 오퍼레이션에 대한 취소가 시도됨: Operation already in progress
WSAENOTSOCK 10038 해당 애플리케이션에 대해 지정된 소켓 기술자가 유효하지 않음: Socket operation on non-socket)
WSAEDESTADDRREQ 10039 해당 함수에 대해 목적지 어드레스가 필요하지만 제공되지 않았음: (Destination address required)
WSAEMSGSIZE 10040 데이터 수신 시 데이터그램이 너무 길어서 제공된 버퍼에 맞지 않아 잘렸음. 데이터 전송 시 제공된 데이터그램이 윈도우즈 소켓 시스템에 의해 제공된 데이터그램의 최대 크기보다 더 김
WSAEPROTOTYPE 10041 지정된 프로토콜이 다른 파라미터와 일치하지 않음: Protocol wrong type for socket
WSAENOPROTOOPT 10042 프로토콜 옵션이 알려지지 않은 것이거나 유효하지 않음: Protocol not available
WSAEPROTONOSUPPORT 10043 지정된 프로토콜이 윈도우즈 소켓 시스템에 의해 지원되지 않음: Protocol not supported
WSAESOCKTNOSUPPORT 10044 지정된 소켓 타입이 지정된 어드레스 패밀리에 의해 지원도지 않음: Socket type not supported
WSAEOPNOTSUPP 10045 소켓이 지정된 어퍼레이션을 지원하지 않음. 예:listen함수가 데이터그램 소켓에서 호출: Operation not supported on socket
WSAEPFNOSUPPORT 10046 BSD와 동일: Protocol family not supported
WSAEAFNOSUPPORT 10047 지정된 어드레스 패밀리가 윈도우즈 소켓 시스템에 의해 지원되지 않거나 표시된 소켓과 사용될 수 없음: Address family not supported by protocol family
WSAEADDRINUSE 10048 지정된 어드레스가 이미 사용 중임: Address already in use)
WSAEADDRNOTAVAIL 10049 지정된 어드레스를 로컬 머신에서 사용할 수 없음: Can't assign requested address)
WSAENETDOWN 10050 네트워크 서브시스템과 문제가 있음: Network is down)
WSAENETUNREACH 10051 네크웍에 접근할 수 없습니다.(Network is unreachable)
WSAENETRESET 10052 연결이 끊어져서 재설정되어야 함: Network dropped connection on reset
WSAECONNABORTED 10053 타임아웃이나 다른 에러 상황으로 인해 연결이 중지되었음: Software caused connection abort(WSAECONNABORTED)
WSAECONNRESET 10054 연결이 원격 호스트에 의해 재설정되었음: Connection reset by peer
WSAENOBUFS 10055 윈도우즈 소켓 시스템이 버퍼 공간으 넘거나, 애플리케이션에 의해 API에게 제공된 공간이 너무 작아서 요청된 정보를 저장할 수 없음 :(No buffer space available)
WSAEISCONN 10056 지정된 소켓이 이미 연결되었음: Socket is already connected)
WSAENOTCONN 10057 지정된 소켓이 연결되지 않았음: Socket is not connected
WSAESHUTDOWN 10058 소켓에게 셧다운이 요청되었음: Can't send after socket shutdown
WSAETOOMANYREFS 10059 BSD와 동일: Too many references: can't splice
WSAETIMEDOUT 10060 연결이 이루어지기 전에 연결 시도가 타임아웃되었음: (Connection timed out)
WSAECONNREFUSED 10061 서버가 강제로 연결시도를 거절합니다.(Connection refused)
WSAELOOP 10062 BSD와 동일: Too many levels of symbolic links
WSAENAMETOOLONG 10063 BSD와 동일: File name too long
WSAEHOSTDOWN 10064 BSD와 동일: Host is down
WSAEHOSTUNREACH 10065 BSD와 동일: No route to host
WSAENOTEMPTY 네트워크 서브시스템이 아직 통신할 준비가 되어 있지 않음 WSAStartup에 의해 반환: Directory not empty
WSAEPROCLIM Too many processes
WSAEUSERS Too many users
WSAEDQUOT Disc quota exceeded
WSAESTALE Stale NFS file handle
WSAEREMOTE Too many levels of remote in path
WSAEDISCON Disconnect
WSASYSNOTREADY 네트워크 서브시스템이 아직 통신할 준비가 되어 있지 않음 WSAStartup에 의해 반환: Network sub-system is unusable
WSAVERNOTSUPPORTED 윈도우즈 소켓 DLL이 요청된 윈속 프로토콜 버전을 지원하지 않음. WSAStartUp에 의해 반환: WinSock DLL cannot support this application
WSANOTINITIALISED WSAStartup함수가 성공적으로 수행되기 전에 모든 윈속 API함수에 의해 반환: WinSock not initialized
WSAHOST_NOT_FOUND 요청된 데이터베이스 정보가 존재하지 않은. 공인 호스트에 의해 확인: Host not found
WSATRY_AGAIN 요청된 정보가 발견되지 않았지만 응답에 대한 공인도가 없음: Non-authoritative host not found
WSANO_RECOVERY 복구할 수 없는 에러가 발생하였음: Non-recoverable error
WSANO_DATA 제공된 이름이 유효하지만 요청된 타입의 정보가 데이터베이스에 없음: Valid name, no data record of requested type
============================================================================================
The following list describes the possible error codes returned by the WSAGetLastError function. Errors are listed in alphabetical order by error macro. Some error codes defined in Winsock2.h are not returned from any function?遊쿴ese are not included in this list.
Return Code/Value Description
WSAEINTR
10004
Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
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).
Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or 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 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
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 sockaddr structure, is smaller than the sizeof(sockaddr).
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?遊즣r instance, calling accept on a socket that is not listening.
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.
WSAEWOULDBLOCK
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.
WSAEINPROGRESS
10036
Operation now in progress.
A blocking operation is currently executing. Windows Sockets only allows a single blocking operation?遊칎r- task or thread?遊쿽 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.
WSAEALREADY
10037
Operation already in progress.
An operation was attempted on a nonblocking socket with an operation already in progress?遊쿴at 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.
WSAENOTSOCK
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.
WSAEDESTADDRREQ
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.
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 was smaller than the datagram itself.
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.
WSAENOPROTOOPT
10042
Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
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.
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.
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 is 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. 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.
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.
WSAEADDRINUSE
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??A class='MIME' class='MIME' href="connect_2.htm">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.
WSAEADDRNOTAVAIL
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).
WSAENETDOWN
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.
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.
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.
WSAECONNABORTED
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.
WSAECONNRESET
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.
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.
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.
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?遊즣r example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
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 have been discontinued.
WSAETIMEDOUT
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.
WSAECONNREFUSED
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?遊쿴at is, one with no server application running.
WSAEHOSTDOWN
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.
WSAEHOSTUNREACH
10065
No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAEPROCLIM
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.
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.
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.
WSANOTINITIALISED
10093
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.
WSAEDISCON
10101
Graceful shutdown in progress.
Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
WSATYPE_NOT_FOUND
10109
Class type not found.
The specified class was not found.
WSAHOST_NOT_FOUND
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.
WSATRY_AGAIN
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.
WSANO_RECOVERY
11003
This is a nonrecoverable error.
This indicates 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.
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 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?遊쬷dicating the host itself exists, but is not directly reachable.
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 Windows function. The Windows function is indicating a problem with one or more parameters.
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, 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 that cannot be completed immediately. A completion indication will be given later when the operation has been completed.
WSA_NOT_ENOUGH_MEMORY
OS dependent
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.
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.
WSAINVALIDPROCTABLE
OS dependent
Invalid procedure table from service provider.
A service provider returned a bogus procedure 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.
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.
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/name space catalogs.
Returned when a provider does not return SUCCESS and does not provide an extended error code. Can indicate a service provider implementation error.
