A new era in Business process Management

What is IBM WebSphere Business Modeler software

IBM WebSphere Business Modeler software is the tool for documenting and understanding existing processes. It can help you visualize, document and model business processes for understanding and process execution, enabling you to rework older business processes into more agile ones or create new processes from scratch. The software enables users to make informed decisions about deployment with advanced analysis and simulation capabilities based on modeled and actual data. Business analysts can visualize and identify bottlenecks to better optimize processes. This robust modeling tool can then turn these process models into executable business processes for automation.


What is IBM WebSphere Dynamic Process Edition software
To realize the full potential of business processes, organizations with diverse,constantly evolving IT environments need comprehensive BPM capabilities, including modeling and simulation, rapid deployment and real-time business process monitoring and analysis. IBM WebSphere Dynamic Process Edition includes all of these capabilities and organizes SOA and BPM infrastructure into shareable, reusable intelligent business services, for a fully realized SOA vision of architectural agility and reuse.

What is IBM WebSphere Industry Content Pack assets
IBM WebSphere Industry Content Packs provide prebuilt assets to speed and enhance BPM solution delivery from modeling to deployment to monitoring including maps and models, service schemas and interfaces, key performance indicators (KPIs), business glossaries and end-to-end solution examples. Based on industry standards, they can help to reduce risk and increase consistency and reuse across the different lines of business within an enterprise and are available for banking, healthcare, insurance, industrial product life-cycle manageme
and telecommunications. The industry content packs are a core part of the IBM Industry Frameworks, which combine the power of award-winning IBM software with industry-specific assets and best practices specifically configured to meet an industry’s specific challenges and needs.

What is IBM WebSphere Transformation Extender software
IBM WebSphere Transformation Extender software increases the speed and reliability with which SOA applications and services can be extended beyond organizational walls to partners, suppliers and customers. For industry-specific data solutions, enterprises can leverage predefined WebSphere Transformation Extender Industry Packs, including healthcare, financial services, insurance and electronic data interchange (EDI). Complex industry transformations can be deployed quickly, with relative ease, helping to increase transaction volume while providing additional flexibility and fostering adaptability to industry changes. WebSphere Transformation Extender software helps remove risk from projects where regulatory bodies or industry service providers require strict conformance to mandatory and advisory guidelines.

What is IBM WebSphere Business Monitor software
When business leaders can link operational metrics to business strategy, their decision-making ability improves. WebSphere Business Monitor software provides real-time insight into business processes, presented in easy-to-read role-based business dashboards. Users can integrate existing business activity monitoring capabilities into WebSphere Business Monitor dashboards, along with other BPM, enterprise resource planning (ERP) and legacy applications, for more holistic process management. And the software offers an embedded metrics library of more than 800 open standard KPIs.

Troubleshooting IBM HTTP Server

Troubleshooting IBM HTTP Server.

Viewing error messages for a server that fails to start

If you encounter an error starting a HTTP server, you can view the error message in the server logs.

About :

If the target Web server fails to start, a message might appear on the WebSphere Application Server administrative console that indicates that the Web server cannot be started and to view the error messages in the server logs for further details. The types of errors that can result are:

•errors due to caching problems
•errors due to configuration problems
•errors due to SSL handshake failures
•errors due to SSL initialization problems
•errors due to I/O failures
•errors due to Secure Sockets Layer (SSL) stash utility problems





Cache messages
This topic contains error messages that might result due to caching problems and provides a solution to help you troubleshoot the problem.
The following messages are displayed due to caching problems:
• Message: SSL0600E: Unable to connect to session ID cache
o Reason: The server cannot connect to the Session ID caching daemon.
o Solution: Verify that the daemon successfully started.
• Message: SSL0601E: Session ID cache daemon process exited with exit code ; restarting
o Reason: If the value of is 0, the session ID cache daemon (sidd) received the SIGTERM signal. Other exit codes are not expected. Sidd automatically restarted.
o Solution: If the value of is 0 and IBM® HTTP Server did not stop or restart, verify that locally installed CGI scripts, scheduled operating system tasks, or other monitoring software cannot send SIGTERM to sidd.
• Message: SSL0602E: Session ID cache daemon process exited with terminating signal ; restarting
o Reason: The session ID cache daemon (sidd) received a signal other than SIGTERM was received by the session ID cache daemon (sidd), which caused it to exit. Sidd automatically restarted.
o Solution: If the value of is 0 and IBM HTTP Server did not stop or restart, verify that locally installed CGI scripts, scheduled operating system tasks, or other monitoring software cannot send the signal to sidd.
• Message: SSL0603E: Session ID cache daemon process exited with exit code; not restarting; check sidd configuration or enable sidd error log with SSLCacheErrorLog
o Reason: The session ID cache daemon (sidd) did not initialize. The following possible exit code values might be displayed:
Value Reason
2 Log files could not be opened. The SSLCacheTraceLog or the SSLCacheErrorLog directive is not valid.
3 The AF_UNIX socket cannot be initialized. Use the SSLCachePortFilename directive to specify a different socket for the session ID cache daemon.
4 Sidd cannot switch to the configured user and group. Verify the values for the user and group directives.
o Solution: Provide a valid value for the directives and restart IBM HTTP Server.

