Windows Sockets 錯誤碼

Windows Sockets 錯誤碼及出錯原因

 

轉載

 

windows sockets 錯誤碼及出錯原因[轉]

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 name service）返回的各種失敗。假如windows sockets實現沒有使用域名服務，它將使用最合適的代碼。一般地，windows sockets應用程序應該將錯誤wsahost_not_found和wsano_data解釋爲指示要害字（名字，地址等）沒有找着，而錯誤 wsatry_again和wsano_recovery是提醒名字服務自身是非操作的。

     錯誤碼由windows sockets 規範定義，在所有同一版本規範的windows sockets兼容實現中，它們是一致的。

表a.1  windows sockets錯誤碼

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)             cannot assign requested address.

被請求的地址在它的環境中是不合法的。通常地在bind()函數試圖將一個本地機器不合法的地址綁紮到套接字時產生。它也可能在 connect()、sendto()、wsaconnect()、wsajoinleaf()或wsasendto()函數調用時因遠程機器的遠程地址 或端口號非法（如0地址或0端口號）而產生。

wsaeafnosupport            (10047)             address family not supported by protocol family.

使用的地址與被請求的協議不兼容。所有的套接字在創建時都與一個地址族（如ip協議對應的af_inet）和一個通用的協議類型（如 sock_stream）聯繫起來。假如在socket()調用中明確地要求一個不正確的協議，或在調用sendto()等函數時使用了對套接字來說是錯 誤的地址族的地址，該錯誤返回。

wsaealready                    (10037)             operation already in progress.

當在非阻塞套接字上已經有一個操作正在進行時，又有一個操作試圖在其上執行則產生此錯誤。如：在一個正在進行連接的非阻塞套接字上第二次調用connect()函數；或取消一個已經被取消或已完成的異步請求（wsaasyncgetxbyy()）。

wsaeconnaborted           (10053)             software caused connection abort.

一個已建立的連接被你的主機上的軟件終止，可能是因爲一次數據傳輸超時或是協議錯誤。

wsaeconnrefused            (10061)             connection refused.

因爲目標主機主動拒絕，連接不能建立。這通常是因爲試圖連接到一個遠程主機上不活動的服務，如沒有服務器應用程序處於執行狀態。

wsaeconnreset                (10054)             connection reset by peer.

存在的連接被遠程主機強制關閉。通常原因爲：遠程主機上對等方應用程序忽然停止運行，或遠程主機重新啓動，或遠程主機在遠程方套接字上使用了 “強制”關閉（參見setsockopt(so_linger)）。另外，在一個或多個操作正在進行時，假如連接因“keep-alive”活動檢測到一 個失敗而中斷，也可能導致此錯誤。此時，正在進行的操作以錯誤碼wsaenetreset失敗返回，後續操作將失敗返回錯誤碼 wsaeconnreset。

wsaedestaddrreq           (10039)             destination address required.

在套接字上一個操作所必須的地址被遺漏。例如，假如sendto()函數被調用且遠程地址爲addr_any時，此錯誤被返回。

wsaefault                          (10014)             bad address.

系統檢測到調用試圖使用的一個指針參數指向的是一個非法指針地址。假如應用程序傳遞一個非法的指針值，或緩衝區長度太小，此錯誤發生。例如，參數爲結構sockaddr，但參數的長度小於sizeof(struct sockaddr)。

wsaehostdown                 (10064)             host is down.

套接字操作因爲目的主機關閉而失敗返回。套接字操作碰到不活動主機。本地主機上的網絡活動沒有初始化。這些條件由錯誤碼wsaetimedout指示似乎更合適。

wsaehostunreach           (10065)             no route to host.

試圖和一個不可達主機進行套接字操作。參見wsaenetunreach。

wsaeinprogress               (10036)             operation now in progress.

一個阻塞操作正在執行。windows sockets只答應一個任務（或線程）在同一時間可以有一個未完成的阻塞操作，假如此時調用了任何函數（不管此函數是否引用了該套接字或任何其它套接字），此函數將以錯誤碼wsaeinprogress返回。

