Handshake messages

 

+

Search Tips   |   Advanced Search

 

This topic contains error messages that might result due to SSL handshake failures and provides solutions to help we troubleshoot these problems.

The following messages display due to handshake failures:

• Message: SSL0117E: Initialization error, Internal unknown error. Report problem to service.

  • Reason: Initialization error, Internal unknown error. Report problem to service.

  • Solution: Initialization error, Internal unknown error. Report problem to service.

• Message: SSL0118E: Initialization error, Open failed due to cipher error.

  • Reason: Report problem to service.

  • Solution: Report problem to service.

• Message: SSL0119E: Initialization error, I/O error reading keyfile.

  • Reason: I/O error trying to read SSL keyfile.

  • Solution: Check the file permissions for keyfile.

• Message: SSL0120E: Initialization error, Keyfile has and invalid internal format. Recreate keyfile.

  • Reason: Initialization error, the keyfile has an invalid internal format. Recreate the keyfile.

  • Solution: Verify the keyfile is not corrupted.

• Message: SSL0121E: Initialization error, Keyfile has two entries with the same key. Use Ikeyman to remove the duplicate key.

  • Reason: The keyfile has two entries with the same key. Use Ikeyman to remove the duplicate key.

  • Solution: Use Ikeyman to remove the duplicate key.

• Message: SSL0122E: Initialization error, Keyfile has two entries with the same label. Use Ikeyman to remove the duplicate label.

  • Reason: The keyfile has two entries with the same label. Use Ikeyman to remove the duplicate label.

  • Solution: Use Ikeyman to remove the duplicate label.

• Message: SSL0123E: Initialization error, The keyfile password is used as an integrity check. Either the keyfile has become corrupted or the password is incorrect.

  • Reason: The keyfile password is used as an integrity check. Either the keyfile has become corrupted or the password is incorrect.

  • Solution: Use Ikeyman to verify that the keyfile is valid, check permissions on the stash file, verify passwords.

• Message: SSL0124E: Initialization error, The default key in the keyfile has an expired certificate. Use Ikeyman to remove certificates that are expired.

  • Reason: The default key in the keyfile has an expired certificate. Use Ikeyman to remove certificates that are expired.

  • Solution: Use Ikeyman to remove or update expired certificates, verify the system time is accurate.

• Message: SSL0125E: Initialization error, There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly.

  • Reason: There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly.

  • Solution: Verify GSK is installed and appropriate level for release of IBM HTTP Server.

• Message: SSL0126S: Initialization error, Invalid date.

  • Reason: Initialization error, invalid date.

• Message: SSL0127S: Initialization error, No ciphers specified.

  • Reason: Initialization error, no ciphers specified.

  • Solution: Report problem to service.

• Message: SSL0128S: Initialization error, No certificate.

  • Reason: Initialization error, no certificate.

  • Solution: Report problem to service.

• Message: SSL0129S: Initialization error, The received certificate was formatted incorrectly.

  • Reason: The received certificate is formatted incorrectly.

  • Solution: Use Ikeyman to validate certificates used for connection.

• Message: SSL0130E: Initialization error, Unsupported certificate type.

  • Reason: Unsupported certificate type.

  • Solution: Check certificates that are used for this connection in Ikeyman.

• Message: SSL0131I: Initialization error, I/O error during handshake.

  • Reason: I/O error during handshake.

  • Solution: Check network connectivity.

• Message: SSL0132E: Initialization error, Invalid key length for export.

  • Reason: Invalid key length for export.

  • Solution: Report problem to service.

• Message: SSL0133W: Initialization error, An incorrectly formatted SSL message was received.

  • Reason: An incorrectly formatted SSL message was received.

  • Solution: Check client settings.

• Message: SSL0134W: Initialization error, Could not verify MAC.

  • Reason: Could not verify MAC.

  • Solution: Report problem to service.

• Message: SSL0135W: Initialization error, Unsupported SSL protocol or unsupported certificate type.

  • Reason: Unsupported SSL protocol or unsupported certificate type.

  • Solution: Check server ciphers and certificate settings.

