Did this connection , or is this a brand-new setup?
Example for PostgreSQL with SSL required:
: Firewalls, load balancers, or intermediate proxies dropping connections or blocking specific database ports. This frequently triggers during security hardening phases when environments shift from standard non-encrypted communication over to Secure Sockets Layer (SSL) or Transport Layer Security (TLS) ports without updating the corresponding data server string.
: For DB2, using IBM JCC JDBC driver version 4.33.31 can cause trusted connection failures. Upgrading or ensuring driver compatibility with your specific Cognos version is recommended. Missing Drivers : Ensure the correct JAR file (e.g., sqljdbc4.jar for SQL Server) is placed in the \drivers Did this connection , or is this a brand-new setup
Double-check your database instance name, database name, and tenant structures (especially on cloud data warehouses like Snowflake, Amazon Redshift, or Google BigQuery). Step 3: Inspect the XQE Diagnostic Logs
Database server logs often contain explicit reasons for connection rejection. Common log locations:
: Never deploy updated JDBC driver classes directly to a production server environment. Always stage .jar file modifications inside a sandbox environment to check for regressions against current Cognos reporting workflows. To help find a specific solution, please let me know: : For DB2, using IBM JCC JDBC driver version 4
: In some environments, like IBM OpenPages , users with non-English locale settings may trigger this error. Changing the user's locale to English can often resolve this. SSL and Port Configuration :
An error in the connection parameters typed into Cognos Administration will trigger this failure.
Remove any duplicate or older versions of the same vendor's driver from that directory to prevent class loader conflicts. Step 3: Inspect the XQE Diagnostic Logs Database
: Ensure JAR files (e.g., sqljdbc42.jar for SQL Server) are located in the \drivers folder.
Example for PostgreSQL: