If you implemented the log4j no-upgrade fix you will need to check this.
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.
-javaagent:../webapps/p2pd/WEB-INF/lib/log4jSafeAgent2021.jar
Restart Cognos.
An official tech note is coming soon but this is the short answer regarding the "fix".
(For anyone else reading this your situation may be different. If, for any reason, you are
not moving to a version that contains the resolution to the log4j vulnerability (like 11.2.1 GA or IF1 etc) you will need to re-evaluate the no-upgrade mitigation on the security bulletin.)
------------------------------
TREVOR COMEAU
------------------------------
Original Message:
Sent: Sun January 23, 2022 09:32 AM
From: jonathan chesterton
Subject: 11.2.1 fix pack 3 - DPR-ERR-2002 problems after upgrade
Hi ,
We've just upgraded our dev environment 11.2.1 to fix pack 3. Sadly its introduced an issue for us where we now see the following message when trying to load packages in the studios.
"DPR-ERR-2002 Unable to execute the request because there was no process available within the configured time limit"
Within the Cogaudit.log on start up I can also see that the query service is reports an error as it starts. Ive tried a fresh run of the installation over the top but still get the same issue. Anyone else have the same problem or an idea as to where I can look?
I've seen some old documentation that points at recreating the crypto keys so may look at that unless anyone has any other suggestions/recommendations.
Thanks
------------------------------
jonathan chesterton
NHS Supply Chain
------------------------------
#CognosAnalyticswithWatson