SAL error codes include the following:
-5857 FFFFE91F SERR SKTEREMOTE
Source:
SAL, Socket
Explanation:
The item is not available locally.
-5858 FFFFE91E SERR SKTESTALE
Source:
SAL, Socket
Explanation:
The socket handle reference is no longer available.
-5859 FFFFE91D SERR SKTEDQUOT
Source:
SAL, Socket
Explanation:
SAL ran out of disk space quota.
-5860 FFFFE91C SERR SKTEUSERS
Source:
SAL, Socket
Explanation:
SAL ran out of quota.
-5861 FFFFE91B SERR SKTEPROCLIM
Source:
SAL, Socket
Explanation:
Too many processes are being used.
Possible Cause:
A SAL Sockets implementation might have a limit on the number of applications that can use it simultaneously. SAL_Startup may fail with this error if this limit exists on a platform and the limit has been reached.
-5862 FFFFE91A SERR SKTENOTEMPTY
Source:
SAL, Socket
Explanation:
A directory that is not empty cannot be removed.
-5863 FFFFE919 SERR SKTEHOSTUNREACH
Source:
SAL, Socket
Explanation:
A socket operation was attempted to an unreachable host.
-5864 FFFFE918 SERR SKTEHOSTDOWN
Source:
SAL, Socket
Explanation:
A socket operation failed because the destination host is down.
Possible Cause:
A socket operation encountered a dead host, or networking activity on the local host has not been initiated. These conditions are more likely to be indicated by sal_sktetimedout error.
-5865 FFFFE917 SERR SKTENAMETOOLONG
Source:
SAL, Socket
Explanation:
The filename is too long.
-5866 FFFFE916 SERR SKTELOOP
Source:
SAL, Socket
Explanation:
There are too many levels of symbolic links.
-5867 FFFFE915 SERR SKTECONNREFUSED
Source:
SAL, Socket
Explanation:
The connection was refused by the target machine.
Possible Cause:
No connection could be made because the target machine refused it. This usually results from trying to connect to a service that is inactive on the foreign host; that is, one with no server application running.
-5868 FFFFE914 SERR SKTETIMEDOUT
Source:
SAL, Socket
Explanation:
The connection timed out.
Possible Cause:
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.
-5869 FFFFE913 SERR SKTETOOMANYREFS
Source:
SAL, Socket
Explanation:
There are too many socket references.
-5870 FFFFE912 SERR SKTESHUTDOWN
Source:
SAL, Socket
Explanation:
Data could not be sent after socket shutdown.
Possible Cause:
A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous SAL_SktShutdown call. By calling SAL_SktShutdown, a partial close of a socket is requested, which is a signal that sending and receiving have been discontinued.
-5871 FFFFE911 SERR SKTENOTCONN
Source:
SAL, Socket
Explanation:
Socket is not connected.
Possible Cause:
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using SAL_SktSend) no address was supplied. Any other type of operation might also return this error, for example, SAL_SktSetOption setting SAL_So_Keepalive if the connection has been reset.
-5872 FFFFE910 SERR SKTEISCONN
Source:
SAL, Socket
Explanation:
Socket is already connected.
Possible Cause:
A connect request was made on an already-connected socket. Some implementations also return this error if SAL_SktSend is called on a connected SAL_Sock_Dgram socket (for SAL_Sock_Stream sockets, the to parameter in SAL_SktSend is ignored) although other implementations treat this as a legal occurrence.
-5873 FFFFE90F SERR SKTENOBUFS
Source:
SAL, Socket
Explanation:
No buffer space available.
Possible Cause:
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
-5874 FFFFE90E SERR SKTECONNRESET
Source:
SAL, Socket
Explanation:
Connection reset by peer.
Possible Cause:
An existing connection was forcibly closed by the remote host. This normally happens if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host uses a hard close. This error can also occur 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 SAL_Sktenetreset. Subsequent operations fail with SAL_Skteconnreset.
-5875 FFFFE90D SERR SKTECONNABORTED
Source:
SAL, Socket
Explanation:
Software caused the connection to abort.
Possible Cause:
An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error.
-5876 FFFFE90C SERR SKTENETRESET
Source:
SAL, Socket
Explanation:
Network dropped connection on reset.
Possible Cause:
The connection was broken because of a keep-alive activity detected a failure while the operation was in progress. This error can also be returned by SAL_SktSetOption if an attempt is made to set SAL_So_Keepalive on a connection that has already failed.
-5877 FFFFE90B SERR SKTENETUNREACH
Source:
SAL, Socket
Explanation:
Network is unreachable.
Possible Cause:
A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.
-5878 FFFFE90A SERR SKTENETDOWN
Source:
SAL, Socket
Explanation:
Network is down.
Possible Cause:
A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack in use by SAL Sockets), the network interface, or the local network itself.
-5879 FFFFE909 SERR SKTEADDRNOTAVAIL
Source:
SAL, Socket
Explanation:
Cannot assign requested address.
Possible Cause:
The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from SAL_SktConnect or SAL_SktSend when the remote address or port is not valid for a remote machine (for example, address or port 0).
-5880 FFFFE908 SERR SKTEADDRINUSE
Source:
SAL, Socket
Explanation:
Socket address already in use.
Possible Cause:
Typically, only one usage of each socket address (protocol/IP address/port) is 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, consider using SAL_SktSetOption(SAL_So_Reuseaddr). Client applications usually need not call SAL_SktBind at all. SAL_SktConnect chooses an unused port automatically. When SAL_SktBind is called with a wildcard address (involving SAL_Addr_Any), SAL_Skteaddrinuse could be delayed until the specific address is committed. This could happen with a call to another function later, including SAL_SktConnect or SAL_SktListen.
-5881 FFFFE907 SERR SKTEAFNOSUPPORT
Source:
SAL, Socket
Explanation:
Address family not supported by protocol family.
Possible Cause:
An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, SAL_Af_Inet for Internet protocols) and a generic protocol type (that is, SAL_Sock_Stream). This error is 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 (for example, in SAL_SktSend).
-5882 FFFFE906 SERR SKTEPFNOSUPPORT
Source:
SAL, Socket
Explanation:
Protocol family not supported.
Possible Cause:
The protocol family has not been configured into the system, or no implementation for it exists. This message has a slightly different meaning from SAL_Skteafnosupport. However, it is interchangeable in most cases, and all SAL Sockets functions that return one of these messages also specify SAL_Skteafnosupport.
-5883 FFFFE905 SERR SKTEOPNOTSUPP
Source:
SAL, Socket
Explanation:
Socket operation not supported for object type.
Possible Cause:
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 is trying to accept a connection on a datagram socket.
-5884 FFFFE904 SERR SKTESOCKTNOSUPPORT
Source:
SAL, Socket
Explanation:
Support for the specified socket type does not exist in this address family. For example, the optional type SAL_Sock_Raw might be selected in a socket call, and the implementation does not support SAL_Sock_Raw sockets at all.
-5885 FFFFE903 SERR SKTEPROTONOSUPPORT
Source:
SAL, Socket
Explanation:
The protocol type is not supported for the socket.
Possible Cause:
The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SAL_Sock_Dgram socket, but specifies a stream protocol.
-5886 FFFFE902 SERR SKTENOPROTOOPT
Source:
SAL, Socket
Explanation:
The protocol option is bad.
Possible Cause:
An unknown, invalid, or unsupported option or level was specified in a SAL_SktGetOption
or SAL_SktSetOption call.
-5887 FFFFE901 SERR SKTEPROTOTYPE
Source:
SAL, Socket
Explanation:
The protocol type is wrong for the socket.
Possible Cause:
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 SAL_Sock_Stream.
-5888 FFFFE900 SERR SKTEMSGSIZE
Source:
SAL, Socket
Explanation:
The message is too long.
Possible Cause:
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 was smaller than the datagram itself.
-5889 FFFFE8FF SERR SKTEDESTADDRREQ
Source:
SAL, Socket
Explanation:
A required address was omitted from an operation on a socket. For example, this error is returned if SAL_SktSend is called with the remote address of SAL_Addr_Any.
-5890 FFFFE8FE SERR SKTENOTSOCK
Source:
SAL, Socket
Explanation:
An socket operation was attempted on something that is not a socket.
Possible Cause:
Either the socket handle parameter did not reference a valid socket, or for SAL_SktSelect, a member of a SAL_Fdset was not valid.
-5891 FFFFE8FD SERR SKTEALREADY
Source:
SAL, Socket
Explanation:
A non-blocking operation is already in progress.
Possible Cause:
An operation was attempted on a non-blocking socket with an operation already in progress (that is, calling SAL_SktConnect a second time on a non-blocking socket that is already connecting).
-5892 FFFFE8FC SERR SKTEINPROGRESS
Source:
SAL, Socket
Explanation:
A blocking operation is currently executing.
Possible Cause:
SAL Sockets only allows a single blocking operation per task or thread to be outstanding. If any other function call is made (whether or not it references that or any other socket), the function fails with the SAL_Skteinprogress error.
-5893 FFFFE8FB SERR SKTEWOULDBLOCK
Source:
SAL, Socket
Explanation:
The requested resource is temporarily unavailable.
Possible Cause:
This error is returned from operations on non-blocking sockets that cannot be completed immediately, for example SAL_SktReceive when no data is queued to be read from the socket. It is not a fatal error, and the operation should be retried later. It is normal for SAL_Sktewouldblock to be reported as the result from calling connect on a non-blocking SAL_Sock_Stream socket, because some time must elapse for the connection to be established.
-5894 FFFFE8FA SERR SKTEMFILE
Source:
SAL, Socket
Explanation:
There are too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.
-5895 FFFFE8F9 SERR SKTEINVAL
Source:
SAL, Socket
Explanation:
An invalid argument is in a socket operation.
Possible Cause:
An invalid argument was supplied (for example, specifying an invalid level to SAL_SktSetOption). In some instances, this error also refers to the current state of the socket (for example, calling SAL_SktAccept on a socket that is not listening).
-5896 FFFFE8F8 SERR SKTEFAULT
Source:
SAL, Socket
Explanation:
Bad address detected in socket operation.
Possible Cause:
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 example, if the length of an argument, which is a SAL_Sockaddr structure, is smaller than the size of (SAL_Sockaddr).
-5897 FFFFE8F7 SERR SKTEACCES
Source:
SAL, Socket
Explanation:
An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for SAL_SktSend without broadcast permission being set using SAL_SktSetOption(SAL_So_Broadcast).
-5898 FFFFE8F6 SERR SKTEBADF
Source:
SAL, Socket
Explanation:
The socket handle supplied is not valid.
-5899 FFFFE8F5 SERR SKTEINTR
Source:
SAL, Socket
Explanation:
This error indicates an interrupted function call. A blocking operation was interrupted.
-5976 FFFFE8A8 SERR OBJECT BUSY
Source:
SAL, Base
Explanation:
A call was made to an API that could block, but “no block” was specified. In this case, the API returns Object_Busy to indicate that the request could not be completed without blocking.
-5977 FFFFE8A7 SERR CALLBACK CANCELLED
Source:
SAL, Base
Explanation:
This error is not currently returned by any SAL routines. It is present as a tool to allow upper-layer callback routines a way of indicating that they cancelled an enumeration process.
-5978 FFFFE8A6 SERR UNICODE TRANSLATION
Source:
SAL, Base
Explanation:
A unicode translation operation failed.
Possible Cause:
There was no mappable character, and success was specified as a translation requirement.
-5979 FFFFE8A5 SERR INVALID RESPONSE
Source:
SAL, Base
Explanation:
A response was received from a client callback routine or over the wire from a client, and its contents were not expected.
-5980 FFFFE8A4 SERR INVALID REQUEST
Source:
SAL, Base
Explanation:
A routine was called to perform an operation that cannot be completed given the specified parameters. For example, a call was made to a buffer routine to extract a 4 byte quantity from a 3 byte buffer.
-5981 FFFFE8A3 SERR NOT IMPLEMENTED
Source:
SAL, Base
Explanation:
A call was made to a routine that has not been implemented.
-5982 FFFFE8A2 SERR SYSTEM FAILURE
Source:
SAL, Base
Explanation:
A catastrophic system failure occurred.
-5983 FFFFE8A1 SERR NO SUCH ENTRY POINT
Source:
SAL, Base
Explanation:
An attempt was made to import an entry point symbol from an executable module, but the entry point could not be found.
-5984 FFFFE8A0 SERR MODULE NOT FOUND
Source:
SAL, Base
Explanation:
An attempt was made to load an executable module but the module could not be located.
-5985 FFFFE89F SERR TOO MANY POSTS
Source:
SAL, Base
Explanation:
Too many signals were sent to a SAL semaphore.
-5986 FFFFE89E SERR THREAD STILL ACTIVE
Source:
SAL, Base
Explanation:
This error is returned by SAL_ThreadGetExitCode when the requested thread is still active.
-5987 FFFFE89D SERR NAME T00 LONG
Source:
SAL, Base
Explanation:
A string parameters was too long for the API to use it without truncating.
Possible Cause:
Many of the path routines return this error rather than truncate the parameter value.
-5988 FFFFE89C SERR INVALID MODULE
Source:
SAL, Base
Explanation:
A request was made to read information from a module by name and the module was not of a type that is recognized by the SAL implementation.
Possible Cause:
This value can be returned for many different reasons, all of which are related to executable modules. Each platform defines a recognizable module in a different manner.
-5989 FFFFE89B SERR SYSTEM NOT INITIALIZED
Source:
SAL, Base
Explanation:
SAL_Startup was not called before an SAL API call.
Possible Cause:
This error is only returned if SAL_Startup was not called before any SAL API call was attempted.
Action:
Call SAL_Startup before you call any SAL API.
-5990 FFFFE89A SERR TOO MANY HANDLES
Source:
SAL, Base
Explanation:
There is a maximum limit on the number of handles that can be allocated from the SAL handle table. There are also presumably limits on the underlying OS handle table. This error can be returned for either reason.
-5991 FFFFE899 SERR NO ACCESS
Source:
SAL, Base
Explanation:
Access is denied.
Possible Cause:
You don’t have rights to perform the requested operation.
-5992 FFFFE898 SERR ALREADY EXISTS
Source:
SAL, Base
Explanation:
The requested object already exists.
Possible Cause:
This value may be returned for successful calls if you did not explicitly specify failure on pre-existence. In the case of OS sync object, for instance, the error simply indicates that the object was attached.
-5993 FFFFE897 SERR OBJECT NOT FOUND
Source:
SAL, Base
Explanation:
The requested object, file, or global sync object could not be located.
-5994 FFFFE896 SERR WAIT TIMEOUT
Source:
SAL, Base
Explanation:
A synchronization primitive timed out and returned before acquiring the requested lock. This error can only be returned in calls that take a timeout value (and then only when a real timeout value is specified), or in calls whose names imply that they could not return without success because they would have to block to succeed. For example, SAL_RWLock**Try**Acquire.
-5995 FFFFE895 SERR END OF STREAM
Source:
SAL, Base
Explanation:
There is no more data to be read on the specified data stream. This could mean file data or directory data, or another form of data that is read in iterative passes.
-5996 FFFFE894 SERR INVALID HANDLE
Source:
SAL, Base
Explanation:
A bad handle was passed to a SAL library routine.
-5997 FFFFE893 SERR INVALID PARAMETER
Source:
SAL, Base
Explanation:
This is a programmer error. The library user passed an invalid value as a parameter to a library exported routine.
-5998 FFFFE892 SERR INSUFFICIENT BUFFER
Source:
SAL, Base
Explanation:
The buffer parameter was too small to return the result.
-5999 FFFFE891 SERR INSUFFICIENT MEMORY
Source:
SAL, Base
Explanation:
This error indicates a memory allocation failure.