SSL errors
The following table provides a set of SSL messages that can appear in messages
EQQIP16I, EQQPH46I, EQQX601E, showing the most common error cause in the Cause column:
| SSL message | Cause |
|---|---|
| SSL ERROR ON CONTEXT INITIALIZATION: Error in gsk_enviroment_init: 201 No key database password supplied. |
The process cannot access the password file. A common cause is a typing error in the file name or directory authorizations not properly set. |
| SSL ERROR GETTING CERTIFICATE INFORMATION: The program cannot authenticate the SSL peer certificate: the requested level is not matched. | There partners’ certificates do not match. For example, you set different SSLSTRING values for the communication partners. |
| TIMEOUT EXPIRED, WAITING FOR SSL CONNECTION. | You set different SSLLEVEL values for the communication partners. Make sure that both the communication partners specify the same value for the SSLLEVEL parameter. |
| TIMEOUT (15 SEC) EXPIRED WHILE WAITING FOR SSL HANDSHAKE FROM REMOTE AGENT. | It is issued in the message log of the controller or server started task, when you set different SSLLEVEL values for the communication partners. Make sure that both the communication partners specify the same value for the SSLLEVEL parameter. |
| SSL ERROR INITIALIZING A SECURE CONNECTION: Error in gsk_secure_socket_init: <6> : Key label is not found. | The SSL key database of the controller or server started task does not contain a default certificate. |
| SSL ERROR GETTING CERTIFICATE INFORMATION: The counterpart workstation did not present a valid SSL peer certificate, common name is missing. | It is issued in the message log of the controller or server started task, when the SSL key database of the client partner does not contain a default certificate. |
| SSL ERROR INITIALIZING A SECURE CONNECTION: Error in gsk_secure_socket_init: <420> : Socket closed by remote partner. | The message log of the communication partner is expected to show the route cause of the problem. |
| SSL ERROR ON CONTEXT INITIALIZATION: Error in gsk_enviroment_init: 408 Key database password is not correct. |
The most common cause is that the password file does not match the database password. |
| SSL ERROR ON CONTEXT INITIALIZATION: Error in gsk_enviroment_init: 202 Error detected while opening the key database. |
The process cannot access the key database. A common cause is a typing error in the database name. |