• Message: SSL0136W: Initialization error, Invalid certificate signature.

  • Reason: Invalid certificate signature.

  • Solution: Check certificate in Ikeyman.

• Message: SSL0137W: Initialization error, Invalid certificate sent by partner.

  • Reason: Invalid certificate sent by partner.

  • Solution: If this occurs during an SSL Proxy connection, the remote SSL server sent a bad certificate to IBM HTTP Server. Check the certificate and certificate authority chain at the other end of the SSL connection.

• Message: SSL0138W: Initialization error, Invalid peer.

  • Reason: Invalid peer.

  • Solution: Report problem to service.

• Message: SSL0139W: Initialization error, Permission denied.

  • Reason: Permission denied.

  • Solution: Report problem to service.

• Message: SSL0140W: Initialization error, The self-signed certificate is not valid.

  • Reason: The self-signed certificate is not valid.

  • Solution: Check the certificate in Ikeyman.

• Message: SSL0141E: Initialization error, Internal error - read failed.

  • Reason: Internal error - read failed.

  • Solution: Report to service.

• Message: SSL0142E: Initialization error, Internal error - write failed.

  • Reason: Internal error - write failed.

  • Solution: Report to service.

• Message: SSL0143I: Initialization error, Socket has been closed.

  • Reason: Socket has been closed unexpectedly.

  • Solution: Check the client and network. Report problem to service.

• Message: SSL0144E: Initialization error, Invalid SSLV2 Cipher Spec.

  • Reason: Invalid SSLV2 cipher spec.

  • Solution: Check the SSLCipherSpec directive.

• Message: SSL0145E: Initialization error, Invalid SSLV3 Cipher Spec.

  • Reason: Invalid SSLV3 Cipher Spec.

  • Solution: Check the SSLCipherSpec directive.

• Message: SSL0146E: Initialization error, Invalid security type.

  • Reason: Invalid security type.

  • Solution: Report to service.

• Message: SSL0147E: Initialization error, Invalid security type combination.

  • Reason: Invalid security type combination.

  • Solution: Report to service.

• Message: SSL0148E: Initialization error, Internal error - SSL Handle creation failure.

  • Reason: Internal error - SSL handle creation failure.

  • Solution: Report to service.

• Message: SSL0149E: Initialization error, Internal error - GSK initialization has failed.

  • Reason: Internal error - GSK initialization has failed.

  • Solution: Report to service.

• Message: SSL0150E: Initialization error, LDAP server not available.

  • Reason: LDAP server not available.

  • Solution: Check CRL directives.

• Message: SSL0151E: Initialization error, The specified key did not contain a private key.

  • Reason: The specified key did not contain a private key.

  • Solution: Check the certificate in use in Ikeyman.

• Message: SSL0152E: Initialization error, A failed attempt was made to load the specified PKCS#11 shared library.

  • Reason: A failed attempt was made to load the specified PKCS#11 shared library.

  • Solution: Check SSLPKCSDriver directive and file system.

• Message: SSL0153E: Initialization error, The PKCS#11 driver failed to find the token specified by the caller.

  • Reason: The PKCS#11 driver failed to find the token specified by the caller.

• Message: SSL0154E: Initialization error, A PKCS#11 token is not present for the slot.

  • Reason: A PKCS#11 token is not present for the slot.

  • Solution: Verify PKCS#11 directives.

• Message: SSL0155E: Initialization error, The password/pin to access the PKCS#11 token is invalid.

  • Reason: The password and pin to access the PKCS#11 token is invalid.

• Message: SSL0156E: Initialization error, The SSL header received was not a properly SSLV2 formatted header.

  • Reason: The SSL header received was not a properly SSLV2 formatted header.

• Message: SSL0157E: Initialization error, The function call, %s, has an invalid ID.

  • Reason: The function call, %s, has an invalid ID.

  • Solution: Report problem to service.

• Message: SSL0158E: Initialization error, Internal error - The attribute has a negative length: %s.

  • Reason: Internal error - The attribute has a negative length.

  • Solution: Report problem to service.

• Message: SSL0159E: Initialization error, The enumeration value is invalid for the specified enumeration type: %s.

  • Reason: The enumeration value is invalid for the specified enumeration type: %s.

  • Solution: Report problem to service.

• Message: SSL0160E: Initialization error, The SID cache is invalid: %s.

  • Reason: The SID cache is invalid.

  • Solution: Report problem to service.

• Message: SSL0161E: Initialization error, The attribute has an invalid numeric value: %s.

  • Reason: The attribute has an invalid numeric value: %s.

  • Solution: Check SSL directives.

• Message: SSL0162W: Setting the LD_LIBRARY_PATH or LIBPATH for GSK failed.

  • Reason: Could not update the environment for GSK libraries.

  • Solution: Report problem to service.

• Message: SSL0163W: Setting the LIBPATH for GSK failed, could not append /usr/opt/ibm/gskkm/lib.

  • Reason: Could not append to LD_LIBRARY_PATH or LIBPATH for GSK failed.

  • Solution: Report problem to service.

• Message: SSL0164W: Error accessing Registry, RegOpenKeyEx/RegQueryValueEx returned [%d].

  • Reason: Error accessing registry.

  • Solution: Check GSK installation and windows registry.

• Message: SSL0165W: Storage allocation failed.

  • Reason: Storage allocation failed.

  • Solution: Check memory usage, report problem to service.

• Message: SSL0166E: Failure attempting to load GSK library.

  • Reason: Failure while attempting to load GSK library.

  • Solution: Check the GSK installation.

• Message: SSL0167E: GSK function address undefined.

  • Reason: GSK function address is undefined.

  • Solution: Check the GSK installation and level.

• Message: SSL0168E: SSL initialization for server: %s, port: %u failed due to a configuration error.

  • Reason: Iinitialization for server: %s, port: %u failed due to a configuration error.

  • Solution: Check the SSL configuration.

• Message: SSL0169E: Keyfile does not exist: %s.

  • Reason: Keyfile does not exist.

  • Solution: Check to ensure the path that is provided to the KeyFile directive exists, and is readable by the user that IBM HTTP Server is running as.

• Message: SSL0170E: GSK could not initialize, no keyfile specified.

  • Reason: Keyfile is not specified.

  • Solution: Specify Keyfile directive.

• Message: SSL0171E: CRL cannot be specified as an option for the SSLClientAuth directive on HPUX because the IBM HTTP Server does not support CRL on HPUX.

  • Reason: CRL cannot be specified as an option for the SSLClientAuth directive on HPUX because IBM HTTP Server does not support CRL on HPUX.

  • Solution: Remove CRL directives.

• Message: SSL0172E: If CRL is turned on, we must specify an LDAP hostname for the SSLCRLHostname directive.

  • Reason: If CRL is turned on, we must specify an LDAP hostname for the
    SSLCRLHostname directive.

  • Solution: Specify SSLCRLHostname.

• Message: SSL0173E: Failure obtaining supported cipher specs from the GSK library.

  • Reason: Failure obtaining supported cipher specs from the GSK library.

  • Solution: Check the GSK installation, report problem to service.

• Message: SSL0174I: No CRL password found in the stash file: %s.

  • Reason: No CRL password is found in the stash file: %s.

  • Solution: Check the stash file permissions, regenerate stash file.

• Message: SSL0174I: No CRYPTO password found in the stash file: %s.

  • Reason: No CRYPTO password is found in the stash file: %s.

  • Solution: Check stash file permissions, regenerate stash file.

• Message: SSL0175E: fopen failed for stash file: %s.

  • Reason: fopen failed for stash file.

  • Solution: Check stash file permissions, regenerate stash file.

• Message: SSL0176E: fread failed for the stash file: %s.

  • Reason: fread failed for the stash file.

  • Solution: Make sure the stash file is readable by user IBM HTTP Server is running as.

