12 – Internal unknown error. Report problem to service.
101 – Internal unknown error. Report problem to service.
102 – I/O error reading keyfile.
103 – Keyfile has an invalid internal format. Re-create
keyfile.
104 – Keyfile has two entries with the same key. Use iKeyman
to remove the duplicate key.
105 – Keyfile has two entries with the same label. Use iKeyman
to remove the duplicate label.
106 – The keyfile password is used as an integrity check.
Either the keyfile has become corrupted or the password ID is incorrect.
107 – The default key in the keyfile has an expired certificate.
Use iKeyman to remove certificates that are expired.
108 – There was an error loading one of the GSKdynamic link
libraries. Be sure GSK was installed correctly.
109 – Indicates that a connection is trying to be made in
a gsk environment after the GSK_ENVIRONMENT_CLOSE_OPTIONS has been
set to GSK_DELAYED_ENVIRONMENT_CLOSE and gsk_environment_close() function
has been called.
201 – Neither the password nor the stash-file name was specified,
so the key file could not be initialized.
202 – Unable to open the key file. Either the path was specified
incorrectly or the file permissions did not allow the file to be opened.
203 – Unable to generate a temporary key pair. Report this
error to service.
204 – A User Name object was specified that is not found
205 – A Password used for an LDAP query is not correct
206 – An index into the Fail Over list of LDAP servers was
not correct.
301 – Indicates that the GSK environment close request was
not properly handled. Cause is most likely due to a gsk_secure_socket*()
command being attempted after a gsk_close_environment() call.
401 – The system date was set to an invalid value.
402 – Neither SSLv2 nor SSLv3 is enabled.
403 – The required certificate was not received from partner.
404 – The received certificate was formatted incorrectly.
405 – The received certificate type was not supported.
406 – An IO error occurred on a data read or write.
407 – The specified label in the key file could not be found.
408 – The specified key file password is incorrect. The
key file could not be used. The key file may also be corrupt.
409 – In a restricted cryptography environment, the key
size is too long to be supported.
410 – An incorrectly formatted SSL message was received
from the partner.
411 – The message authentication code (MAC) was not successfully
verified.
412 – Unsupported SSL protocol or unsupported certificate
type.
413 – The received certificate contained an incorrect signature.
414 – Incorrectly formatted certificate received from partner.
415 – Invalid SSL protocol received from partner.
416 – Internal error. Report problem to service.
417 – The self-signed certificate is not valid.
418 – The read failed. Report this error to service.
419 – The write failed. Report this error to service.
420 – The partner closed the socket before the protocol
completed.
421 – The specified V2 cipher is not valid.
422 – The specified V3 cipher is not valid.
423 – Internal error. Report problem to service.
424 – Internal error. Report problem to service.
425 – The handle could not be created. Report this internal
error to service.
426 – Initialization failed. Report this internal error
to service.
427 – When validating a certificate, unable to access the
specified LDAP directory.
428 – The specified key did not contain a private key.
429 – A failed attempt was made to load the specified Public-Key
Cryptography Standards (PKCS) #11 shared library.
430 – The PKCS #11 driver failed to find the token specified
by the caller.
431 – A PKCS #11 token is not present in the slot.
432 – The password/pin to access the PKCS #11 token is invalid.
433 – The SSL header received was not a properly SSLV2 formatted
header.
501 – The buffer size is negative or zero.
502 – Used with non-blocking I/O. Refer to the non-blocking
section for usage.
601 – SSLV3 is required for reset_cipher, and the connection
uses SSLV2.
602 – An invalid ID was specified for the gsk_secure_soc_misc
function call.
701 – The function call has an invalid ID. This may also
be caused by specifying an environment handle when a handle for a
SSL connection should be used.
702 – The attribute has a negative length, which is invalid.
703 – The enumeration value is invalid for the specified
enumeration type.
704 – Invalid parameter list for replacing the SID cache
routines.
705 – When setting a numeric attribute, the specified value
is invalid for the specific attribute being set.
706 – Conflicting parameters have been set for additional
certificate validation.