wsaeintr                            (10004)             interrupted function call.

阻塞操作被函數wsacancelblockingcall ()調用所中斷。

wsaeinval                           (10022)             invalid argument.

提供了非法參數（例如，在使用setsockopt()函數時指定了非法的level）。在一些實例中，它也可能與套接字的當前狀態相關，例如，在套接字沒有使用listen()使其處於監聽時調用accept()函數。

wsaeisconn                        (10056)             socket is already connected.

連接請求發生在已經連接的套接字上。一些實現對於在已連接sock_dgram套接字上使用sendto()函數的情況也返回此錯誤（對於sock_stream套接字，sendto()函數的to參數被忽略），儘管其它一些實現將此操作視爲合法事件。

wsaemfile                          (10024)             too many open files.

打開了太多的套接字。不管是對整個系統還是每一進程或線程，windows sockets實現都可能有一個最大可用的套接字句柄數。

wsaemsgsize                      (10040)             message too long.

在數據報套接字上發送的一個消息大於內部消息緩衝區或一些其它網絡限制，或者是用來接受數據報的緩衝區小於數據報本身。

wsaenetdown                    (10050)             network is down.

套接字操作碰到一個不活動的網絡。此錯誤可能指示網絡系統（例如winsock dll運行的協議棧）、網絡接口或本地網絡本身發生了一個嚴重的失敗。

wsaenetreset                   (10052)             network dropped connection on reset.

在操作正在進行時連接因“keep-alive”檢測到失敗而中斷。也可能由setsockopt()函數返回，假如試圖使用它在一個已經失敗的連接上設置so_keepalive。

wsaenetunreach              (10051)             network is unreachable.

試圖和一個無法到達的網絡進行套接字操作。它經常意味着本地軟件不知道到達遠程主機的路由。

wsaenobufs                        (10055)             no buffer space available.

由於系統缺乏足夠的緩衝區空間，或因爲隊列已滿，在套接字上的操作無法執行。

wsaenoprotoopt             (10042)             bad protocol option.

在getsockopt()或setsockopt()調用中，指定了一個未知的、非法的或不支持的選項或層（level）。

wsaenotconn                    (10057)             socket is not connected.

因爲套接字沒有連接，發送或接收數據的請求不被答應，或者是使用sendto()函數在數據報套接字上發送時沒有提供地址。任何其它類型的操作也可以返回此錯誤，例如，使用setsockopt()函數在一個已重置的連接上設置so_keepalive。

wsaenotsock                    (10038)             socket operation on non-socket.

操作試圖不是在套接字上進行。它可能是套接字句柄參數沒有引用到一個合法套接字，或者是調用select()函數時，一個fd_set中的成員不合法。

wsaeopnotsupp                (10045)             operation not supported.

對於引用的對象的類型來說，試圖進行的操作不支持。通常它發生在套接字不支持此操作的套接字描述符上，例如，試圖在數據報套接字上接收連接。

wsaepfnosupport            (10046)             protocol family not supported.

協議簇沒有在系統中配置或沒有支持它的實現存在。它與wsaeafnosupport有些微的不同，但在絕大多數情況下是可互換的，返回這兩個錯誤的所有windows sockets函數的說明見wsaeafnosupport的描述。

wsaeproclim                     (10067)             too many processes.

windows sockets實現可能限制同時使用它的應用程序的數量，假如達到此限制，wsastartup()函數可能因此錯誤失敗。

wsaeprotonosupport     (10043)             protocol not supported.

請求的協議沒有在系統中配置或沒有支持它的實現存在。例如，socket()調用請求一個sock_dgram套接字，但指定的是流協議。

wsaeprototype                (10041)             protocol wrong type for socket.

在socket()函數調用中指定的協議不支持請求的套接字類型的語義。例如，arpa internet udp協議不能和sock_stream套接字類型一同指定。

wsaeshutdown                 (10058)             cannot send after socket shutdown.

因爲套接字在相應方向上已經被先前的shutdown()調用關閉，因此該方向上的發送或接收請求不被答應。通過調用shutdown()函數來請求對套接字的部分關閉，它發送一個信號來停止發送或接收或雙向操作。

