The Windows Socket (Application Programming Interface)
On occasion a user will get WSA errors starting or running the server. This is a list of some errors, codes, meanings, and possible resolves. Note that these errors in reference to WoWEmu are usually not a problem with the server itself, but with the host setup or configuration.
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.
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 Error:WSAAsyncGetXbyY that
An address incompatible with the requested protocol was used. All sockets are created with an associated "address family" Error: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,
Only one usage of each socket address Error: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.
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, or connect an address or port that is not valid for a remote machine. Routers used as HUBs or Firewalls are often to blame.
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.
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.
Some invalid argument was supplied Error: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.
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.
This is often caused by bad HOSTS entries and conflicting driver services. It can be caused by conflicting network drivers.
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. This may be caused by network data collisions. It could also be a faulty or cheap NIC.
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.
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.
The connection may be timing out due to a slow link. Increase the retransmission timeout value of the following registry key to 10 or even 20.
Worker Threads may also be set too high. Firewalls may be interfering with transmission rates. ---------------------------------------------------------------------------
WSAEPROCLIM
Error Number: 10067
Too many processes.
A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously.
WoWEMU World
Thema drucken
17.02.2007 17:51
Antworten