Configuration messages
This topic contains error messages that might result due to configuration problems and provides solutions to help you troubleshoot these problems.
The following messages appear due to configuration problems:
• Message: SSL0300E: Unable to allocate terminal node.
• Message: SSL0301E: Unable to allocate string value in node.
• Message: SSL0302E: Unable to allocate non terminal node.
• Message: SSL0303E: Syntax Error in SSLClientAuthGroup directive.
• Message: SSL0304E: Syntax Error in SSLClientAuthRequire directive.
• Message: SSL0307E: Invalid token preceding NOT or !
• Message: SSL0308E: A group is specified in SSLClientAuthRequire but no groups are specified.
• Message: SSL0309E: The group is specified in SSLClientAuthRequire is not defined.
• Message: SSL0310I: Access denied to object due to invalid SSL version , expected .
• Message: SSL0311E: Unable to get cipher in checkBanCipher.
• Message: SSL0312I: Cipher is in ban list and client is forbidden to access object.
• Message: SSL0313E: Fell through to default return in checkCipherBan.
• Message: SSL0314E: Cipher is NULL in checkRequireCipher.
• Message: SSL0315E: Cipher used is not in the list of required ciphers to access this object.
• Message: SSL0316E: Fell through to default return in checkCipherRequire.
• Message: SSL0317E: Unable to allocate memory for fake basic authentication username.
• Message: SSL0318E: Limit exceeded for specified cipher specs, only 64 total allowed.
o Reason: The number of ciphers configured using the SSLCipherSpec directive exceeds the maximum allowed of 64.
o Solution: Check for duplicate SSLCipherSpec directives.
• Message: SSL0319E: Cipher Spec is not supported by this GSK library.
o Reason: The cipher is not a valid cipher for use with the installed SSL libraries.
o Solution: Check that a valid cipher value was entered with the SSLCipherSpec directive.
• Message: SSL0320I: Using Version 2|3 Cipher: .
o Reason: This is an informational message listing the ciphers used for connections to this virtual host.
o Solution: None.
• Message: SSL0321E: Invalid cipher spec .
o Reason: The cipher is not a valid cipher.
o Solution: Check the documentation for a list of valid cipher specs.
• Message: SSL0322E: Cipher Spec is not valid.
o Reason: The cipher is not a valid cipher.
o Solution: Check the documentation for a list of valid cipher specs.
• Message: SSL0323E: Cipher Spec has already been added.
o Reason: A duplicate SSLCipherSpec directive has been encountered.
o Solution: This instance of the directive is ignored and should be removed from the configuration file.
• Message: SSL0324E: Unable to allocate storage for cipher specs.
o Reason: The server could not allocate memory needed to complete the operation.
o Solution: Take action to free up some additional memory. Try reducing the number of threads or processes running, or increasing virtual memory.
• Message: SSL0325E: Cipher Spec has already been added to the v2|v3 ban|require list.
o Reason: A duplicate cipher was specified on the SSLCipherBan directive.
o Solution: This instance of the directive is ignored and should be removed from the configuration file.
• Message: SSL0326E: Invalid cipher spec set for SSLCipherBan|SSLCipherRequire.
o Reason: The cipher is not a valid cipher.
o Solution: Check the documentation for a list of valid cipher specs.
• Message: SSL0327E: Invalid value for sslv2timeout|sslv3timeout, using default value of nn seconds.
o Reason: The timeout value specified is not in the valid range.
o Solution: Check the documentation for the proper range of values.
• Message: SSL0328W: Invalid argument for SSLClientAuth: . CRL can not be turned on unless Client Authentication is on.
• Message: SSL0329W: Invalid argument for SSLClientAuth: . If a second argument is entered it must be CRL. CRL cannot be turned on unless client authentication is on.
• Message: SSL0330W: Invalid argument for SSLClientAuth: . If a second value is entered it must be crl.
• Message: SSL0331W: Invalid argument for SSLClientAuth: . The first value must be 0, 1, 2 none, optional, or required.
• Message: SSL0332E: Not enough arguments specified for SSLClientAuthGroup.
• Message: SSL0333E: No parse tree created for .
o Reason: An error occurred processing the SSLClientAuthRequire directive.
o Solution: Check for other error messages. Enable tracing of Client Authentication by adding the directive SSLClientAuthRequireTraceOn to the configuration file.
• Message: SSL0334E: Function ap_make_table failed processing label .
• Message: SSL0337E: OCSP is not supported with this level of GSKit
o Reason: OCSP support requires GSKit 7.0.4.14 or higher
o Solution: Upgrade the level of GSKit on the system to 7.0.4.14 or higher