wsaesocktnosupport    (10044)             socket type not supported.

不支持在此地址族中指定的套接字類型。例如，socket()調用中選擇了可選的套接字類型sock_raw，但是實現卻根本不支持sock_raw類型的套接字。

wsaetimedout                   (10060)             connection timed out.

連接請求因被連接方在一個時間週期內不能正確響應而失敗，或已經建立的連接因被連接的主機不能響應而失敗。

wsatype_not_found        (10109)             class type not found

     指定的類沒有找到。

wsaewouldblock           (10035)             resource temporarily unavailable.

此錯誤由在非阻塞套接字上不能立即完成的操作返回，例如，當套接字上沒有排隊數據可讀時調用了recv()函數。此錯誤不是嚴重錯誤，相應操作 應該稍後重試。對於在非阻塞sock_stream套接字上調用connect()函數來說，報告wsaewouldblock是正常的，因爲建立一個連 接必須花費一些時間。

wsahost_not_found        (11001)             host not found.

主機未知。此名字不是一個正式主機名，也不是一個別名，它不能在查詢的數據庫中找到。此錯誤也可能在協議和服務查詢中返回，它意味着指定的名字不能在相關數據庫中找到。

wsa_invalid_handle        (os dependent) specified event object handle is invalid.

應用程序試圖使用一個事件對象，但指定的句柄非法。

wsa_invalid_parameter (os dependent) one or more parameters are invalid.

應用程序使用了一個直接映射到win32函數的winsock函數，而win32函數指示一個或多個參數有問題。

wsainvalidproctable    (os dependent)      invalid procedure table from service provider.

服務提供者返回了一個假的ws2_32.dll程序（procedure）表。這通常是由一個或多個函數指針爲空引起。

wsainvalidprovider        (os dependent)      invalid service provider version number.

     服務提供者返回一個不同於2.2的版本號。

wsa_io_incomplete         (os dependent) overlapped i/o event object not in signaled state.

應用程序試圖檢測一個沒有完成的重疊操作的狀態。應用程序使用函數wsagetoverlappedresult()（參數fwait設置爲false）以輪詢模式檢測一個重疊操作是否完成時將得到此錯誤碼，除非該操作已經完成。

wsa_io_pending                 (os dependent) overlapped operations will complete later.

應用程序已經初始化了一個不能立即完成的重疊操作。當稍後此操作完成時將有完成指示。

wsa_not_enough_memory  (os dependent)       insufficient memory available.

應用程序使用了一個直接映射到win32函數的winsock函數，而win32函數指示缺乏必要的內存資源。

wsanotinitialised           (10093)             successful wsastartup() not yet performed.

應用程序沒有調用wsastartup()函數，或函數wsastartup()調用失敗了。應用程序可能訪問了不屬於當前活動任務的套接字（例如試圖在任務間共享套接字），或調用了過多的wsacleanup()函數。

wsano_data                        (11004)             valid name, no data record of requested type.

請求的名字合法並且在數據庫中找到了，但它沒有正確的關聯數據用於解析。此錯誤的通常例子是主機名到地址（使用gethostbyname() 或wsaasyncgethostbyname()函數）的dns轉換請求，返回了mx（mail exchanger）記錄但是沒有a（address）記錄，它指示主機本身是存在的，但是不能直接到達。

wsano_recovery              (11003)             this is a non-recoverable error.

此錯誤碼指示在數據庫查找時發生了某種不可恢復錯誤。它可能是因爲數據庫文件（如bsd兼容的hosts、services或protocols文件）找不到，或dns請求應服務器有嚴重錯誤而返回。

wsaproviderfailedinit  (os dependent)      unable to initialize a service provider.

服務提供者的dll不能加載（loadlibrary()失敗）或提供者的wspstartup/nspstartup函數失敗。

wsasyscallfailure         (os dependent)      system call failure..

當一個不應該失敗的系統調用失敗時返回。例如，假如waitformultipleobjects()調用失敗，或註冊的api不能夠利用協議／名字空間目錄。

