Look for entries like:
As reported in IBM documentation , if you are using Db2 Trusted Context, certain IBM JCC JDBC drivers (specifically version 4.33.31) may fail with the XQE-JDB-0001 error.
Open Services ( services.msc ) and locate your database service (e.g., SQL Server (MSSQLSERVER) ). Ensure it shows "Running". Look for entries like: As reported in IBM
console to run a test on the specific data source. If the Native/OLE DB connection succeeds but the JDBC connection fails, the issue is isolated to the Java-based query engine. Examine XQE Logs
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. console to run a test on the specific data source
Analyze the lines immediately following the code indicator. Look for distinct nested Java exceptions such as:
Navigate to > Data Server Connections (or Cognos Administration > Data Source Connections). This link or copies made by others cannot be deleted
: Using an uncertified or outdated driver. For example, IBM JCC JDBC driver version 4.33.31 has been known to cause failures with DB2 Trusted Contexts.
A typo in the connection string is a frequent cause of the xqe-jdb-0001 error. Go to your Data Source properties in Cognos (or your specific application) and check the connection string.
: A database administrator may mandate Transport Layer Security (TLS/SSL) and close clear-text ports. If your Cognos Data Server connection profile is still hardcoded to standard ports (e.g., standard port 1433 for Microsoft SQL Server or port 50000 for IBM Db2) rather than the secure SSL listening port, the network interface drops the packet.
If the port is closed, check firewalls, network ACLs, and whether the DB service is running.