Handshake messages
This topic contains error messages that might result due to SSL handshake failures and provides solutions to help you troubleshoot these problems.
The following messages display due to handshake failures:
• Message: SSL0200E: Handshake Failed, .
o Reason: The handshake failed when the SSL library returned an unknown error.
o Solution: Report this problem to Service.
• Message: SSL0201E: Handshake Failed, Internal error - Bad handle.
o Reason: An internal error has occurred.
o Solution: Report this problem to Service.
• Message: SSL0202E: Handshake Failed, The GSK library unloaded.
o Reason: A call to the GSKit function failed because the dynamic link library unloaded (Windows® operating systems only).
o Solution: Shut down the server and restart.
• Message: SSL0203E: Handshake Failed, GSK internal error.
o Reason: The communication between client and the server failed due to an error in the GSKit library.
o Solution: Retry connection from the client. If the error continues, report the problem to Service.
• Message: SSL0204E: Handshake Failed, Internal memory allocation failure.
o Reason: The server could not allocate memory needed to complete the operation.
o 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.
o Reason: The SSL state for the connection is invalid.
o Solution: Retry connection from the client. If the error continues, report the problem to Service.
• Message: SSL0206E: Handshake Failed, Key-file label not found
o Reason: The label specified for the SSLServerCert directive was not found in the key database (KDB) file specified for the KeyFile directive.
o Solution: Specify a value for the SSLServerCert directive that corresponds to a personal certificate available in the KDB file specified for the KeyFile directive
• Message: SSL0207E: Handshake Failed, Certificate is not available.
o Reason: The client did not send a certificate.
o 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.
o Reason: The received certificate failed one of the validation checks.
o Solution: Use another certificate. Contact Service to determine why the certificate failed validation.
• Message: SSL0209E: Handshake Failed, ERROR processing cryptography.
o Reason: A cryptography error occurred.
o Solution: None. If the problem continues, report it to Service.
• Message: SSL0210E: Handshake Failed, ERROR validating ASN fields in certificate.
o Reason: The server was not able to validate one of the ASN fields in the certificate.
o Solution: Try another certificate.
• Message: SSL0211E: Handshake Failed, ERROR connecting to LDAP server.
o Reason: The Web server failed to connect to the CRL LDAP server.
o 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.
o Report problem to Service. Reason: An unknown error has occurred in the SSL library.
o Solution: Report the problem to Service.
• Message: SSL0213E: Handshake Failed, Open failed due to cipher error.
o Reason: An unknown error has occurred in the SSL library.
o Solution: Report the problem to Service.
• Message: SSL0214E: Handshake Failed, I/O error reading key file.
o Reason: The server could not read the key database file.
o 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.
o Reason: Key file has an invalid format.
o Solution: Recreate key file.
• Message: SSL0216E: Handshake Failed, Key file has two entries with the same key. Use IKEYMAN to remove the duplicate key.
o Reason: Two identical keys exist in key file.
o 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.
o Reason: A second certificate with the same label was placed in the key database file.
o Solution: Use IKEYMAN to remove duplicate label.
• Message: SSL0218E: Handshake failed, Either the key file has become corrupted or the password is incorrect.
o 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.
o Solution: Use IKEYMAN to stash the key database file password again. If that fails, recreate the key database.
• Message: SSL0219E: SSL Handshake Failed, Either the default key in the keyfile has an expired certificate or the keyfile password expired. Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.
o Reason: Either the default key in the keyfile has an expired certificate or the keyfile password expired.
o Solution: Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.
• Message: SSL0220E: Handshake Failed, There was an error loading one of the GSKdynamic link libraries. Be sure GSK was installed correctly.
o Reason: Opening the SSL environment resulted in an error because one of the GSKdynamic link libraries could not load.
o Solution: Contact Support to make sure the GSKit is installed correctly.
• Message: SSL0221E: Handshake Failed, Either the certificate has expired or the system clock is incorrect.
o Reason: Either the certificate expired or the system clock is incorrect.
o Solution: Use the key management utility (iKeyman) to recreate or renew your server certificate or change the system date to a valid date.
• Message: SSL0222W: Handshake failed, no ciphers specified.
o Reason: SSLV2 and SSLV3 are disabled.
o Solution: None. Report this problem to Service.
• Message: SSL0223E: Handshake Failed, No certificate.
o Reason: The client did not send a certificate.
You can also see this message when your keyfile does not have a default certificate specified and you have not specified an SSLServerCert directive. It will pass initialization but fail at connection (handshake) time.
o 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.
o Reason: The client did not specify a valid certificate.
o Solution: Client problem.
• Message: SSL0225E: Handshake Failed, Unsupported certificate type.
o Reason: The certificate type received from the client is not supported by this version of IBM® HTTP Server SSL.
o Solution: The client must use a different certificate type.
• Message: SSL0226I: Handshake Failed, I/O error during handshake.
o 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.
o Solution: Retry the connection from the client.
• Message: SSL0227E: Handshake Failed, Specified label could not be found in the key file.
o Reason: Specified key label is not present in key file.
o 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.
o Reason: The password retrieved from the stash file could not open the key database file.
o 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.
o Reason: In a restricted cryptography environment, the key size is too long to be supported.
o 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.
o Reason: The communication between the client and the server failed.
o Solution: Retry the connection from the client.
• Message: SSL0232W: Handshake Failed, Unsupported SSL protocol or unsupported certificate type.
o 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.
o Solution: Retry the connection from the client using an SSL Version 2 or 3, or TLS 1 protocol. Try another certificate.
• Message: SSL0233W: Handshake Failed, Invalid certificate signature.
• Message: SSL0234W: Handshake Failed, The certificate sent by the peer expired or is invalid.
o 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.
o 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.
o Reason: The read failed.
o Solution: None. Report this error to Service.
• Message: SSL0239E: Handshake Failed, Internal error - write failed.
o Reason: The write failed.
o Solution: None. Report this error to Service.
• Message: SSL0240I: Handshake Failed, Socket has been closed.
o Reason: The client closed the socket before the protocol completed.
o Solution: Retry connection between client and server.
• Message: SSL0241E: Handshake Failed, Invalid SSLV2 Cipher Spec.
o Reason: The SSL Version 2 cipher specifications passed into the handshake were invalid.
o Solution: Change the specified Version 2 cipher specs.
• Message: SSL0242E: Handshake Failed, Invalid SSLV3 Cipher Spec.
o Reason: The SSL Version 3 cipher specifications passed into the handshake were invalid.
o Solution: Change the specified Version 3 cipher specs.
• Message: SSL0243E: Handshake Failed, Invalid security type.
o Reason: There was an internal error in the SSL library.
o 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.
o Reason: There was an internal error in the security libraries.
o Solution: None. Report this problem to Service.
• Message: SSL0246E: Handshake Failed, Internal error - GSK initialization has failed.
o Reason: An error in the security library has caused SSL initialization to fail.
o Solution: None. Report this problem to Service.
• Message: SSL0247E: Handshake Failed, LDAP server not available.
o Reason: Unable to access the specified LDAP directory when validating a certificate.
o 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.
o Reason: The key does not contain a private key.
o 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.
o Reason: An error occurred while loading the PKCS#11 shared library.
o 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.
o Reason: The specified token was not found on the PKCS#11 device.
o Solution: Check that the token label specified on the SSLServerCert directive is valid for your device.
• Message: SSL0251E: Handshake Failed, A PKCS#11 token is not present for the slot.
o Reason: The PKCS#11 device has not been initialized correctly.
o 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.
o Reason: Specified user password and pin for PKCS#11 token is not present or invalid.
o 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.
o Reason: The data received during the handshake does not conform to the SSLV2 protocol.
o Solution: Retry connection between client and server. Verify that the client is using HTTPS.
• Message: SSL0254E: Internal error - I/O failed, buffer size invalid.
o Reason: The buffer size in the call to the I/O function is zero or negative.
o Solution: None. Report this problem to Service.
• Message: SSL0255E: Handshake Failed, Operation would block.
o Reason: The I/O failed because the socket is in non-blocking mode.
o Solution: None. Report this problem to Service.
• Message: SSL0256E: Internal error - SSLV3 is required for reset_cipher, and the connection uses SSLV2.
o Reason: A reset_cipher function was attempted on an SSLV2 connection.
o Solution: None. Report this problem to Service.
• Message: SSL0257E: Internal error - An invalid ID was specified for the gsk_secure_soc_misc function call.
o Reason: An invalid value was passed to the gsk_secure_soc_misc function.
o Solution: None. Report this problem to Service.
• Message: SSL0258E: Handshake Failed, The function call, , has an invalid ID.
o Reason: An invalid function ID was passed to the specified function.
o Solution: None. Report this problem to Service.
• Message: SSL0259E: Handshake Failed, Internal error - The attribute has a negative length in: .
o Reason: The length value passed to the function is negative, which is invalid.
o Solution: None. Report this problem to Service.
• Message: SSL0260E: Handshake Failed, The enumeration value is invalid for the specified enumeration type in: .
o Reason: The function call contains an invalid function ID.
o Solution: None. Report this problem to Service.
• Message: SSL0261E: Handshake Failed, The SID cache is invalid: .
o Reason: The function call contains an invalid parameter list for replacing the SID cache routines.
o Solution: None. Report this problem to Service.
• Message: SSL0262E: Handshake Failed, The attribute has an invalid numeric value: .
o Reason: The function call contains an invalid value for the attribute being set.
o Solution: None. Report this problem to Service.
• Message: SSL0263W: SSL Connection attempted when SSL did not initialize.
o 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.
o Solution: Check for an error message during startup and correct that problem.
• Message: SSL0264E: Failure obtaining Cert data for label .
o Reason: A GSKit error prevented the server certificate information from being retrieved.
o Solution: Check for a previous error message with additional information.
• Message: SSL0265W: Client did not supply a certificate.
o Reason: A client who connected failed to send a client certificate and the server is configured to require a certificate.
o Solution: Nothing on the server side.
• Message: SSL0266E: Handshake failed.
o Reason: Could not establish SSL proxy connection.
o Solution: IBM HTTP Server could not establish a proxy connection to a remote server using SSL.
• Message: SSL0267E: SSL Handshake failed.
o Reason: Timeout on network operation during handshake.
o Solution: Check client connectivity, adjust TimeOuts.
• Message: SSL0270I: SSL Handshake Failed, Timeout (dd seconds) occurred before any data received.
o Reason: A connection was received on an SSL port, but no data was received from the client before the timeout expired.
o Solution: If the timeout (set by the Timeout directive) has been reduced from the default value, verify that it is reasonable. If the message occurs intermittently, it is probably normal, due to things like users cancelling page loads and browser or system crashes. If the message occurs in bursts, it might indicate a denial of service attack in progress.
• Message: SSL0271I: SSL Handshake Failed, client closed connection without sending any data.
o Reason: A connection was received on an SSL port, but the client closed the connection without beginning the handshake.
o Solution: If the timeout (set by the Timeout directive) has been reduced from the default value, verify that it is reasonable. If the message occurs intermittently, it is probably normal, due to things like users cancelling page loads and browser or system crashes. If the message occurs in bursts, it might indicate a denial of service attack in progress.
• Message: SSL0272I: SSL Handshake Failed, I/O error before any data received.
o Reason: A connection was received on an SSL port, but a network error broke the connection before any data was received from the client.
o Solution: If the message occurs intermittently, it is probably normal, due to things like users cancelling page loads and browser or system crashes. If the message occurs in bursts, it might indicate a denial of service attack in progress.
• Message: SSL0273I: Non-SSL request received on connection configured for SSL
o Reason: A connection was received on an SSL port, but the data received was not SSL, and looked like a normal non-SSL request.
o Solution: Verify that the port in question is intended to be configured for SSL. Look for bad links to the page in question that should use https:, but instead use http:.


SSL initialization messages
This topic contains error messages that might result due to SSL initialization problems and provides solutions to help you troubleshoot these problems.
The following messages display as a result of initialization problems:
• Message: SSL0100E: GSK could not initialize,
o Reason: Initialization failed when the SSL library returned an unknown error.
o Solution: None. Report this problem to Service.
• Message: SSL0101E: GSK could not initialize, Neither the password nor the stash file name was specified. Could not open key file.
o Reason: The stash file for the key database could not be found or is corrupted.
o Solution: Use IKEYMAN to open the key database file and recreate the password stash file.
• Message: SSL0102E: GSK could not initialize, Could not open key file.
o Reason: The server could not open the key database file.
o Solution: Check that the Keyfile directive is correct and that the file permissions allow the Web server user ID to access the file.
• Message: SSL0103E: Internal error - GSK could not initialize, Unable to generate a temporary key pair.
o Reason: GSK could not initialize; Unable to generate a temporary key pair.
o Solution: Report this problem to Service.
• Message: SSL0104E: GSK could not initialize, Invalid password for key file.
o Reason: The password retrieved from the stash file could not open the key database file.
o Solution: Use IKEYMAN to open the key database file and recreate the password stash file. This problem could also result from a corrupted key database file. Creating a new key database file may resolve the problem.
• Message: SSL0105E: GSK could not initialize, Invalid label.
o Reason: Specified key label is not present in key file.
o 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: SSL0106E: Initialization error, Internal error - Bad handle
o Reason: An internal error has occurred.
o Solution: Report this problem to Service.
• Message: SSL0107E: Initialization error, The GSK library unloaded.
o Reason: A call to the GSKit function failed because the dynamic link library unloaded (Windows® only).
o Solution: Shut down the server and restart.
• Message: SSL0108E: Initialization error, GSK internal error.
o Reason: The communication between client and the server failed due to an error in the GSKit library.
o Solution: Retry connection from the client. If the error continues, report the problem to Service.
• Message: SSL0109E: GSK could not initialize, Internal memory allocation failure.
o Reason: The server could not allocate memory needed to complete the operation.
o Solution: Take action to free up some additional memory. Try reducing the number of threads or processes running, or increasing virtual memory.
• Message :SSL0110E: Initialization error, GSK handle is in an invalid state for operation.
o Reason: The SSL state for the connection is invalid.
o Solution: Retry connection from the client. If the error continues, report the problem to Service.
• Message: SSL0111E: Initialization error, Key file label not found.
o Reason: Certificate or key label specified was not valid.
o Solution: Verify that the certificate name specified with the SSLServerCert directive is correct or, if no SSLServerCert directive was coded, that a default certificate exists in the key database.
• Message: SSL0112E: Initialization error, Certificate is not available.
o Reason: The client did not send a certificate.
o 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: SSL0113E: Initialization error, Certificate validation error.
o Reason: The received certificate failed one of the validation checks.
o Solution: Use another certificate. Contact Service to determine why the certificate failed validation.
• Message: SSL0114E: Initialization error, Error processing cryptography.
o Reason: A cryptography error occurred.
o Solution: None. If the problem continues, report it to Service.
• Message: SSL0115E: Initialization error, Error validating ASN fields in certificate.
o Reason: The server was not able to validate one of the ASN fields in the certificate.
o Solution: Try another certificate.
• Message: SSL0116E: Initialization error, Error connecting to LDAP server.
o Reason: The Web server failed to connect to the CRL LDAP server.
o 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: SSL0117E: Initialization error, Internal unknown error. Report problem to service.
o Reason: Initialization error, Internal unknown error. Report problem to service.
o Solution: Initialization error, Internal unknown error. Report problem to service.
• Message: SSL0118E: Initialization error, Open failed due to cipher error.
o Reason: Report problem to service.
o Solution: Report problem to service.
• Message: SSL0119E: Initialization error, I/O error reading keyfile.
o Reason: I/O error trying to read SSL keyfile.
o Solution: Check the file permissions for keyfile.
• Message: SSL0120E: Initialization error, Keyfile has and invalid internal format. Recreate keyfile.
o Reason: Initialization error, the keyfile has an invalid internal format. Recreate the keyfile.
o 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.
o Reason: The keyfile has two entries with the same key. Use Ikeyman to remove the duplicate key.
o 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.
o Reason: The keyfile has two entries with the same label. Use Ikeyman to remove the duplicate label.
o 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.
o Reason: The keyfile password is used as an integrity check. Either the keyfile has become corrupted or the password is incorrect.
o Solution: Use Ikeyman to verify that the keyfile is valid, check permissions on the stash file, verify passwords.
• Message: SSL0124E: SSL Handshake Failed, Either the default key in the keyfile has an expired certificate or the keyfile password expired. Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.
o Reason: Either the default key in the keyfile has an expired certificate or the keyfile password expired.
o Solution: Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.
• Message: SSL0125E: Initialization error, There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly.
o Reason: There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly.
o Solution: Verify GSK is installed and appropriate level for release of IBM® HTTP Server.
• Message: SSL0126E: Handshake Failed, Either the certificate has expired or the system clock is incorrect.
o Reason: Either the certificate expired or the system clock is incorrect.
o Solution: Use the key management utility (iKeyman) to recreate or renew your server certificate or change the system date to a valid date.
• Message: SSL0127E: Initialization error, No ciphers specified.
o Reason: Initialization error, no ciphers specified.
o Solution: Report problem to service.
• Message: SSL0128E: Initialization error, Either the certificate expired or the system clock is incorrect.
o Reason: Initialization error, no certificate.
o Solution: Report problem to service.
• Message: SSL0129E: Initialization error, The received certificate was formatted incorrectly.
o Reason: The received certificate is formatted incorrectly.
o Solution: Use Ikeyman to validate certificates used for connection.
• Message: SSL0130E: Initialization error, Unsupported certificate type.
o Reason: Unsupported certificate type.
o Solution: Check certificates that are used for this connection in Ikeyman.
• Message: SSL0131I: Initialization error, I/O error during handshake.
o Reason: I/O error during handshake.
o Solution: Check network connectivity.
• Message: SSL0132E: Initialization error, Invalid key length for export.
o Reason: Invalid key length for export.
o Solution: Report problem to service.
• Message: SSL0133W: Initialization error, An incorrectly formatted SSL message was received.
o Reason: An incorrectly formatted SSL message was received.
o Solution: Check client settings.
• Message: SSL0134W: Initialization error, Could not verify MAC.
o Reason: Could not verify MAC.
o Solution: Report problem to service.
• Message: SSL0135W: Initialization error, Unsupported SSL protocol or unsupported certificate type.
o Reason: Unsupported SSL protocol or unsupported certificate type.
o Solution: Check server ciphers and certificate settings.
• Message: SSL0136W: Initialization error, Invalid certificate signature.
o Reason: Invalid certificate signature.
o Solution: Check certificate in Ikeyman.
• Message: SSL0137W: Initialization error, Invalid certificate sent by partner.
o Reason: Invalid certificate sent by partner.
o 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.
o Reason: Invalid peer.
o Solution: Report problem to service.
• Message: SSL0139W: Initialization error, Permission denied. Distributed Platforms
o Reason: Permission denied.
o Solution: Report problem to service.
z/os
o Reason: If a System Authorization Facility (SAF) SSL keyring is in use, the current user ID is not authorized to read the keyring.
o Solution: See the information about access to SAF keyrings in Performing required z/OS system configurations
• Message: SSL0140W: Initialization error, The self-signed certificate is not valid.
o Reason: The self-signed certificate is not valid.
o Solution: Check the certificate in Ikeyman.
• Message: SSL0141E: Initialization error, Internal error - read failed.
o Reason: Internal error - read failed.
o Solution: Report to service.
• Message: SSL0142E: Initialization error, Internal error - write failed.
o Reason: Internal error - write failed.
o Solution: Report to service.
• Message: SSL0143I: Initialization error, Socket has been closed.
o Reason: Socket has been closed unexpectedly.
o Solution: Check the client and network. Report problem to service.
• Message: SSL0144E: Initialization error, Invalid SSLV2 Cipher Spec.
o Reason: Invalid SSLV2 cipher spec.
o Solution: Check the SSLCipherSpec directive.
• Message: SSL0145E: Initialization error, Invalid SSLV3 Cipher Spec.
o Reason: Invalid SSLV3 Cipher Spec.
o Solution: Check the SSLCipherSpec directive.
• Message: SSL0146E: Initialization error, Invalid security type.
o Reason: Invalid security type.
o Solution: Report to service.
• Message: SSL0147E: Initialization error, Invalid security type combination.
o Reason: Invalid security type combination.
o Solution: Report to service.
• Message: SSL0148E: Initialization error, Internal error - SSL Handle creation failure.
o Reason: Internal error - SSL handle creation failure.
o Solution: Report to service.
• Message: SSL0149E: Initialization error, Internal error - GSK initialization has failed.
o Reason: Internal error - GSK initialization has failed.
o Solution: Report to service.
• Message: SSL0150E: Initialization error, LDAP server not available.
o Reason: LDAP server not available.
o Solution: Check CRL directives.
• Message: SSL0151E: Initialization error, The specified key did not contain a private key.
o Reason: The specified key did not contain a private key.
o 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.
o Reason: A failed attempt was made to load the specified PKCS#11 shared library.
o Solution: Check SSLPKCSDriver directive and file system.
• Message: SSL0153E: Initialization error, The PKCS#11 driver failed to find the token specified by the caller.
o 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.
o Reason: A PKCS#11 token is not present for the slot.
o Solution: Verify PKCS#11 directives.
• Message: SSL0155E: Initialization error, The password/pin to access the PKCS#11 token is invalid.
o 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.
o Reason: The SSL header received was not a properly SSLV2 formatted header.
• Message: SSL0157E: Initialization error, The function call, %s, has an invalid ID.
o Reason: The function call, %s, has an invalid ID.
o Solution: Report problem to service.
• Message: SSL0158E: Initialization error, Internal error - The attribute has a negative length: %s.
o Reason: Internal error - The attribute has a negative length.
o Solution: Report problem to service.
• Message: SSL0159E: Initialization error, The enumeration value is invalid for the specified enumeration type: %s.
o Reason: The enumeration value is invalid for the specified enumeration type: %s.
o Solution: Report problem to service.
• Message: SSL0160E: Initialization error, The SID cache is invalid: %s.
o Reason: The SID cache is invalid.
o Solution: Report problem to service.
• Message: SSL0161E: Initialization error, The attribute has an invalid numeric value: %s.
o Reason: The attribute has an invalid numeric value: %s.
o Solution: Check SSL directives.
• Message: SSL0162W: Setting the LD_LIBRARY_PATH or LIBPATH for GSK failed.
o Reason: Could not update the environment for GSK libraries.
o Solution: Report problem to service.
• Message: SSL0163W: Setting the LIBPATH for GSK failed, could not append /usr/opt/ibm/gskkm/lib.
o Reason: Could not append to LD_LIBRARY_PATH or LIBPATH for GSK failed.
o Solution: Report problem to service.
• Message: SSL0164W: Error accessing Registry, RegOpenKeyEx/RegQueryValueEx returned [%d].
o Reason: Error accessing registry.
o Solution: Check GSK installation and windows registry.
• Message: SSL0165W: Storage allocation failed.
o Reason: Storage allocation failed.
o Solution: Check memory usage, report problem to service.
• Message: SSL0166E: Failure attempting to load GSK library.
o Reason: Failure while attempting to load GSK library.
o Solution: Check the GSK installation.
• Message: SSL0167E: GSK function address undefined.
o Reason: GSK function address is undefined.
o Solution: Check the GSK installation and level.
• Message: SSL0168E: SSL initialization for server: %s, port: %u failed due to a configuration error.
o Reason: Iinitialization for server: %s, port: %u failed due to a configuration error.
o Solution: Check the SSL configuration.
• Message: SSL0169E: Keyfile does not exist: %s.
o Reason: Keyfile does not exist.
o 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.
o Reason: Keyfile is not specified.
o 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.
o Reason: CRL cannot be specified as an option for the SSLClientAuth directive on HPUX because IBM HTTP Server does not support CRL on HPUX.
o Solution: Remove CRL directives.
• Message: SSL0172E: If CRL is turned on, you must specify an LDAP hostname for the SSLCRLHostname directive.
o Reason: If CRL is turned on, you must specify an LDAP hostname for the SSLCRLHostname directive.
o Solution: Specify SSLCRLHostname.
• Message: SSL0173E: Failure obtaining supported cipher specs from the GSK library.
o Reason: Failure obtaining supported cipher specs from the GSK library.
o Solution: Check the GSK installation, report problem to service.
• Message: SSL0174I: No CRL password found in the stash file: %s.
o Reason: No CRL password is found in the stash file: %s.
o Solution: Check the stash file permissions, regenerate stash file.
• Message: SSL0174I: No CRYPTO password found in the stash file: %s.
o Reason: No CRYPTO password is found in the stash file: %s.
o Solution: Check stash file permissions, regenerate stash file.
• Message: SSL0175E: fopen failed for stash file: %s.
o Reason: fopen failed for stash file.
o Solution: Check stash file permissions, regenerate stash file.
• Message: SSL0176E: fread failed for the stash file: %s.
o Reason: fread failed for the stash file.
o 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.
o Reason: Unknown return code from stash_recover(), %d.
o Solution: Check the stash file.
• Message: SSL0181E: Unable to fork for startup of session ID cache.
o Reason: Unable to fork for startup of session ID cache.
o Solution: Check the location of sidd daemon, file permissions.
• Message: SSL0182E: Error creating file mapped memory for SSL passwords.
o Reason: Error creating file mapped memory for SSL passwords.
o Solution: Report problem to service.
• Message: SSL0183E: Exceeded map memory limits.
o Reason: Exceeded map memory limits.
o Solution: Report problem to service.
• Message: SSL0184E: Could not find a password for the resource: %s.
o Reason: SSL0184E: Could not find a password for the resource: %s.
o Solution: Report problem to service, disable password prompting.
• Message: SSL0185E: ssl_getpwd() failed, unable to obtain memory.
o Reason: ssl_getpwd() failed, unable to obtain memory.
o Solution: Report problem to service, disable password prompting.
• Message: SSL0186E: Linked list mismatch.
o Reason: SSL0186E: Linked list mismatch.
o Solution: Report problem to service, disable password prompting.
• Message: SSL0186E: ssl_getpwd() failed, password exceeded maximum size of 4095.
o Reason: ssl_getpwd() failed, password exceeded the maximum size of 4095.
o 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.
o Reason: It is invalid to enable password prompting for the SSLServerCert directive without specifying a crypto card token.
o Solution: Specify a crypto card token or disable password prompting for the SSLServerCert directive.
• Message: SSL0188E: SSL initialization for server: %s, port: %u failed. SSL timeouts cannot be set in a virtualhost when the SSLCacheDisable directive has not been specified globally.
o Reason: When the SSL session cache is being used, only the global timeout settings apply because they are managed by the external session cache daemon. See information about the SSLCacheDisable and SSLCacheEnable directives in the information center topic entitled SSL directives.
o Solution: If separate SSL timeouts are required, disable use of the session ID cache (SSLCacheDisable), otherwise make sure the SSLV3Timeout and SSLV2Timeout directives are only set in the global scope.

