javax.net.ssl.SSLHandshakeException (Indicates a certificate mismatch or missing truststore).
If you are an IBM Cognos Analytics administrator or report developer, encountering the error message can be both frustrating and critical. This error, often accompanied by a stack trace, indicates that the Query Service (XQE) within Cognos is unable to establish a Java Database Connectivity (JDBC) connection to the target database.
| Symptom | Likely Fix | |---------|-------------| | Connection refused | DB not running, wrong port, or firewall block | | Authentication failed | Wrong user/password or user lacks remote privilege | | No suitable driver | Missing JDBC driver JAR | | Timeout | Network latency, DB overload, or incorrect host | | SSL required | Append ?useSSL=true&requireSSL=true or disable SSL if allowed | | Symptom | Likely Fix | |---------|-------------| |
Ensure your connection strings use the actual IP address or Fully Qualified Domain Name (FQDN) of the database server, never localhost .
If you are using a specialized connection type (like a Cognos data module), try creating a simple, generic JDBC connection directly to the database to see if the issue is specific to the data source configuration or systemic. here’s what’s usually behind the error:
Clean environment: Do not maintain multiple versions of the same vendor's JDBC .jar driver in this folder. Doing so causes class-loader collisions, which randomizes connection success rates. Step 4: Execute an Isolated Connection Test
listen_addresses = '*' (then restart)
When Cognos routes user identities to a database backend using Single Sign-On (SSO), Kerberos, or Trusted Contexts, security token failures will trigger connection aborts.
If the user interface does not reveal the underlying failure, inspect the raw event logs. Doing so causes class-loader collisions
Verify if switching the user profile to English temporarily resolves the connection issue. F. Incorrect Username or Password
Based on real-world scenarios, here’s what’s usually behind the error: