A list of Windows error codes, Windows internal labels, and their causes follows:
This error is returned if a sockets function is interrupted while it is in progress.
This error is returned if a sockets function is called with a bad file number or descriptor.
Permission denied.
This error is returned if a sockets function is called with a bad address.
This error is returned if a sockets function is called with an invalid argument.
Too many files open.
Resource temporarily unavailable.
This error is returned if a sockets function is called while a blocking function is in progress.
This error is returned if a sockets function is called while a function is already in progress.
This error is returned is a sockets function is performed on a non-socket.
Destination address required.
Message too long.
Protocol type wrong for socket.
Protocol not available.
Protocol not supported.
Socket type not supported.
Operation not supported on socket.
Protocol family not supported.
Address family not supported.
Address already in use.
Cannot assign requested address.
This error may be reported at any time if the sockets implementation detects an underlying failure. Generally used to mean that the network is down.
Network is unreachable.
Network dropped connection due to reset.
Software caused connection abort.
Connection reset by peer.
No buffer space available.
Socket is already connected.
Socket is not connected.
Cannot send after socket shutdown.
Too many references: cannot splice
Connection timed out.
Connection refused.
Symbolic link loop.
Path name is too long.
The host is down.
No route to host.
Unable to initialize the network subsystem. This may indicate a configuration error in the network subsystem.
Unable to initialize the network subsystem. This may indicate a configuration error in the network subsystem.
Unable to use the network subsystem because it has not been successfully initialized.
|
Copyright © 2013 CA.
All rights reserved.
|
|