SSL initialization messages
This topic contains error messages that might result due to SSL initialization problems and provides solutions to help you troubleshoot these problems.
The following messages display as a result of initialization problems:
• Message: SSL0100E: GSK could not initialize,
o Reason: Initialization failed when the SSL library returned an unknown error.
o Solution: None. Report this problem to Service.
• Message: SSL0101E: GSK could not initialize, Neither the password nor the stash file name was specified. Could not open key file.
o Reason: The stash file for the key database could not be found or is corrupted.
o Solution: Use IKEYMAN to open the key database file and recreate the password stash file.
• Message: SSL0102E: GSK could not initialize, Could not open key file.
o Reason: The server could not open the key database file.
o Solution: Check that the Keyfile directive is correct and that the file permissions allow the Web server user ID to access the file.
• Message: SSL0103E: Internal error - GSK could not initialize, Unable to generate a temporary key pair.
o Reason: GSK could not initialize; Unable to generate a temporary key pair.
o Solution: Report this problem to Service.
• Message: SSL0104E: GSK could not initialize, Invalid password for key file.
o Reason: The password retrieved from the stash file could not open the key database file.
o Solution: Use IKEYMAN to open the key database file and recreate the password stash file. This problem could also result from a corrupted key database file. Creating a new key database file may resolve the problem.
• Message: SSL0105E: GSK could not initialize, Invalid label.
o Reason: Specified key label is not present in key file.
o 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: SSL0106E: Initialization error, Internal error - Bad handle
o Reason: An internal error has occurred.
o Solution: Report this problem to Service.
• Message: SSL0107E: Initialization error, The GSK library unloaded.
o Reason: A call to the GSKit function failed because the dynamic link library unloaded (Windows® only).
o Solution: Shut down the server and restart.
• Message: SSL0108E: Initialization error, GSK internal error.
o Reason: The communication between client and the server failed due to an error in the GSKit library.
o Solution: Retry connection from the client. If the error continues, report the problem to Service.
• Message: SSL0109E: GSK could not initialize, Internal memory allocation failure.
o Reason: The server could not allocate memory needed to complete the operation.
o Solution: Take action to free up some additional memory. Try reducing the number of threads or processes running, or increasing virtual memory.
• Message :SSL0110E: Initialization error, GSK handle is in an invalid state for operation.
o Reason: The SSL state for the connection is invalid.
o Solution: Retry connection from the client. If the error continues, report the problem to Service.
• Message: SSL0111E: Initialization error, Key file label not found.
o Reason: Certificate or key label specified was not valid.
o Solution: Verify that the certificate name specified with the SSLServerCert directive is correct or, if no SSLServerCert directive was coded, that a default certificate exists in the key database.
• Message: SSL0112E: Initialization error, Certificate is not available.
o Reason: The client did not send a certificate.
o 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: SSL0113E: Initialization error, Certificate validation error.
o Reason: The received certificate failed one of the validation checks.
o Solution: Use another certificate. Contact Service to determine why the certificate failed validation.
• Message: SSL0114E: Initialization error, Error processing cryptography.
o Reason: A cryptography error occurred.
o Solution: None. If the problem continues, report it to Service.
• Message: SSL0115E: Initialization error, Error validating ASN fields in certificate.
o Reason: The server was not able to validate one of the ASN fields in the certificate.
o Solution: Try another certificate.
• Message: SSL0116E: Initialization error, Error connecting to LDAP server.
o Reason: The Web server failed to connect to the CRL LDAP server.
o 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: SSL0117E: Initialization error, Internal unknown error. Report problem to service.
o Reason: Initialization error, Internal unknown error. Report problem to service.
o Solution: Initialization error, Internal unknown error. Report problem to service.
• Message: SSL0118E: Initialization error, Open failed due to cipher error.
o Reason: Report problem to service.
o Solution: Report problem to service.
• Message: SSL0119E: Initialization error, I/O error reading keyfile.
o Reason: I/O error trying to read SSL keyfile.
o Solution: Check the file permissions for keyfile.
• Message: SSL0120E: Initialization error, Keyfile has and invalid internal format. Recreate keyfile.
o Reason: Initialization error, the keyfile has an invalid internal format. Recreate the keyfile.
o 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.
o Reason: The keyfile has two entries with the same key. Use Ikeyman to remove the duplicate key.
o 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.
o Reason: The keyfile has two entries with the same label. Use Ikeyman to remove the duplicate label.
o 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.
o Reason: The keyfile password is used as an integrity check. Either the keyfile has become corrupted or the password is incorrect.
o Solution: Use Ikeyman to verify that the keyfile is valid, check permissions on the stash file, verify passwords.
• Message: SSL0124E: SSL Handshake Failed, Either the default key in the keyfile has an expired certificate or the keyfile password expired. Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.
o Reason: Either the default key in the keyfile has an expired certificate or the keyfile password expired.
o Solution: Use iKeyman to renew or remove certificates that are expired or to set a new keyfile password.
• Message: SSL0125E: Initialization error, There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly.
o Reason: There was an error loading one of the GSK dynamic link libraries. Be sure GSK is installed correctly.
o Solution: Verify GSK is installed and appropriate level for release of IBM® HTTP Server.
• Message: SSL0126E: Handshake Failed, Either the certificate has expired or the system clock is incorrect.
o Reason: Either the certificate expired or the system clock is incorrect.
o Solution: Use the key management utility (iKeyman) to recreate or renew your server certificate or change the system date to a valid date.
• Message: SSL0127E: Initialization error, No ciphers specified.
o Reason: Initialization error, no ciphers specified.
o Solution: Report problem to service.
• Message: SSL0128E: Initialization error, Either the certificate expired or the system clock is incorrect.
o Reason: Initialization error, no certificate.
o Solution: Report problem to service.
• Message: SSL0129E: Initialization error, The received certificate was formatted incorrectly.
o Reason: The received certificate is formatted incorrectly.
o Solution: Use Ikeyman to validate certificates used for connection.
• Message: SSL0130E: Initialization error, Unsupported certificate type.
o Reason: Unsupported certificate type.
o Solution: Check certificates that are used for this connection in Ikeyman.
• Message: SSL0131I: Initialization error, I/O error during handshake.
o Reason: I/O error during handshake.
o Solution: Check network connectivity.
• Message: SSL0132E: Initialization error, Invalid key length for export.
o Reason: Invalid key length for export.
o Solution: Report problem to service.
• Message: SSL0133W: Initialization error, An incorrectly formatted SSL message was received.
o Reason: An incorrectly formatted SSL message was received.
o Solution: Check client settings.
• Message: SSL0134W: Initialization error, Could not verify MAC.
o Reason: Could not verify MAC.
o Solution: Report problem to service.
• Message: SSL0135W: Initialization error, Unsupported SSL protocol or unsupported certificate type.
o Reason: Unsupported SSL protocol or unsupported certificate type.
o Solution: Check server ciphers and certificate settings.
• Message: SSL0136W: Initialization error, Invalid certificate signature.
o Reason: Invalid certificate signature.
o Solution: Check certificate in Ikeyman.
• Message: SSL0137W: Initialization error, Invalid certificate sent by partner.
o Reason: Invalid certificate sent by partner.
o 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.
o Reason: Invalid peer.
o Solution: Report problem to service.
• Message: SSL0139W: Initialization error, Permission denied.
o Reason: Permission denied.
o Solution: Report problem to service.

