Kbase 16731: 1432 networking error on Windows - winsock errno listing
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/7/1999 |
|
1432 networking error on Windows - winsock errno listing
Title: 1432 Networking Error on Windows - winsock errno listing
Knowledgebase number: 16731
Creation Date: 7-Mar-1997
Modification Date: 7-May-1999
This document applies to
Version: Windows versions of Progress
Release Number: 7.3E, 8.1A and above
The WinSock TCP API is used by PROGRESS for all TCP/IP communications
on Windows and Windows NT products on 7.3 and after. It is also used
by 7.2 (_prowin executable) and 6.2 (_prowinf executable).
WinSock uses a function to report error status, instead of the errno
variable. On all 16-bit PROGRESS releases up to 7.3D, plus 8.0A,
PROGRESS gets the error information from errno, resulting in incorrect
error codes. In those cases, you will see errno zero or two, but these
errno codes are not WinSock networking errors.
Beginning with PROGRESS 7.3E, 8.1A and later versions, PROGRESS will
correctly report WinSock errors. A valid WinSock error number is
greater than 10000.
The following is a table of WinSock error codes, the mnemonic and it's
description. For a suggested aproach to the most common errors, see
kbase 16163 - PROGRESS netw. errors: What they mean and how 2
troubleshoot.
Error Mnemonic Description
10004 WSAEINTR Interrupted system call
10009 WSAEBADF Bad file number
10014 WSAEFAULT Bad address
10022 WSAEINVAL Invalid argument
10024 WSAEMFILE Too many open files
10035 WSAEWOULDBLOCK Operation would block
10036 WSAEINPROGRESS Operation now in progress
10037 WSAEALREADY Operation already in progress
10038 WSAENOTSOCK Socket operation on non-socket
10039 WSAEDESTADDRREQ Destination address required
10040 WSAEMSGSIZE Message too long
10041 WSAEPROTOTYPE Protocol wrong type for socket
10042 WSAENOPROTOOPT Protocol not available
10043 WSAEPROTONOSUPPORT Protocol not supported
10044 WSAESOCKTNOSUPPORT Socket type not supported
10045 WSAEOPNOTSUPP Operation not supported on socket
10046 WSAEPFNOSUPPORT Protocol family not supported
10047 WSAEAFNOSUPPORT Address family not supported by protocol
family
10048 WSAEADDRINUSE Address already in use
10049 WSAEADDRNOTAVAIL Can't assign requested address
10050 WSAENETDOWN Network is down
10051 WSAENETUNREACH Network is unreachable
10052 WSAENETRESET Network dropped connection on reset
10053 WSAECONNABORTED Software caused connection abort
10054 WSAECONNRESET Connection reset by peer
10055 WSAENOBUFS No buffer space available
10056 WSAEISCONN Socket is already connected
10057 WSAENOTCONN Socket is not connected
10058 WSAESHUTDOWN Can't send after socket shutdown
10059 WSAETOOMANYREFS Too many references: can't splice
10060 WSAETIMEDOUT Connection timed out
10061 WSAECONNREFUSED Connection refused
10062 WSAELOOP Too many levels of symbolic links
10063 WSAENAMETOOLONG File name too long
10064 WSAEHOSTDOWN Host is down
10065 WSAEHOSTUNREACH No route to host
10066 WSAENOTEMPTY Directory not empty
10067 WSAEPROCLIM Too many processes
10068 WSAEUSERS Too many users
10069 WSAEDQUOT Disc quota exceeded
10070 WSAESTALE Stale NFS file handle
10071 WSAEREMOTE Too many levels of remote in path
10091 WSASYSNOTREADY System not ready
10092 WSAVERNOTSUPPORTED Version not supported
10093 WSANOTINITIALISED Winsock was not initialized
11001 WSAHOST_NOT_FOUND Host not found
11002 WSATRY_AGAIN Transient failure - Try again
11003 WSANO_RECOVERY No recovery
11004 WSANO_DATA No data
WinSock stands for Windows Sockets, it's the industry standard
networking API for all Windows platforms for TCP/IP applications. It's
implemented for 16-bit applications by a DLL named WINSOCK.DLL, and
with a DLL named WSOCK32.DLL for 32-bit applications.
With Windows NT 3.51 or latter, Windows Sockets have been upgraded to
WinSock V2. This supports other protocols through the WinSock API.
PROGRESS implements NETBIOS and SPX/IPX communications with our 32-bit
products (both server and client) using WSOCK32 for NETBIOS and SPX
with V8 and latter.
MAP (03/07/96)
Progress Software Technical Support Note # 16731