• Message: SSL0179E: Unknown return code from stash_recover(), %d.

  • Reason: Unknown return code from stash_recover(), %d.

  • Solution: Check the stash file.

• Message: SSL0181S: Unable to fork for startup of session ID cache.

  • Reason: Unable to fork for startup of session ID cache.

  • Solution: Check the location of sidd daemon, file permissions.

• Message: SSL0182E: Error creating file mapped memory for SSL passwords.

  • Reason: Error creating file mapped memory for SSL passwords.

  • Solution: Report problem to service.

• Message: SSL0183E: Exceeded map memory limits.

  • Reason: Exceeded map memory limits.

  • Solution: Report problem to service.

• Message: SSL0184E: Could not find a password for the resource: %s.

  • Reason: SSL0184E: Could not find a password for the resource: %s.

  • Solution: Report problem to service, disable password prompting.

• Message: SSL0185E: ssl_getpwd() failed, unable to obtain memory.

  • Reason: ssl_getpwd() failed, unable to obtain memory.

  • Solution: Report problem to service, disable password prompting.

• Message: SSL0186E: Linked list mismatch.

  • Reason: SSL0186E: Linked list mismatch.

  • Solution: Report problem to service, disable password prompting.

• Message: SSL0186E: ssl_getpwd() failed, password exceeded maximum size of 4095.

  • Reason: ssl_getpwd() failed, password exceeded the maximum size of 4095.

  • Solution: The password must be smaller than 4K.

• Message: SSL0187E: It is invalid to enable password prompting for the SSLServerCert directive without specifying a Crypto Card Token.

  • Reason: It is invalid to enable password prompting for the SSLServerCert directive without specifying a crypto card token.

  • Solution: Specify a crypto card token or disable password prompting for the SSLServerCert directive.

• Message: SSL0200E: Handshake Failed, <code>.

  • Reason: The handshake failed when the SSL library returned an unknown error.

  • Solution: None. Report this problem to Service.

• Message: SSL0201E: Handshake Failed, Internal error - Bad handle.

  • Reason: An internal error has occurred.

  • Solution: Report this problem to Service.

• Message: SSL0202E: Handshake Failed, The GSK library unloaded.

  • Reason: A call to the GSKit function failed because the dynamic link library unloaded (Windows operating systems only).

  • Solution: Shut down the server and restart.

• Message: SSL0203E: Handshake Failed, GSK internal error.

  • Reason: The communication between client and the server failed due to an error in the GSKit library.

  • Solution: Retry connection from the client. If the error continues, report the problem to Service.

• Message: SSL0204E: Handshake Failed, Internal memory allocation failure.

  • Reason: The server could not allocate memory needed to complete the operation.

  • Solution: Take action to free up some additional memory. Try reducing the number of threads or processes running, or increasing virtual memory.

• Message: SSL0205E: Handshake Failed, GSK handle is in an invalid state for operation.

  • Reason: The SSL state for the connection is invalid.

  • Solution: Retry connection from the client. If the error continues, report the problem to Service.

• Message: SSL0205E: Handshake Failed, GSK handle is in an invalid state for operation.

  • Reason: The SSL state for the connection is invalid.

  • Solution: Retry connection from the client. If the error continues, report the problem to Service.

• Message: SSL0207E: Handshake Failed, Certificate is not available.

  • Reason: The client did not send a certificate.

  • Solution: Set client authentication to optional if a client certificate is not required. Contact the client to determine why it is not sending an acceptable certificate.

• Message: SSL0208E: Handshake Failed, Certificate validation error.

  • Reason: The received certificate failed one of the validation checks.

  • Solution: Use another certificate. Contact Service to determine why the certificate failed validation.

• Message: SSL0209E: Handshake Failed, ERROR processing cryptography.

  • Reason: A cryptography error occurred.

  • Solution: None. If the problem continues, report it to Service.

• Message: SSL0210E: Handshake Failed, ERROR validating ASN fields in certificate.

  • Reason: The server was not able to validate one of the ASN fields in the certificate.

  • Solution: Try another certificate.