o Reason: If a System Authorization Facility (SAF) SSL keyring is in use, the current user ID is not authorized to read the keyring.
o Solution: See the information about access to SAF keyrings in Performing required z/OS system configurations
• Message: SSL0140W: Initialization error, The self-signed certificate is not valid.
o Reason: The self-signed certificate is not valid.
o Solution: Check the certificate in Ikeyman.
• Message: SSL0141E: Initialization error, Internal error - read failed.
o Reason: Internal error - read failed.
o Solution: Report to service.
• Message: SSL0142E: Initialization error, Internal error - write failed.
o Reason: Internal error - write failed.
o Solution: Report to service.
• Message: SSL0143I: Initialization error, Socket has been closed.
o Reason: Socket has been closed unexpectedly.
o Solution: Check the client and network. Report problem to service.
• Message: SSL0144E: Initialization error, Invalid SSLV2 Cipher Spec.
o Reason: Invalid SSLV2 cipher spec.
o Solution: Check the SSLCipherSpec directive.
• Message: SSL0145E: Initialization error, Invalid SSLV3 Cipher Spec.
o Reason: Invalid SSLV3 Cipher Spec.
o Solution: Check the SSLCipherSpec directive.
• Message: SSL0146E: Initialization error, Invalid security type.
o Reason: Invalid security type.
o Solution: Report to service.
• Message: SSL0147E: Initialization error, Invalid security type combination.
o Reason: Invalid security type combination.
o Solution: Report to service.
• Message: SSL0148E: Initialization error, Internal error - SSL Handle creation failure.
o Reason: Internal error - SSL handle creation failure.
o Solution: Report to service.
• Message: SSL0149E: Initialization error, Internal error - GSK initialization has failed.
o Reason: Internal error - GSK initialization has failed.
o Solution: Report to service.
• Message: SSL0150E: Initialization error, LDAP server not available.
o Reason: LDAP server not available.
o Solution: Check CRL directives.
• Message: SSL0151E: Initialization error, The specified key did not contain a private key.
o Reason: The specified key did not contain a private key.
o 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.
o Reason: A failed attempt was made to load the specified PKCS#11 shared library.
o Solution: Check SSLPKCSDriver directive and file system.
• Message: SSL0153E: Initialization error, The PKCS#11 driver failed to find the token specified by the caller.
o 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.
o Reason: A PKCS#11 token is not present for the slot.
o Solution: Verify PKCS#11 directives.
• Message: SSL0155E: Initialization error, The password/pin to access the PKCS#11 token is invalid.
o 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.
o Reason: The SSL header received was not a properly SSLV2 formatted header.
• Message: SSL0157E: Initialization error, The function call, %s, has an invalid ID.
o Reason: The function call, %s, has an invalid ID.
o Solution: Report problem to service.
• Message: SSL0158E: Initialization error, Internal error - The attribute has a negative length: %s.
o Reason: Internal error - The attribute has a negative length.
o Solution: Report problem to service.
• Message: SSL0159E: Initialization error, The enumeration value is invalid for the specified enumeration type: %s.
o Reason: The enumeration value is invalid for the specified enumeration type: %s.
o Solution: Report problem to service.
• Message: SSL0160E: Initialization error, The SID cache is invalid: %s.
o Reason: The SID cache is invalid.
o Solution: Report problem to service.
• Message: SSL0161E: Initialization error, The attribute has an invalid numeric value: %s.
o Reason: The attribute has an invalid numeric value: %s.
o Solution: Check SSL directives.
• Message: SSL0162W: Setting the LD_LIBRARY_PATH or LIBPATH for GSK failed.
o Reason: Could not update the environment for GSK libraries.
o Solution: Report problem to service.
• Message: SSL0163W: Setting the LIBPATH for GSK failed, could not append /usr/opt/ibm/gskkm/lib.
o Reason: Could not append to LD_LIBRARY_PATH or LIBPATH for GSK failed.
o Solution: Report problem to service.
• Message: SSL0164W: Error accessing Registry, RegOpenKeyEx/RegQueryValueEx returned [%d].
o Reason: Error accessing registry.
o Solution: Check GSK installation and windows registry.
• Message: SSL0165W: Storage allocation failed.
o Reason: Storage allocation failed.
o Solution: Check memory usage, report problem to service.
• Message: SSL0166E: Failure attempting to load GSK library.
o Reason: Failure while attempting to load GSK library.
o Solution: Check the GSK installation.
• Message: SSL0167E: GSK function address undefined.
o Reason: GSK function address is undefined.
o Solution: Check the GSK installation and level.
• Message: SSL0168E: SSL initialization for server: %s, port: %u failed due to a configuration error.
o Reason: Iinitialization for server: %s, port: %u failed due to a configuration error.
o Solution: Check the SSL configuration.
• Message: SSL0169E: Keyfile does not exist: %s.
o Reason: Keyfile does not exist.
o 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.
o Reason: Keyfile is not specified.
o 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.
o Reason: CRL cannot be specified as an option for the SSLClientAuth directive on HPUX because IBM HTTP Server does not support CRL on HPUX.
o Solution: Remove CRL directives.
• Message: SSL0172E: If CRL is turned on, you must specify an LDAP hostname for the SSLCRLHostname directive.
o Reason: If CRL is turned on, you must specify an LDAP hostname for the SSLCRLHostname directive.
o Solution: Specify SSLCRLHostname.
• Message: SSL0173E: Failure obtaining supported cipher specs from the GSK library.
o Reason: Failure obtaining supported cipher specs from the GSK library.
o Solution: Check the GSK installation, report problem to service.
• Message: SSL0174I: No CRL password found in the stash file: %s.
o Reason: No CRL password is found in the stash file: %s.
o Solution: Check the stash file permissions, regenerate stash file.
• Message: SSL0174I: No CRYPTO password found in the stash file: %s.
o Reason: No CRYPTO password is found in the stash file: %s.
o Solution: Check stash file permissions, regenerate stash file.
• Message: SSL0175E: fopen failed for stash file: %s.
o Reason: fopen failed for stash file.
o Solution: Check stash file permissions, regenerate stash file.
• Message: SSL0176E: fread failed for the stash file: %s.
o Reason: fread failed for the stash file.
o 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.
o Reason: Unknown return code from stash_recover(), %d.
o Solution: Check the stash file.
• Message: SSL0181E: Unable to fork for startup of session ID cache.
o Reason: Unable to fork for startup of session ID cache.
o Solution: Check the location of sidd daemon, file permissions.
• Message: SSL0182E: Error creating file mapped memory for SSL passwords.
o Reason: Error creating file mapped memory for SSL passwords.
o Solution: Report problem to service.
• Message: SSL0183E: Exceeded map memory limits.
o Reason: Exceeded map memory limits.
o Solution: Report problem to service.
• Message: SSL0184E: Could not find a password for the resource: %s.
o Reason: SSL0184E: Could not find a password for the resource: %s.
o Solution: Report problem to service, disable password prompting.
• Message: SSL0185E: ssl_getpwd() failed, unable to obtain memory.
o Reason: ssl_getpwd() failed, unable to obtain memory.
o Solution: Report problem to service, disable password prompting.
• Message: SSL0186E: Linked list mismatch.
o Reason: SSL0186E: Linked list mismatch.
o Solution: Report problem to service, disable password prompting.
• Message: SSL0186E: ssl_getpwd() failed, password exceeded maximum size of 4095.
o Reason: ssl_getpwd() failed, password exceeded the maximum size of 4095.
o 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.
o Reason: It is invalid to enable password prompting for the SSLServerCert directive without specifying a crypto card token.
o Solution: Specify a crypto card token or disable password prompting for the SSLServerCert directive.
• Message: SSL0188E: SSL initialization for server: %s, port: %u failed. SSL timeouts cannot be set in a virtualhost when the SSLCacheDisable directive has not been specified globally.
o Reason: When the SSL session cache is being used, only the global timeout settings apply because they are managed by the external session cache daemon. See information about the SSLCacheDisable and SSLCacheEnable directives in the information center topic entitled SSL directives.
o Solution: If separate SSL timeouts are required, disable use of the session ID cache (SSLCacheDisable), otherwise make sure the SSLV3Timeout and SSLV2Timeout directives are only set in the global scope.
SSL stash utility messages
This topic contains error messages that might result due to Secure Sockets Layer (SSL) stash utility problems and provides solutions to help you troubleshoot these problems.
The following messages appear due to SSL Stash utility errors:
• Message: SSL0700S: Invalid function
o Reason: An invalid parameter was entered. The valid values are crl or crypto.
o Solution: Rerun the command with the proper function.
• Message: SSL0701S: The password was not entered.
o Reason: The password was not entered on the command line.
o Solution: Rerun the command with the password added.
• Message: SSL0702S: Password exceeds the allowed length of 512.
o Reason: The password that was entered is longer than the allowed maximum of 512 characters.
o Solution: Use a shorter password.

