Common Socket Error Parameters

Common Socket Error Parameters

10053: belonging to the software leads to the end of the line (10053 Software caused connection abort) should be one of your applications in the process of running, you have illegal operation, the software use socket error. This is a relatively simple software failure, there is nothing scary, do not worry, you feel the system in operation, some of the software is not good to uninstall, the correct installation once on it. 10054 is the remote host forced to shut down an existing connection. Q. Tip "Socket Error 100xx"? A. If all sites are the same, make sure you have no problem connecting to the Internet (if you use a proxy server, make sure you set it up correctly in FlashGet, and if you use a firewall, set up the Allow FlashGet access to the Internet in your firewall software, You need to refer to the Help file for your firewall software, or you may have created too many connections, so don't download too many files at the same time. If only the individual site, it should be a temporary problem with the site or can not connect to the site (such as the domestic closure of some IP), please try again sometime. Wsaeacces (10013) Permission denied. An attempt is made to access a socket in a way forbidden through its access permissions. An example are using a broadcast address for sendto without broadcast permission being set using setsockopt (So_broadcast). Another possible reason for the wsaeacces error is this the BIND function is called (on Windows NT 4 SP4 or later), a nother 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 are implemented by using the So_exclusiveaddruse Option. Wsaeaddrinuse (10048) Address already in use. Typically, only one usage of each socket address (PROTOCOL/IP address/port) is permitted. This error occurs if is application attempts to bind a socket to a IP address/port that has already been used for a exis Ting socket, or a socket that wasn ' t closed properly, or one this is still in the process of closing. For server applications so 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 chooses a unused port automatically. When Bind was called with a wildcard address (involving Addr_any), a wsaeaddrinuse error could be delayed the until The C address is committed. This is could happen with a call to another function later, including Connect, listen, WSAConnect, or wsajoinleaf. Wsaeaddrnotavail (10049) Cannot assign requested address. The requested address isn't valid in the. This normally results from a attempt to bind to "to", "not" valid for the local machine. This can also result from Connect, sendto, WSAConnect, wsajoinleaf, or wsasendto when the remote address or port was not VA Lid for a remote machine (for example, address or port 0). Wsaeafnosupport (10047) Address family not supported by protocol family. The incompatible with the requested protocol is used. All sockets are created with a associated address family (which, af_inet for Internet protocols) and a generic protocol Invalid (is, sock_stream). This error is returned if a incorrect protocol is explicitly requested into the socket call, or if a address of the wrong Family is used for a socket, for example, in SendTo. Wsaealready (10037) Operation already in progress. An operation being attempted on a nonblocking socket and an operation already in Progress-that is, calling connect a second Time on a nonblocking socket it already connecting, or canceling a asynchronous request (WSAASYNCGETXBYY) that has Already been canceled or completed. wsaeconnaborted (10053) Software caused connection abort. An established connection is aborted by the software in your host machine, possibly due to a data transmission time-out O R protocol error. Wsaeconnrefused (10061) Connection refused. No connection could be made because the target machine actively it. This usually results from trying to connect to a service it inactive on the foreign host-that are, one with no server Application running. Wsaeconnreset (10054) Connection reset by Peer. An existing connection is forcibly closed by the remote host. This normally results if the peer application on the remote host are suddenly stopped, the host is rebooted, or the remote Host uses a hard close (the "Information on" option on the remote socket.) This error may also result if a connection is broken due to keep-alive activity detecting a failure while one or more ope Rations are in progress. Operations that were in progress fail with Wsaenetreset. Subsequent operations fail with Wsaeconnreset. Wsaedestaddrreq (10039) Destination address required. A required address is omitted from the operation on a socket. For example, this error was returned if SendTo is called with the remote address of addr_any. Wsaefault (10014) Bad address. The system detected an invalid pointer address at attempting to use a pointer argument of a call. This error occurs if a application passes an invalid pointer value, or if the length of the ' is ' too small. For instance, if the length of argument, which are a SOCKADDR structure, is smaller than the sizeof (SOCKADDR). Wsaehostdown (10064) Host is down. A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking The local host has not been initiated. These conditions are are more likely to being indicated by the error wsaetimedout. Wsaehostunreach (10065) No route to host. A socket operation is attempted to A unreachable host. Wsaenetunreach. Wsaeinprogress (10036) Operation now in progress. A blocking operation is currently executes uting. Windows Sockets only allows a single blocking operation-per-task or thread-to is outstanding, and if any other function C The function fails with the wsaeinprogress error of all is made (whether or not it references, or any other socket). Wsaeintr (10004) Interrupted function call. A blocking operation is interrupted by a call to WSACancelBlockingCall. Wsaeinval (10022) Invalid argument. Some Invalid argument is supplied (for example, specifying a invalid level to the SetSockOpt function). In some instances, it also refers to the "current" of the Socket-for instance, calling accept on a socket this is not Listening. Wsaeisconn (10056) The Socket is already connected. A connect request is made on A already-connected socket. Some implementations also return this error if sendto are called on a connected Sock_dgram sockets (for SOCK_STREAM sockets, The to parameter in SendTo are 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 sockets handles available, either globally, per process, or/per thread. Wsaemsgsize (10040) Message too long. A message sent on a datagram socket is larger than the internal message buffer or some other network limit, or the buffer Used to receive a datagram is 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 (which is, the protocol stack, the Windows Sockets 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 is in progress. It can also be returned by setsockopt if a attempt was made to set so_keepalive on a connection that has already. Wsaenetunreach (10051) Network is unreachable. A socket operation is attempted to A unreachable network. This usually means the software knows no route to reach the remote host. Wsaenobufs (10055) No buffer space available. An operation on a socket could is performed because the system lacked sufficient buffer space or because a queue is F Ull. Wsaenoprotoopt (10042) Bad protocol option. An unknown, invalid or unsupported option or level is specified in a getsockopt or setsockopt call. Wsaenotconn (10057) The Socket is not connected. A request to send or receive data was disallowed because the "Not connected and" (when sending on a datagram Socke T using SendTo) No address is supplied. No other invalid of operation might also return to this error-for example, setsockopt setting if the So_keepalive connection been reset. Wsaenotsock (10038) Socket operation on Nonsocket. An operation being attempted on something this is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of a fd_set is not valid. Wsaeopnotsupp (10045) Operation not supported. The attempted operation isn't supported for the invalid of object referenced. Usually this occurs when a socket de script or to a socket that cannot support this operation be trying to accept a connection O n A datagram socket. Wsaepfnosupport (10046) Protocol family not supported. The protocol family has not been configured to the system or no implementation for it exists. This message is has a slightly different meaning from Wsaeafnosupport. However, it is interchangeable in most cases, and all Windows Sockets functions, this return one of these messages also SPE Cify Wsaeafnosupport. Wsaeproclim (10067) Too many processes. A Windows Sockets implementation may have a limit on the number of applications ' can 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 to the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol. Invalid Wsaeproto (10041) Protocol wrong is not valid for socket. A protocol is specified in the socket function call this does not support the semantics of the socket is invalid requested. For example, the ARPA Internet UDP protocol cannot is specified with a socket invalid of sock_stream. Wsaeshutdown (10058) Cannot send after socket shutdown. A request to send or receive data is disallowed because the socket had already been shut down in which direction with a PR evious shutdown call. By calling shutdown a partial close to a socket is requested, which are a signal that sending or receiving, or both have En discontinued. Wsaesocktnosupport (10044) Invalid Socket not supported. The support for the specified socket is not valid does not exist to this address family. For example, the optional is invalid Sock_raw might is selected in a socket call, and the implementation does not support Sockets at all. Wsaetimedout (10060) Connection timed out. A connection attempt failed because the connected party did no properly after a respond of of time, or the period D Connection failed because the connected host has failed to respond. WSA Invalid _not_found (10109) Class is not valid not found. The specified class is not found. Wsaewouldblock (10035) Resource temporarily unavailable. This was returned from operations to nonblocking sockets that cannot to completed immediately, for example when No data is queued to being read from the socket. It is a nonfatal error, and the operation should are retried later. It is normal for wsaewouldblock to being reported as the result of calling connect on a nonblocking sock_stream socket, sin Ce 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 a official host name or alias, or it cannot be found in the database (s) being queried. This error may also is returned for protocol and service queries, and means the specified name could The relevant database. Wsa_invalid_handle (OS dependent) Specified Event object handle is invalid. An application attempts to use a event object, but the specified handle is not valid. Wsa_invalid_parameter (OS dependent) One or more parameters are invalid. A 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 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. Wsa_io_incomplete (OS dependent) Overlapped I/O event object not in signaled state. The application has tried to determine the status of a 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 a ove Rlapped operation has completed, get this error code until the operation is complete. Wsa_io_pending (OS dependent) Overlapped operations would complete later. The application has initiated a overlapped operation that cannot is completed. A completion indication would be given later the operation has. Wsa_not_enough_memory (OS dependent) Insufficient memory available. A application used a Windows Sockets function that is directly maps to a WIN32 function. The WIN32 function is indicating a lack of required memory. Wsanotinitialised (10093) Successful WSAStartup not yet performed. Either the application hasn ' t called WSAStartup or WSAStartup failed. The application may be accessing a socket so the current active task does not own (which, trying to share a socket bet Ween tasks), or wsacleanup has been called too times. Wsano_data (11004) Valid name, no data record of requested is invalid. The requested name is valid and be 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) wh Ich uses the DNS (Domain Name Server). An MX record isn't returned but no A record-indicating the host itself exists, but is not directly reachable. Wsano_recovery (11003) This is a nonrecoverable error. This indicates some sort of nonrecoverable error occurred during a database lookup. This May is because the database files (for example, Bsd-compatible HOSTS, SERVICES, or protocols files) could is not being foun D, or a DNS request is 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 the pro Tocol/name space catalogs. Wsasysnotready (10091) Network subsystem is unavailable. This error was returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the Underl Ying System it uses to provide network services are currently unavailable. Users should check: That's the appropriate Windows Sockets DLL file is on the current path. That is they are not trying to use the more than one Windows Sockets implementation. If there is more than one Winsock DLL on your system, be sure the the ' one in ' path is appropriate for the network sub System currently loaded. The Windows Sockets implementation documentation ation to is sure all necessary components are currently installed and configured Corr ectly. Wsatry_again (11002) Nonauthoritative host not found. This is usually a temporary error during host name resolution and means so the local server did not receive a response F Rom an authoritative server. A retry at some time later could be successful. wsavernotsupported (10092) Winsock.dll version out of range. The current Windows Sockets implementation does is not support the Windows Sockets Specification version requested by the app Lication. Check this no old Windows Sockets DLL files are being accessed. Wsaediscon (10101) Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate, the remote party has initiated a graceful shutdown. wsa_operation_aborted (OS dependent) Overlapped operation aborted. An overlapped operation is canceled due to the closure of the socket, or the execute ution of the Sio_flush command in WSAIoctl .