CCL-CFG-0007 Error

[gbez]

Hi,

We have had Cognos 8.4 installed in a production environment for the past two years. Two days ago we had issues logging into the portal. After some research, we found that we needed to recreate the keystores in the environment. We have managed to do that successfully on all machines bar one - the content manager. We have a distributed installation with a gateway server, a content manager (which also happens to have planning installed on it), and two report servers. After we have recreated the keystores on the content manager and try start up the cognos service, we receive the following error:

CCL-CFG-0007 The cryptographic encryption did not initialize.
The cryptographic configuration may be incorrect or missing some security components. {0}

This is the procedure that we followed to recreate the keystores:
http://www-01.ibm.com/support/docview.wss?uid=swg21340413

We have the same architecture in our development environment except that we have only one report server, and we managed to follow the procedure successfully on all machines including the content manager, which also has planning installed on it.

Any help would be appreciated if anybody has any information on how to fix this issue.

Thanks in advance.

[Grim]

The Content Manager (CM) is where you want to start to recreate teh crypto keys. Reason being is that all other components will get their keys from the CM.

Try these instructions:
http://www-01.ibm.com/support/docview.wss?uid=swg21427302

Start with the Primary CM. Move to App tiers. End with the GW.

PS. Dispatchers, App tier, Report server...whatever you want to call it (I call it App tier) will need at least 1 CM started to get keys. If you have a separate gw only install, it will require at least 1 app tier started to get keys.

[gbez]

Hi,

We have tried following these steps, but still get the same error. The first server we perform the steps on is the content manager, and this is the machine giving the problem.

Please see screenshot attached.

[Grim]

Instead of starting the services, just click save to generate the crypto keys on the CM. Make sure you are deleting all the following:
<cognos>/configuration
Files...
caSerial
cogconfig.prefs
cogstartup.xml
Folders...
csk
encryptkeypair
signkeypair

and if you want to be really thorough the <cognos>/temp/cam/freshness file can be deleted as well.

I'd also check to make sure the "bouncy Castle" file is in place. From the docs...

Copy the bcprov-jdknn-nnn.jar file from the c8_location/bin/jre/version/lib/ext directory to the Java_location/lib/ext directory.

[gbez]

We have actually just managed to sort it out, by setting the system clock on the content manager to a future date, after the date that was specified in the old keystores that were about to expire.

After the keystores were created, set the date back and started the services without any issues.

Thanks for your assistance, much appreciated.

[Grim]

System clock....interesting. I think I saw that in one of the Technotes.

Yup...here it is...
http://www-01.ibm.com/support/docview.wss?uid=swg21344755