Review the localized user profile rules within application layers like IBM OpenPages or standalone Cognos Analytics environments. If the connection fails only for specific global regional managers:
Because the error is generic, it can be triggered by several different issues. Usually, it falls into one of three buckets:
Non-English locale settings for certain users can sometimes trigger this connection failure.
Move target .jar files (e.g., db2jcc4.jar , ojdbc8.jar , mssql-jdbc.jar ) directly into the root Cognos environment driver storage path and cycle the services. 4. Best Practices for Maintenance Review the localized user profile rules within application
Force the Cognos service initialization script ( cogstartup.sh or service parameters) to run on an explicit English locale standard ( user.language=en and user.region=US ). Database side connection rejection.
PostgreSQL: jdbc:postgresql://hostname:5432/database_name MySQL: jdbc:mysql://hostname:3306/database_name?useSSL=false Oracle: jdbc:oracle:thin:@hostname:1521:ORCL SQL Server: jdbc:sqlserver://hostname:1433;databaseName=dbname
For older databases, you might need a legacy driver. Also ensure the driver class is loaded – most modern apps do this automatically, but in plain JDBC you need Class.forName("org.postgresql.Driver") . Move target
If you continue to face the issue after following this guide, consult your application’s detailed logs (e.g., xqe.log , cogserver.log , or your custom JDBC logs). Look for an underlying java.net.ConnectException or SQLException with a more specific state code—that will be the final piece of the puzzle.
Confirm that the JDBC connection string exactly matches the database's requirements, including the correct hostname, port number , and instance name. If using SSL, verify the port is correct and that the IBM Cognos Certificate Authority has the necessary database certificates.
: If the database requires SSL, but the certificate has not been properly imported into the Cognos keystore or the connection string is not using the correct SSL port, the connection will fail. Troubleshooting & Resolution Steps Database side connection rejection
If all the above pass, restart the XQE engine or the entire application server—sometimes a stale network socket table requires a full process restart.
Look for messages like "Connection attempt failed" or "SSL handshake failed" .