Windows Sockets在頭文件winsock.h中定義了所有的錯誤碼，它們包括以“WSA”打頭的Windows Sockets實現返回的錯誤碼和Berkeley Sockets定義的錯誤碼全集。定義Berkeley Sockets錯誤碼是爲了確保原有軟件的可移植性。
A.1 Windows 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 NameService）返回的各種失敗。如果Windows Sockets實現沒有使用域名服務，它將使用最合適的代碼。一般地，Windows Sockets應用程序應該將錯誤WSAHOST_NOT_FOUND和WSANO_DATA解釋爲指示關鍵字（名字，地址等）沒有找着，而錯誤WSATRY_AGAIN和WSANO_RECOVERY是提醒名字服務自身是非操作的。
錯誤碼由Windows Sockets 規範定義，在所有同一版本規範的Windows Sockets兼容實現中，它們是一致的。
表A.1 Windows Sockets錯誤碼
|
Windows Sockets錯誤碼 |
Berkeley 對應錯誤碼 |
錯誤號 |
解 釋 |
|
WSAEINTR |
EINTR |
10004 |
同標準C |
|
WSAEBADF |
EBADF |
10009 |
同標準C |
|
WSAEACCES |
EACCES |
10013 |
同標準C |
|
WSAEFAULT |
EFAULT |
10014 |
同標準C |
|
WSAEINVAL |
EINVAL |
10022 |
同標準C |
|
WSAEMFILE |
EMFILE |
10024 |
同標準C |
|
WSAEWOULDBLOCK |
EWOULDBLOCK |
10035 |
同BSD |
|
WSAEINPROGRESS |
EINPROGRESS |
10036 |
當一個阻塞函數正在進行時，調用任何Windows Sockets API函數均返回此錯誤 |
|
WSAEALREADY |
EALREADY |
10037 |
同BSD |
|
WSAENOTSOCK |
ENOTSOCK |
10038 |
同BSD |
|
WSAEDESTADDRREQ |
EDESTADDRREQ |
10039 |
同BSD |
|
WSAEMSGSIZE |
EMSGSIZE |
10040 |
同BSD |
|
WSAEPROTOTYPE |
EPROTOTYPE |
10041 |
同BSD |
|
WSAENOPROTOOPT |
ENOPROTOOPT |
10042 |
同BSD |
|
WSAEPROTONOSUPPORT |
EPROTONOSUPPORT |
10043 |
同BSD |
|
WSAESOCKTNOSUPPORT |
ESOCKTNOSUPPORT |
10044 |
同BSD |
|
WSAEOPNOTSUPP |
EOPNOTSUPP |
10045 |
同BSD |
|
WSAEPFNOSUPPORT |
EPFNOSUPPORT |
10046 |
同BSD |
|
WSAEAFNOSUPPORT |
EAFNOSUPPORT |
10047 |
同BSD |
|
WSAEADDRINUSE |
EADDRINUSE |
10048 |
同BSD |
|
WSAEADDRNOTAVAIL |
EADDRNOTAVAIL |
10049 |
同BSD |
|
WSAENETDOWN |
ENETDOWN |
10050 |
同BSD。任何時候只要Windows Sockets實現檢測到網絡子系統失敗，它就報告此錯誤。 |
|
WSAENETUNREACH |
ENETUNREACH |
10051 |
同BSD |
|
WSAENETRESET |
ENETRESET |
10052 |
同BSD |
|
WSAECONNABORTED |
ECONNABORTED |
10053 |
同BSD |
|
WSAECONNRESET |
ECONNRESET |
10054 |
同BSD |
|
WSAENOBUFS |
ENOBUFS |
10055 |
同BSD |
|
WSAEISCONN |
EISCONN |
10056 |
同BSD |
|
WSAENOTCONN |
ENOTCONN |
10057 |
同BSD |
|
WSAESHUTDOWN |
ESHUTDOWN |
10058 |
同BSD |
|
WSAETOOMANYREFS |
ETOOMANYREFS |
10059 |
同BSD |
|
WSAETIMEDOUT |
ETIMEDOUT |
10060 |
同BSD |
|
WSAECONNREFUSED |
ECONNREFUSED |
10061 |
同BSD |
|
WSAELOOP |
ELOOP |
10062 |
同BSD |
|
WSAENAMETOOLONG |
ENAMETOOLONG |
10063 |
同BSD |
|
WSAEHOSTDOWN |
EHOSTDOWN |
10064 |
同BSD |
|
WSAEHOSTUNREACH |
EHOSTUNREACH |
10065 |
同BSD |
|
WSASYSNOTREADY |
|
10091 |
由WSAStartup() 返回，指示網絡子系統無法使用。 |
|
WSAVERNOTSUPPORTED |
|
10092 |
由WSAStartup() 返回，指示Windows Sockets |
|
WSANOTINITIALISED |
|
10093 |
由除WSAStartup()之外的其它函數返回，指示 尚沒有一次成功的WSAStartup() 調用執行過。 |
|
WSAEDISCON |
|
10101 |
由WSARecv()和WSARecvFrom()返回，指示遠程方已經初始化了一個“雅緻”的shutdown序列。 |
|
WSAHOST_NOT_FOUND |
HOST_NOT_FOUND |
11001 |
同BSD |
|
WSATRY_AGAIN |
TRY_AGAIN |
11002 |
同BSD |
|
WSANO_RECOVERY |
NO_RECOVERY |
11003 |
同BSD |
|
WSANO_DATA |
NO_DATA |
11004 |
同BSD |
A.2 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) Cannotassign 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) Badaddress.
系統檢測到調用試圖使用的一個指針參數指向的是一個非法指針地址。如果應用程序傳遞一個非法的指針值，或緩衝區長度太小，此錯誤發生。例如，參數爲結構sockaddr，但參數的長度小於sizeof(struct sockaddr)。
WSAEHOSTDOWN (10064) Hostis down.
套接字操作因爲目的主機關閉而失敗返回。套接字操作遇到不活動主機。本地主機上的網絡活動沒有初始化。這些條件由錯誤碼WSAETIMEDOUT指示似乎更合適。
WSAEHOSTUNREACH (10065) Noroute 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) Toomany 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) Nobuffer space available.
由於系統缺乏足夠的緩衝區空間，或因爲隊列已滿，在套接字上的操作無法執行。
WSAENOPROTOOPT (10042) Badprotocol 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) Protocolfamily not supported.
協議簇沒有在系統中配置或沒有支持它的實現存在。它與WSAEAFNOSUPPORT有些微的不同，但在絕大多數情況下是可互換的，返回這兩個錯誤的所有Windows Sockets函數的說明見WSAEAFNOSUPPORT的描述。
WSAEPROCLIM (10067) Toomany processes.
Windows Sockets實現可能限制同時使用它的應用程序的數量，如果達到此限制，WSAStartup()函數可能因此錯誤失敗。
WSAEPROTONOSUPPORT (10043) Protocol notsupported.
請求的協議沒有在系統中配置或沒有支持它的實現存在。例如，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 typenot supported.
不支持在此地址族中指定的套接字類型。例如，socket()調用中選擇了可選的套接字類型SOCK_RAW，但是實現卻根本不支持SOCK_RAW類型的套接字。
WSAETIMEDOUT (10060) Connection timed out.
連接請求因被連接方在一個時間週期內不能正確響應而失敗，或已經建立的連接因被連接的主機不能響應而失敗。
WSATYPE_NOT_FOUND (10109) Class typenot found
指定的類沒有找到。
WSAEWOULDBLOCK (10035) Resource temporarily unavailable.
此錯誤由在非阻塞套接字上不能立即完成的操作返回，例如，當套接字上沒有排隊數據可讀時調用了recv()函數。此錯誤不是嚴重錯誤，相應操作應該稍後重試。對於在非阻塞SOCK_STREAM套接字上調用connect()函數來說，報告WSAEWOULDBLOCK是正常的，因爲建立一個連接必須花費一些時間。
WSAHOST_NOT_FOUND (11001) Host not found.
主機未知。此名字不是一個正式主機名，也不是一個別名，它不能在查詢的數據庫中找到。此錯誤也可能在協議和服務查詢中返回，它意味着指定的名字不能在相關數據庫中找到。
WSA_INVALID_HANDLE (OSdependent) 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 (OSdependent) Invalid service provider version number.
服務提供者返回一個不同於2.2的版本號。
WSA_IO_INCOMPLETE (OSdependent) 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 (OSdependent) 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) Thisis a non-recoverable error.
此錯誤碼指示在數據庫查找時發生了某種不可恢復錯誤。它可能是因爲數據庫文件（如BSD兼容的HOSTS、SERVICES或PROTOCOLS文件）找不到，或DNS請求應服務器有嚴重錯誤而返回。
WSAPROVIDERFAILEDINIT (OS dependent) Unableto initialize a service provider.
服務提供者的DLL不能加載（LoadLibrary()失敗）或提供者的WSPStartup/NSPStartup函數失敗。
WSASYSCALLFAILURE (OSdependent) System call failure..
當一個不應該失敗的系統調用失敗時返回。例如，如果WaitForMultipleObjects()調用失敗，或註冊的API不能夠利用協議／名字空間目錄。
WSASYSNOTREADY (10091) Network subsystem is unavailable.
此錯誤由WSAStartup()函數返回，它表示此時Windows Sockets實現因底層用來提供網絡服務的系統不可用。用戶應該檢查：
是否有合適的Windows SocketsDLL文件在當前路徑中。
是否同時使用了多個WinSock實現。如果有多於一個的WINSOCK DLL在系統中，必須確保搜索路徑中第一個WINSOCK DLL文件是當前加載的網絡子系統所需要的。
查看WinSock實現的文檔以確保所有必須的部件都正確地安裝並配置好了。
WSATRY_AGAIN (11002) Non-authoritative host not found.
此錯誤通常是在主機名解析時的臨時錯誤，它意味着本地服務器沒有從授權服務器接收到一個響應。稍後的重試可能會獲得成功。
WSAVERNOTSUPPORTED (10092) WINSOCK.DLLversion out of range.
當前的WinSock實現不支持應用程序指定的Windows Sockets規範版本。檢查是否有舊的Windows SocketsDLL文件正在被訪問。
WSAEDISCON (10101) Graceful shutdown in progress.
由WSARecv()和WSARecvFrom()函數返回，指示遠程方已經初始化了一個“雅緻”的關閉序列。
WSA_OPERATION_ABORTED (OS dependent) Overlapped operationaborted.
因爲套接字的關閉，一個重疊操作被取消，或是執行了WSAIoctl()函數的SIO_FLUSH命令。
以下英文解釋來自MSDN:
The following is alist of possible error codes returned by the WSAGetLastError call, along withtheir extended explanations. Errors are listed in alphabetical order by errormacro. Some error codes defined in WINSOCK2.H are not returned from anyfunction - these have not been listed here.
WSAEACCES
(10013)
Permission denied.
An attempt wasmade to access a socket in a way forbidden by its access permissions. Anexample is using a broadcast address for sendto without broadcast permission being setusing setsockopt(SO_BROADCAST).
WSAEADDRINUSE
(10048)
Address already in use.
Only one usage ofeach socket address (protocol/IP address/port) is normally permitted. Thiserror occurs if an application attempts to bind a socket to an IP address/port that hasalready 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 thatneed tobind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Clientapplications 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 specificaddress is "committed." This could happen with a call to otherfunction later, including connect, listen, WSAConnect orWSAJoinLeaf.
WSAEADDRNOTAVAIL
(10049)
Cannot assign requested address.
The requestedaddress is not valid in its context. Normally results from an attempt to bind to an address that is not valid for thelocal machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTowhen 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 addressincompatible with the requested protocol was used. All sockets are created withan associated "address family" (i.e. AF_INET for Internet Protocols)and a generic protocol type (i.e. SOCK_STREAM). This error will be returned ifan incorrect protocol is explicitly requested in the socket call, or if an address of the wrong familyis used for a socket, e.g. in sendto.
WSAEALREADY
(10037)
Operation already in progress.
An operation wasattempted on a non-blocking socket that already had an operation in progress -i.e. calling connecta second time on a non-blocking socket that is already connecting, orcanceling an asynchronous request (WSAAsyncGetXbyY) that has already beencanceled or completed.
WSAECONNABORTED
(10053)
Software caused connection abort.
An establishedconnection was aborted by the software in your host machine, possibly due to adata transmission timeout or protocol error.
WSAECONNREFUSED
(10061)
Connection refused.
No connectioncould be made because the target machine actively refused it. This usuallyresults from trying to connect to a service that is inactive on the foreignhost - i.e. one with no server application running.
WSAECONNRESET
(10054)
Connection reset by peer.
A existingconnection was forcibly closed by the remote host. This normally results if thepeer 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 errormay 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 operationsfail with WSAECONNRESET.
WSAEDESTADDRREQ
(10039)
Destination address required.
A required addresswas omitted from an operation on a socket. For example, this error will bereturned if sendto is called with the remote address of ADDR_ANY.
WSAEFAULT
(10014)
Bad address.
The systemdetected an invalid pointer address in attempting to use a pointer argument ofa call. This error occurs if an application passes an invalid pointer value, orif the length of the buffer is too small. For instance, if the length of anargument which is a struct sockaddr is smaller than sizeof(struct sockaddr).
WSAEHOSTDOWN
(10064)
Host is down.
A socket operationfailed because the destination host was down. A socket operation encountered adead host. Networking activity on the local host has not been initiated. Theseconditions are more likely to be indicated by the error WSAETIMEDOUT.
WSAEHOSTUNREACH
(10065)
No route to host.
A socket operationwas attempted to an unreachable host. See WSAENETUNREACH
WSAEINPROGRESS
(10036)
Operation now in progress.
A blockingoperation is currently executing. Windows Sockets only allows a single blockingoperation to be outstanding per task (or thread), and if any other functioncall is made (whether or not it references that or any other socket) thefunction fails with the WSAEINPROGRESS error.
WSAEINTR
(10004)
Interrupted function call.
A blockingoperation was interrupted by a call to WSACancelBlockingCall.
WSAEINVAL
(10022)
Invalid argument.
Some invalidargument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it alsorefers to the current state of the socket - for instance, calling accept on a socket that is notlistening.
WSAEISCONN
(10056)
Socket is already connected.
A connect requestwas made on an already connected socket. Some implementations also return thiserror if sendto is called on a connected SOCK_DGRAM socket (For SOCK_STREAM sockets, the to parameter in sendto is ignored), although otherimplementations treat this as a legal occurrence.
WSAEMFILE
(10024)
Too many open files.
Too many opensockets. Each implementation may have a maximum number of socket handlesavailable, either globally, per process or per thread.
WSAEMSGSIZE
(10040)
Message too long.
A message sent ona datagram socket was larger than the internal message buffer or some othernetwork limit, or the buffer used to receive a datagram into was smaller thanthe datagram itself.
WSAENETDOWN
(10050)
Network is down.
A socket operationencountered a dead network. This could indicate a serious failure of thenetwork system (i.e. the protocol stack that the WinSock DLL runs over), thenetwork interface, or the local network itself.
WSAENETRESET
(10052)
Network dropped connection on reset.
The connection hasbeen broken due to "keep-alive" activity detecting a failure whilethe operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVEon a connection that has already failed.
WSAENETUNREACH
(10051)
Network is unreachable.
A socket operationwas attempted to an unreachable network. This usually means the local softwareknows no route to reach the remote host.
WSAENOBUFS
(10055)
No buffer space available.
An operation on asocket could not be performed because the system lacked sufficient buffer spaceor 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 sendor receive data was disallowed because the socket is not connected and (whensending on a datagram socket using sendto) no address was supplied. Any other type of operation might also returnthis error - for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
WSAENOTSOCK
(10038)
Socket operation on non-socket.
An operation wasattempted on something that is not a socket. Either the socket handle parameterdid not reference a valid socket, or for select, a member of an fd_set was not valid.
WSAEOPNOTSUPP
(10045)
Operation not supported.
The attemptedoperation is not supported for the type of object referenced. Usually thisoccurs 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 protocolfamily has not been configured into the system or no implementation for itexists. Has a slightly different meaning to WSAEAFNOSUPPORT, but isinterchangeable in most cases, and all Windows Sockets functions that returnone of these specify WSAEAFNOSUPPORT.
WSAEPROCLIM
(10067)
Too many processes.
A Windows Socketsimplementation may have a limit on the number of applications that may use itsimultaneously.WSAStartup may fail with this error if the limit has been reached.
WSAEPROTONOSUPPORT
(10043)
Protocol not supported.
The requestedprotocol has not been configured into the system, or no implementation for itexists. For example, asocket call requests a SOCK_DGRAM socket, but specifies a stream protocol.
WSAEPROTOTYPE
(10041)
Protocol wrong type for socket.
A protocol wasspecified in the socket function call that does not support the semantics of the socket typerequested. For example, the ARPA Internet UDP protocol cannot be specified witha socket type of SOCK_STREAM.
WSAESHUTDOWN
(10058)
Cannot send after socket shutdown.
A request to sendor receive data was disallowed because the socket had already been shut down inthat direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sendingor receiving or both has been discontinued.
WSAESOCKTNOSUPPORT
(10044)
Socket type not supported.
The support forthe 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 notsupport SOCK_RAW sockets at all.
WSAETIMEDOUT
(10060)
Connection timed out.
A connectionattempt failed because the connected party did not properly respond after aperiod of time, or established connection failed because connected host hasfailed to respond.
WSATYPE_NOT_FOUND
(10109)
Class type not found.
The specifiedclass was not found.
WSAEWOULDBLOCK
(10035)
Resource temporarily unavailable.
This error isreturned from operations on non-blocking sockets that cannot be completedimmediately, for examplerecv 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 tobe reported as the result from calling connect on a non-blocking SOCK_STREAM socket, since some time must elapse for theconnection to be established.
WSAHOST_NOT_FOUND
(11001)
Host not found.
No such host isknown. The name is not an official hostname or alias, or it cannot be found inthe database(s) being queried. This error may also be returned for protocol andservice queries, and means the specified name could not be found in the relevantdatabase.
WSA_INVALID_HANDLE
(OS dependent)
Specified event object handle is invalid.
An applicationattempts to use an event object, but the specified handle is not valid.
WSA_INVALID_PARAMETER
(OS dependent)
One or more parameters are invalid.
An applicationused a Windows Sockets function which directly maps to a Win32 function. TheWin32 function is indicating a problem with one or more parameters.
WSAINVALIDPROCTABLE
(OS dependent)
Invalid procedure table from service provider.
A service providerreturned a bogus proc table to WS2_32.DLL. (Usually caused by one or more ofthe function pointers being NULL.)
WSAINVALIDPROVIDER
(OS dependent)
Invalid service provider version number.
A service providerreturned a version number other than 2.0.
WSA_IO_INCOMPLETE
(OS dependent)
Overlapped I/O event object not in signaled state.
The applicationhas tried to determine the status of an overlapped operation which is not yetcompleted. Applications that use WSAGetOverlappedResult (with the fWait flag set to false) in a polling mode to determine when an overlappedoperation has completed will get this error code until the operation iscomplete.
WSA_IO_PENDING
(OS dependent)
Overlapped operations will complete later.
The applicationhas initiated an overlapped operation which cannot be completed immediately. Acompletion indication will be given at a later time when the operation has beencompleted.
WSA_NOT_ENOUGH_MEMORY
(OS dependent)
Insufficient memory available.
An applicationused a Windows Sockets function which directly maps to a Win32 function. TheWin32 function is indicating a lack of required memory resources.
WSANOTINITIALISED
(10093)
Successful WSAStartup not yet performed.
Either theapplication hasn't called WSAStartup or WSAStartup failed. The application may be accessing a socket which the current activetask 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 nameis valid and was found in the database, but it does not have the correctassociated data being resolved for. The usual example for this is a hostname-> address translation attempt (using gethostbyname orWSAAsyncGetHostByName) which uses the DNS (Domain Name Server),and an MX record is returned but no A record - indicating the host itselfexists, but is not directly reachable.
WSANO_RECOVERY
(11003)
This is a non-recoverable error.
This indicatessome sort of non-recoverable error occurred during a database lookup. This maybe because the database files (e.g. BSD-compatible HOSTS, SERVICES or PROTOCOLSfiles) could not be found, or a DNS request was returned by the server with asevere error.
WSAPROVIDERFAILEDINIT
(OS dependent)
Unable to initialize a service provider.
Either a serviceprovider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup/NSPStartupfunction failed.
WSASYSCALLFAILURE
(OS dependent)
System call failure.
Returned when asystem call that should never fail does. For example, if a call to WaitForMultipleObjects fails or one ofthe registry functions fails trying to manipulate theprotocol/namespacecatalogs.
WSASYSNOTREADY
(10091)
Network subsystem is unavailable.
This error isreturned by WSAStartup if the Windows Sockets implementation cannot function at this time becausethe underlying system it uses to provide network services is currentlyunavailable. Users should check:
· that the appropriate Windows Sockets DLLfile is in the current path,
· that they are not trying to use more thanone Windows Sockets implementation simultaneously. If there is more than oneWINSOCK DLL on your system, be sure the first one in the path is appropriatefor the network subsystem currently loaded.
· the Windows Sockets implementationdocumentation to be sure all necessary components are currently installed andconfigured correctly.
WSATRY_AGAIN
(11002)
Non-authoritative host not found.
This is usually atemporary error during hostname resolution and means that the local server didnot receive a response from an authoritative server. A retry at some time latermay be successful.
WSAVERNOTSUPPORTED
(10092)
WINSOCK.DLL version out of range.
The currentWindows Sockets implementation does not support the Windows Socketsspecification version requested by the application. Check that no old WindowsSockets DLL files are being accessed.
WSAEDISCON
(10094)
Graceful shutdown in progress.
Returned by WSARecv and WSARecvFrom to indicate the remote party has initiateda graceful shutdown sequence.
WSA_OPERATION_ABORTED
(OS dependent)
Overlapped operation aborted.
An overlappedoperation was canceled due to the closure of the socket, or the execution ofthe SIO_FLUSH command in WSAIoctl.