wsasysnotready              (10091)             network subsystem is unavailable.

此錯誤由wsastartup()函數返回，它表示此時windows sockets實現因底層用來提供網絡服務的系統不可用。用戶應該檢查：

    是否有合適的windows sockets dll文件在當前路徑中。

    是否同時使用了多個winsock實現。假如有多於一個的winsock dll在系統中，必須確保搜索路徑中第一個winsock dll文件是當前加載的網絡子系統所需要的。

    查看winsock實現的文檔以確保所有必須的部件都正確地安裝並配置好了。

wsatry_again                    (11002)             non-authoritative host not found.

此錯誤通常是在主機名解析時的臨時錯誤，它意味着本地服務器沒有從授權服務器接收到一個響應。稍後的重試可能會獲得成功。

wsavernotsupported     (10092)             winsock.dll version out of range.

當前的winsock實現不支持應用程序指定的windows sockets規範版本。檢查是否有舊的windows sockets dll文件正在被訪問。

wsaediscon                        (10101)             graceful shutdown in progress.

由wsarecv()和wsarecvfrom()函數返回，指示遠程方已經初始化了一個“雅緻”的關閉序列。

wsa_operation_aborted   (os dependent) overlapped operation aborted.

     因爲套接字的關閉，一個重疊操作被取消，或是執行了wsaioctl()函數的sio_flush命令。

以下英文解釋來自msdn:

error codes

the following is a list of possible error codes returned by the wsagetlasterror call, along with their extended explanations. errors are listed in alphabetical order by error macro. some error codes defined in winsock2.h are not returned from any function - these have not been listed here.

wsaeacces

(10013)

permission denied.

an attempt was made to access a socket in a way forbidden by its access permissions. an example is using a broadcast address for sendto without broadcast permission being set using setsockopt(so_broadcast).

wsaeaddrinuse

(10048)

address already in use.

only one usage of each socket address (protocol/ip address/port) is normally permitted. this error occurs if an application attempts to bind a socket to an ip address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. for server applications that need to bind multiple sockets to the same port number, consider using setsockopt(so_reuseaddr). client applications usually need not call bind at all - connect will choose an unused port automatically. when bind is called with a wild-card address (involving addr_any), a wsaeaddrinuse error could be delayed until the specific address is "committed." this could happen with a call to other function later, including connect, listen, wsaconnect or wsajoinleaf.

wsaeaddrnotavail

(10049)

cannot assign requested address.

the requested address is not valid in its context. normally results from an attempt to bind to an address that is not valid for the local machine. this can also result from connect, sendto, wsaconnect, wsajoinleaf, or wsasendto when the remote address or port is not valid for a remote machine (e.g. address or port 0).

wsaeafnosupport

(10047)

address family not supported by protocol family.

an address incompatible with the requested protocol was used. all sockets are created with an associated "address family" (i.e. af_inet for internet protocols) and a generic protocol type (i.e. sock_stream). this error will be returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, e.g. in sendto.

wsaealready

(10037)

operation already in progress.

an operation was attempted on a non-blocking socket that already had an operation in progress - i.e. calling connect a second time on a non-blocking socket that is already connecting, or canceling an asynchronous request (wsaasyncgetxbyy) that has already been canceled or completed.

wsaeconnaborted

(10053)

software caused connection abort.

an established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error.

wsaeconnrefused

(10061)

connection refused.

no connection could be made because the target machine actively refused it. this usually results from trying to connect to a service that is inactive on the foreign host - i.e. one with no server application running.

wsaeconnreset

(10054)

connection reset by peer.

a existing connection was forcibly closed by the remote host. this normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close" (see setsockopt for more information on the so_linger option on the remote socket.) this error may also result if a connection was broken due to "keep-alive" activity detecting a failure while one or more operations are in progress. operations that were in progress fail with wsaenetreset. subsequent operations fail with wsaeconnreset.

wsaedestaddrreq

(10039)

destination address required.

