8.1 Secure Authentication Services Error Code List

SAS error codes include:

-1 SAS E ERROR

Source: SAS
Explanation: A general error occurred. For details, see the component error. The following are the component errors that might be returned to the application when the component error is SAS_COMPONENT_SSL.

  • -1 SSL_ERROR_NO_CIPHERS

  • -2 SSL_ERROR_NO_CERTIFICATE

  • -3 SSL_ERROR_BAD_CERTIFICATE

  • -4 SSL_ERROR_UNSUPPORTED_CERTIFICATE_TYPE

  • -5 SSL_ERROR_IO

  • -6 SSL_ERROR_BAD_MESSAGE

  • -7 SSL_ERROR_BAD_MAC

  • -8 SSL_ERROR_UNSUPPORTED

  • -9 SSL_ERROR_WOULDBLOCK

  • -10 SSL_ERROR_BAD_PEER

  • -11 SSL_ERROR_PERMISSION_DENIED

  • -12 SSL_NO_RANDOMNESS

  • -13 SSL_INTERNAL_INCONSISTENCY

  • -14 SSL_ERROR_ALREADY

  • -15 SSL_ERROR_NO_MEMORY

  • -16 SSL_ERROR_NO_SID

  • -17 SSL_KEY_TOO_OLD

  • -18 SSL_ERROR_IS_SSL3

  • -19 SSL_ERROR_IS_SSL2

  • -20 SSL_ERROR_EODATA

  • -21 SSL_ERROR_NON_EXPORT_KEY

Possible Cause: A program fault occurred in the application.
Action: If the error persists, contact the developer of the application.

-2 SAS E BAD LINKAGE

Source: SAS
Explanation: The application is not authorized to use the underlying SAS services.
Action: Contact a Novell Support Provider.

-3 SAS E ALREADY INITIALIZED

Source: SAS
Explanation: SAS_Register has already been called.
Possible Cause: A program fault occurred in the application.
Action: If the error persists, contact the developer of the application.

-4 SAS E BUSY

Source: SAS
Explanation: The SAS services are busy.
Action: Try the operation again.

-5 SAS E MEMORY

Source: SAS
Explanation: The server does not have enough memory available to run SAS.
Action: Increase the memory available to the server.

-6 SAS E INVALID MODULE

Source: SAS
Explanation: The application did not register through SAS_Register() before using any SAS APIs.
Possible Cause: A program fault occurred in the application.
Action: If the error persists, contact the developer of the application.

-7 SAS E INVALID SOCKET

Source: SAS
Explanation: The socket is not a valid socket number.
Possible Cause: The server does not have enough available sockets.
Action: Configure the server to have more sockets available.
Possible Cause: A program fault occurred in the application.
Action: If the error persists, contact the developer of the application.

-8 SAS E INVALID HANDLE

Source: SAS
Explanation: The SAS handle (SH) is not a valid handle.
Possible Cause: A program fault occurred in the application.
Action: If the error persists, contact the developer of the application.

-9 SAS E INVALID CTX HANDLE

Source: SAS
Explanation: The Crypto Context handle is not a valid cryptography context handle.
Possible Cause: A program fault occurred in the application.
Action: If the error persists, contact the developer of the application.

-10 SAS E NO MORE HANDLES

Source: SAS
Explanation: Accept failed because SAS is unable to create a new SH.
Possible Cause: The server is out of available memory.
Action: Increase the memory available to the server.

-11 SAS E KEYID ERROR

Source: SAS
Explanation: SAS could not find the Key Material object.
Possible Cause: The Key Material object was removed from the eDirectory™ or NDS® tree.
Action: If the error persists, contact the developer of the application.
Possible Cause: A program fault occurred in the application.
Action: If the error persists, contact the developer of the application.

-12 SAS E LOGINSERVICE FAIL

Source: SAS
Explanation: The SAS services could not log in to the eDirectory or NDS tree.
Action: Try loading SAS again. If the error persists, make sure the SAS object exists in eDirectory or NDS as a peer to the server object. You might need to reinstall SAS.