IBM HTTP Server basic administration of server

This topic describes how to start and stop the IBM® HTTP Server administration server on distributed platforms.

null


For this task

Start the IBM HTTP Server administration server as follows. You must be logged in as a root user, or If you installed as non root user for IHS then you must SU - to same user which is owned by IHS.
If it is Windows then you should be administrator.

Procedure
Windows :

From the Start menu

Click Start > Programs > IBM HTTP Server > Start Administration Server.
A message box displays that indicates the server has started.

If the IBM HTTP Server administration server does not start, complete the following steps:
1.Open the Control Panel.
2.Click Services.
3.Double-click IBM HTTP Server Administration Server to start the server.
Confirm that IBM HTTP Server administration server started successfully by checking the admin_error.log file for a "start successful" message. If you use the developer installation option, then the IBM HTTP Server administration server does not install as a service. You have to run the httpd.exe file from a command line with the -f option. From the default directory, type:
httpd -f conf\admin.conf




ALL UNIX (AIX, HP-UX, Linux, Solaris):

The adminctl command starts and stops the IBM HTTP Server administration server. You can find the adminctl command in the bin subdirectory, within the IBM HTTP Server installation directory. If that directory is not in your PATH, the full path should be given on the command line. Start or stop the IBM HTTP Server administration server using the default admin.conf configuration file as follows:

