Unable to open Cognos Configuration after a change in the Java on the Cognos Server.

-

Problem(Abstract)

Unable to open Cognos Configuration after a Java change on the Cognos Server.

Symptom

Cognos Configuration was unable to successfully use the cryptographic information with the current Java Runtime Environment located in <location>/cognos/crn/bin/jre/1.3.1
The cryptographic information may have been corrupted or the Cognos Configuration tool is not running with the Java Runtime Environment that generated the cryptographic information: <location>/cognos/crn/bin/jre/1.3.1.Original

Cause

The Encryption keys were created against either an older version of Java or the JAVA_HOME variable was changed

Resolving the problem

Recreate the Encryption keys in crn/configuration directory and restart the services. For Cognos 8, the Encryptions keys are located in c8/configuration

Steps: 1. Stop CRN services
2. Navigate to crn/configuration
3. Backup and remove the following folders and file: encryptkeypair, signkeypair, csk, and caSerial.
4. Open Cognos Configuration.
5. Configuration maybe required to enter in missing values, such as Content Store password. Confirm all settings are entered and no required entries are missing
6. Restart services.






Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more