Running a DQM (Dynamic Query Mode) report or testing a database connection, the following error is returned:
XQE-CON-0007 XQE error encountered: DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit.
Creating a DQM report, the following error is returned:
XQE error encountered: DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit.
Running or creating a DQM dashboard, the following error is returned:
The metadata for '<Model Name>' did not load. Please contact your administrator for details.
The cogaudit.log contains a log entry with the following strings:
IBM Cognos Analytics 11.1.7 IF8 (11.1.7-2201050500)
IBM Cognos Analytics 11.2.1 IF3 (11.2.1-2201060400)
Verify the version of your installation by opening the <Cognos Install>/cmplst.txt file and looking at the kit_version=<version> entry. The number after the dash (-) in the version represents the date-time when the kit was created. For example, 2201052300 is Year:2022 Month:01 Day:05 Hour:23 Minute:00.
If upgrading to an IBM Cognos version (GA, FP or IF) older than the ones listed, refer to the security bulletin in the next section. You need to revisit the "no-upgrade" option in the bulletin to ensure the installation is properly protected.
Resolving The Problem
In the <Cognos Install>/configuration/xqe.config.custom.xml file search for log4jSafeAgent2021.jar.
If the search finds the file name, remove the argument shown here from the list of options.
While the log4j mitigation steps required the bootstrap_wlp_os_version.xml file also be modified, this file resets back to its default state during the upgrade and does not need to be edited to resolve this issue.
Backing files before modification is recommended.
The change needs to be performed on all application servers.
Was this topic helpful?
24 January 2022