a required address was omitted from an operation on a socket. for example, this error will be returned if sendto is called with the remote address of addr_any.

wsaefault

(10014)

bad address.

the system detected an invalid pointer address in attempting to use a pointer argument of a call. this error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. for instance, if the length of an argument which is a struct sockaddr is smaller than sizeof(struct sockaddr).

wsaehostdown

(10064)

host is down.

a socket operation failed because the destination host was down. a socket operation encountered a dead host. networking activity on the local host has not been initiated. these conditions are more likely to be indicated by the error wsaetimedout.

wsaehostunreach

(10065)

no route to host.

a socket operation was attempted to an unreachable host. see wsaenetunreach

wsaeinprogress

(10036)

operation now in progress.

a blocking operation is currently executing. windows sockets only allows a single blocking operation to be outstanding per task (or thread), and if any other function call is made (whether or not it references that or any other socket) the function fails with the wsaeinprogress error.

wsaeintr

(10004)

interrupted function call.

a blocking operation was interrupted by a call to wsacancelblockingcall.

wsaeinval

(10022)

invalid argument.

some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). in some instances, it also refers to the current state of the socket - for instance, calling accept on a socket that is not listening.

wsaeisconn

(10056)

socket is already connected.

a connect request was made on an already connected socket. some implementations also return this error if sendto is called on a connected sock_dgram socket (for sock_stream sockets, the to parameter in sendto is ignored), although other implementations treat this as a legal occurrence.

wsaemfile

(10024)

too many open files.

too many open sockets. each implementation may have a maximum number of socket handles available, either globally, per process or per thread.

wsaemsgsize

(10040)

message too long.

a message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.

wsaenetdown

(10050)

network is down.

a socket operation encountered a dead network. this could indicate a serious failure of the network system (i.e. the protocol stack that the winsock dll runs over), the network interface, or the local network itself.

wsaenetreset

(10052)

network dropped connection on reset.

the connection has been broken due to "keep-alive" activity detecting a failure while the operation was in progress. it can also be returned by setsockopt if an attempt is made to set so_keepalive on a connection that has already failed.

wsaenetunreach

(10051)

network is unreachable.

a socket operation was attempted to an unreachable network. this usually means the local software knows no route to reach the remote host.

wsaenobufs

(10055)

no buffer space available.

an operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

wsaenoprotoopt

(10042)

bad protocol option.

an unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.

wsaenotconn

(10057)

socket is not connected.

a request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. any other type of operation might also return this error - for example, setsockopt setting so_keepalive if the connection has been reset.

wsaenotsock

(10038)

socket operation on non-socket.

an operation was attempted on something that is not a socket. either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

wsaeopnotsupp

(10045)

operation not supported.

the attempted operation is not supported for the type of object referenced. usually this occurs when a socket descriptor to a socket that cannot support this operation, for example, trying to accept a connection on a datagram socket.

wsaepfnosupport

(10046)

protocol family not supported.

the protocol family has not been configured into the system or no implementation for it exists. has a slightly different meaning to wsaeafnosupport, but is interchangeable in most cases, and all windows sockets functions that return one of these specify wsaeafnosupport.

wsaeproclim

(10067)

too many processes.

a windows sockets implementation may have a limit on the number of applications that may use it simultaneously. wsastartup may fail with this error if the limit has been reached.

wsaeprotonosupport

(10043)

protocol not supported.

the requested protocol has not been configured into the system, or no implementation for it exists. for example, a socket call requests a sock_dgram socket, but specifies a stream protocol.

wsaeprototype

(10041)

protocol wrong type for socket.

a protocol was specified in the socket function call that does not support the semantics of the socket type requested. for example, the arpa internet udp protocol cannot be specified with a socket type of sock_stream.

wsaeshutdown

(10058)

cannot send after socket shutdown.

a request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. by calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving or both has been discontinued.

wsaesocktnosupport

(10044)

socket type not supported.

the support for the specified socket type does not exist in this address family. for example, the optional type sock_raw might be selected in a socket call, and the implementation does not support sock_raw sockets at all.

wsaetimedout

(10060)