null

1.Run the adminctl start command to start the server or run the adminctl stop command to stop the server.

Issue the commands from the default directories, based on your operating system:

AIX : /usr/IBM/HTTPServer/bin/adminctl start|stop

HP-UX, Linux, Solaris : /opt/IBM/HTTPServer/bin/adminctl start|stop

null


For example, The adminctl command is not in your PATH, the IBM HTTP Server installation directory is /usr/IBM/HTTPServer, and the default configuration file is used as follows:

/usr/IBM/HTTPServer/bin/adminctl start
/usr/IBM/HTTPServer/bin/adminctl stop

Important: The admin.conf configuration file supports single-byte characters (SBCS) only.
2.Confirm that IBM HTTP Server administration server started successfully by checking the admin_error.log.

Note: Some times IBM HTTP server process will be found Hung (defunct process) in UNIX environments resulting server will not respond or function even though server’s status is running.

Possible Cause’s: More child process for single instance / reached the maximum open files limit / more memory or CPU usage / reached the maximum user limit..Etc..!

Resolution: How to kill in the above situation.

Kill – (Process ID) , Kill -9 (Process ID) for force fully kill.

If you want to number of defunct process or chilled process which is causing problem.

for i in `ps -ef|grep master Process id of http server|grep -v grep |awk '{print $2}'`; do echo $i;kill -9 $i; done