• Message: SSL0211E: Handshake Failed, ERROR connecting to LDAP server.

  • Reason: The Web server failed to connect to the CRL LDAP server.

  • Solution: Verify that the values entered for the SSLCRLHostname and SSLCRLPort directives are correct. If access to the CRL LDAP server requires authentication, is the SSLCRLUserID directive coded and was the password added to the stash file pointed to by the SSLStashfile directive.

• Message: SSL0212E: Handshake Failed, Internal unknown error.

  • Report problem to Service. Reason: An unknown error has occurred in the SSL library.

  • Solution: Report the problem to Service.

• Message: SSL0213E: Handshake Failed, Open failed due to cipher error.

  • Reason: An unknown error has occurred in the SSL library.

  • Solution: Report the problem to Service.

• Message: SSL0214E: Handshake Failed, I/O error reading key file.

  • Reason: The server could not read the key database file.

  • Solution: Check file access permissions and verify the Web server user ID is allowed access.

• Message: SSL0215E: Handshake Failed, Key file has an invalid internal format. Recreate key file.

  • Reason: Key file has an invalid format.

  • Solution: Recreate key file.

• Message: SSL0216E: Handshake Failed, Key file has two entries with the same key. Use iKeyman to remove the duplicate key.

  • Reason: Two identical keys exist in key file.

  • Solution: Use iKeyman to remove duplicate key.

• Message: SSL0217E: Handshake Failed, Key file has two entries with the same label. Use iKeyman to remove the duplicate label.

  • Reason: A second certificate with the same label was placed in the key database file.

  • Solution: Use iKeyman to remove duplicate label.

• Message: SSL0218E: Handshake failed, Either the key file has become corrupted or the password is incorrect.

  • Reason: The key file password is used as an integrity check and the test failed. Either the key database file is corrupted, or the password is incorrect.

  • Solution: Use iKeyman to stash the key database file password again. If that fails, recreate the key database.

• Message: SSL0219E: Handshake Failed, The default key in the key file has an expired certificate. Use iKeyman to remove certificates that are expired.

  • Reason: An expired certificate exists in the key file and is the default.

  • Solution: Use iKeyman to select another certificate as the default.

• Message: SSL0220E: Handshake Failed, There was an error loading one of the GSKdynamic link libraries. Be sure GSK was installed correctly.

  • Reason: Opening the SSL environment resulted in an error because one of the GSKdynamic link libraries could not load.

  • Solution: Contact Support to make sure the GSKit is installed correctly.

• Message: SSL0221E: Handshake Failed, Invalid date.

  • Reason: The system date was set to an invalid date.

  • Solution: Change the system date to a valid date.

• Message: SSL0222W: Handshake failed, no ciphers specified.

  • Reason: SSLV2 and SSLV3 are disabled.

  • Solution: None. Report this problem to Service.

• Message: SSL0223E: Handshake Failed, No certificate.

  • Reason: The client did not send a certificate.

    We can also see this message when our keyfile does not have a default certificate specified and we have not specified an SSLServerCert directive. It will pass initialization but fail at connection (handshake) time.

  • Solution: Set client authentication to optional if a client certificate is not required. Contact the client to determine why it is not sending a certificate.

• Message: SSL0224E: Handshake failed, Invalid or improperly formatted certificate.

  • Reason: The client did not specify a valid certificate.

  • Solution: Client problem.

• Message: SSL0225E: Handshake Failed, Unsupported certificate type.

  • Reason: The certificate type received from the client is not supported by this version of IBM HTTP Server SSL.

  • Solution: The client must use a different certificate type.

• Message: SSL0226I: Handshake Failed, I/O error during handshake.

  • Reason: The communication between the client and the server failed. This is a common error when the client closes the connection before the handshake has completed.

  • Solution: Retry the connection from the client.

• Message: SSL0227E: Handshake Failed, Specified label could not be found in the key file.

  • Reason: Specified key label is not present in key file.

  • Solution: Check that the SSLServerCert directive is correct, if coded, and that the label is valid for one of the keys in the key database.