connection timed out.

a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

wsatype_not_found

(10109)

class type not found.

the specified class was not found.

wsaewouldblock

(10035)

resource temporarily unavailable.

this error is returned from operations on non-blocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. it is a non-fatal error, and the operation should be retried later. it is normal for wsaewouldblock to be reported as the result from calling connect on a non-blocking sock_stream socket, since some time must elapse for the connection to be established.

wsahost_not_found

(11001)

host not found.

no such host is known. the name is not an official hostname or alias, or it cannot be found in the database(s) being queried. this error may also be returned for protocol and service queries, and means the specified name could not be found in the relevant database.

wsa_invalid_handle

(os dependent)

specified event object handle is invalid.

an application attempts to use an event object, but the specified handle is not valid.

wsa_invalid_parameter

(os dependent)

one or more parameters are invalid.

an application used a windows sockets function which directly maps to a win32 function. the win32 function is indicating a problem with one or more parameters.

wsainvalidproctable

(os dependent)

invalid procedure table from service provider.

a service provider returned a bogus proc table to ws2_32.dll. (usually caused by one or more of the function pointers being null.)

wsainvalidprovider

(os dependent)

invalid service provider version number.

a service provider returned a version number other than 2.0.

wsa_io_incomplete

(os dependent)

overlapped i/o event object not in signaled state.

the application has tried to determine the status of an overlapped operation which is not yet completed. applications that use wsagetoverlappedresult (with the fwait flag set to false) in a polling mode to determine when an overlapped operation has completed will get this error code until the operation is complete.

wsa_io_pending

(os dependent)

overlapped operations will complete later.

the application has initiated an overlapped operation which cannot be completed immediately. a completion indication will be given at a later time when the operation has been completed.

wsa_not_enough_memory

(os dependent)

insufficient memory available.

an application used a windows sockets function which directly maps to a win32 function. the win32 function is indicating a lack of required memory resources.

wsanotinitialised

(10093)

successful wsastartup not yet performed.

either the application hasn't called wsastartup or wsastartup failed. the application may be accessing a socket which the current active task does not own (i.e. trying to share a socket between tasks), or wsacleanup has been called too many times.

wsano_data

(11004)

valid name, no data record of requested type.

the requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. the usual example for this is a hostname -> address translation attempt (using gethostbyname or wsaasyncgethostbyname) which uses the dns (domain name server), and an mx record is returned but no a record - indicating the host itself exists, but is not directly reachable.

wsano_recovery

(11003)

this is a non-recoverable error.

this indicates some sort of non-recoverable error occurred during a database lookup. this may be because the database files (e.g. bsd-compatible hosts, services or protocols files) could not be found, or a dns request was returned by the server with a severe error.

wsaproviderfailedinit

(os dependent)

unable to initialize a service provider.

either a service provider's dll could not be loaded (loadlibrary failed) or the provider's wspstartup/nspstartup function failed.

wsasyscallfailure

(os dependent)

system call failure.

returned when a system call that should never fail does. for example, if a call to waitformultipleobjects fails or one of the registry functions fails trying to manipulate theprotocol/namespace catalogs.

wsasysnotready

(10091)

network subsystem is unavailable.

this error is returned by wsastartup if the windows sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. users should check:

• that the appropriate windows sockets dll file is in the current path,
• that they are not trying to use more than one windows sockets implementation simultaneously. if there is more than one winsock dll on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded.
• the windows sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.

wsatry_again

(11002)

non-authoritative host not found.

this is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. a retry at some time later may be successful.

wsavernotsupported

(10092)

winsock.dll version out of range.

the current windows sockets implementation does not support the windows sockets specification version requested by the application. check that no old windows sockets dll files are being accessed.

wsaediscon

(10094)

graceful shutdown in progress.

returned by wsarecv and wsarecvfrom to indicate the remote party has initiated a graceful shutdown sequence.

wsa_operation_aborted

(os dependent)

overlapped operation aborted.

an overlapped operation was canceled due to the closure of the socket, or the execution of the sio_flush command in wsaioctl.