• Message: SSL0228E: Handshake Failed, Invalid password for key file.

  • Reason: The password retrieved from the stash file could not open the key database file.

  • Solution: Use iKeyman to open the key database file and recreate the password stash file. This problem can also result from a corrupted key database file. Creating a new key database file may resolve the problem.

• Message: SSL0229E: Handshake Failed, Invalid key length for export.

  • Reason: In a restricted cryptography environment, the key size is too long to be supported.

  • Solution: Select a certificate with a shorter key.

• Message: SSL0230I: Handshake Failed, An incorrectly formatted SSL message was received.

• Message: SSL0231W: Handshake Failed, Could not verify MAC.

  • Reason: The communication between the client and the server failed.

  • Solution: Retry the connection from the client.

• Message: SSL0232W: Handshake Failed, Unsupported SSL protocol or unsupported certificate type.

  • Reason: The communication between the client and the server failed because the client is trying to use a protocol or certificate which the IBM HTTP Server does not support.

  • Solution: Retry the connection from the client using an SSL V2 or 3, or TLS 1 protocol. Try another certificate.

• Message: SSL0233W: Handshake Failed, Invalid certificate signature.

• Message: SSL0234W: Handshake Failed, Invalid certificate sent by partner.

  • Reason: The partner did not specify a valid certificate. The server is acting as a reverse proxy to an SSL URL and the _server_ cert could not be validated.

  • Solution: Partner problem. If this occurs during an SSL Proxy connection, the remote SSL server sent a bad certificate to IBM HTTP Server. Check the certificate and certificate authority chain at the other end of the SSL connection. For more information, see Securing with SSL communications.

• Message: SSL0235W: Handshake Failed, Invalid peer.

• Message: SSL0236W: Handshake Failed, Permission denied.

• Message: SSL0237W: Handshake Failed, The self-signed certificate is not valid.

• Message: SSL0238E: Handshake Failed, Internal error - read failed.

  • Reason: The read failed.

  • Solution: None. Report this error to Service.

• Message: SSL0239E: Handshake Failed, Internal error - write failed.

  • Reason: The write failed.

  • Solution: None. Report this error to Service.

• Message: SSL0240I: Handshake Failed, Socket has been closed.

  • Reason: The client closed the socket before the protocol completed.

  • Solution: Retry connection between client and server.

• Message: SSL0241E: Handshake Failed, Invalid SSLV2 Cipher Spec.

  • Reason: The SSL V2 cipher specifications passed into the handshake were invalid.

  • Solution: Change the specified V2 cipher specs.

• Message: SSL0242E: Handshake Failed, Invalid SSLV3 Cipher Spec.

  • Reason: The SSL V3 cipher specifications passed into the handshake were invalid.

  • Solution: Change the specified V3 cipher specs.

• Message: SSL0243E: Handshake Failed, Invalid security type.

  • Reason: There was an internal error in the SSL library.

  • Solution: Retry the connection from the client. If the error continues, report the problem to Service.

• Message: SSL0245E: Handshake Failed, Internal error - SSL Handle creation failure.

  • Reason: There was an internal error in the security libraries.

  • Solution: None. Report this problem to Service.

• Message: SSL0246E: Handshake Failed, Internal error - GSK initialization has failed.

  • Reason: An error in the security library has caused SSL initialization to fail.

  • Solution: None. Report this problem to Service.

• Message: SSL0247E: Handshake Failed, LDAP server not available.

  • Reason: Unable to access the specified LDAP directory when validating a certificate.

  • Solution: Check that the SSLCRLHostname and SSLCRLPort directives are correct. Make sure the LDAP server is available.

• Message: SSL0248E: Handshake Failed, The specified key did not contain a private key.

  • Reason: The key does not contain a private key.

  • Solution: Create a new key. If this was an imported key, include the private key when doing the export.

• Message: SSL0249E: Handshake Failed, A failed attempt was made to load the specified PKCS#11 shared library.

  • Reason: An error occurred while loading the PKCS#11 shared library.

  • Solution: Verify that the PKCS#11 shared library specified in the SSLPKCSDriver directive is valid.

• Message: SSL0250E: Handshake Failed, The PKCS#11 driver failed to find the token label specified by the caller.

  • Reason: The specified token was not found on the PKCS#11 device.

  • Solution: Check that the token label specified on the SSLServerCert directive is valid for our device.

• Message: SSL0251E: Handshake Failed, A PKCS#11 token is not present for the slot.

  • Reason: The PKCS#11 device has not been initialized correctly.

  • Solution: Specify a valid slot for the PKCS#11 token or initialize the device.

• Message: SSL0252E: Handshake Failed, The password/pin to access the PKCS#11 token is either not present, or invalid.

  • Reason: Specified user password and pin for PKCS#11 token is not present or invalid.

  • Solution: Check that the correct password was stashed using the SSLStash utility and that the SSLStashfile directive is correct.

• Message: SSL0253E: Handshake Failed, The SSL header received was not a properly SSLV2 formatted header.

  • Reason: The data received during the handshake does not conform to the SSLV2 protocol.

  • Solution: Retry connection between client and server. Verify that the client is using HTTPS.

• Message: SSL0254E: Internal error - I/O failed, buffer size invalid.

  • Reason: The buffer size in the call to the I/O function is zero or negative.

  • Solution: None. Report this problem to Service.

• Message: SSL0255E: Handshake Failed, Operation would block.

  • Reason: The I/O failed because the socket is in non-blocking mode.

  • Solution: None. Report this problem to Service.

• Message: SSL0256E: Internal error - SSLV3 is required for reset_cipher, and the connection uses SSLV2.

  • Reason: A reset_cipher function was attempted on an SSLV2 connection.

  • Solution: None. Report this problem to Service.

• Message: SSL0257E: Internal error - An invalid ID was specified for the gsk_secure_soc_misc function call.

  • Reason: An invalid value was passed to the gsk_secure_soc_misc function.

  • Solution: None. Report this problem to Service.

• Message: SSL0258E: Handshake Failed, The function call, <function>, has an invalid ID.

  • Reason: An invalid function ID was passed to the specified function.

  • Solution: None. Report this problem to Service.

• Message: SSL0259E: Handshake Failed, Internal error - The attribute has a negative length in: <function>.

  • Reason: The length value passed to the function is negative, which is invalid.

  • Solution: None. Report this problem to Service.

• Message: SSL0260E: Handshake Failed, The enumeration value is invalid for the specified enumeration type in: <function>.

  • Reason: The function call contains an invalid function ID.

  • Solution: None. Report this problem to Service.

• Message: SSL0261E: Handshake Failed, The SID cache is invalid: <function>.

  • Reason: The function call contains an invalid parameter list for replacing the SID cache routines.

  • Solution: None. Report this problem to Service.

• Message: SSL0262E: Handshake Failed, The attribute has an invalid numeric value: <function>.

  • Reason: The function call contains an invalid value for the attribute being set.

  • Solution: None. Report this problem to Service.

• Message: SSL0263W: SSL Connection attempted when SSL did not initialize.

  • Reason: A connection was received on an SSL-enabled virtual host but it could not be completed because there was an error during SSL initialization.

  • Solution: Check for an error message during startup and correct that problem.

• Message: SSL0264E: Failure obtaining Cert data for label <certificate>.

  • Reason: A GSKit error prevented the server certificate information from being retrieved.

  • Solution: Check for a previous error message with additional information.

• Message: SSL0265W: Client did not supply a certificate.

  • Reason: A client who connected failed to send a client certificate and the server is configured to require a certificate.

  • Solution: Nothing on the server side.

• Message: SSL0266E: Handshake failed.

  • Reason: Could not establish SSL proxy connection.

  • Solution: IBM HTTP Server could not establish a proxy connection to a remote server using SSL.

• Message: SSL0267E: SSL Handshake failed.

  • Reason: Timeout on network operation during handshake.

  • Solution: Check client connectivity, adjust TimeOuts.

---

 

Related reference

SSL directives