After applying the latest updates to Win2008 R2 server (somehow introducing IE version 10 as well) , the Cognos 8.4.1. instance no longer starts.
I experienced similar problems with customer sites over the past years and it usually was a matter of taking down the maximum memory from 768 to something like 512 Mb to solve similar issues. No luck this time.. I am developer, not an admin, so I'd appreciate all suggstions ;)
In the Win server log:
Faulting application name: cogbootstrapservice.exe, version: 8.4.6008.0, time stamp: 0x4acb65fd
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x4c0
Faulting application start time: 0x01ce57c2cd333922
Faulting application path: C:\Program Files\Cognos\C841_64\bin64\cogbootstrapservice.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 4bb8d9c0-c3b9-11e2-a888-0050569c0002
Which does not make much sense as the mentioned paths are valid..
edit:
just not the java.log error:
16 ERROR [main] - LogIPFControl::initCAMCrypto() - Cannot create CAM signing session.
CAM-CRP-1114 Unable to find the Certificate Authority self-signed certificate with alias 'ca' in the keystore 'C:/Program Files/Cognos/C841_64/configuration/signkeypair\jCAKeystore'.
at com.cognos.accman.jcam.crypto.misc.KeyStoreReader.getCACertificate(KeyStoreReader.java:590)
at com.cognos.accman.jcam.crypto.misc.Configuration.isCAKeyPairValid(Configuration.java:1442)
at com.cognos.accman.jcam.crypto.CAMFactory.initialize(CAMFactory.java:155)
at com.cognos.indications.LogIPFControl.initCAMCrypto(LogIPFControl.java:526)
at com.cognos.indications.LogIPFControl.initialize(LogIPFControl.java:147)
at com.cognos.crconfig.CRConfigFrame.initDataManager(CRConfigFrame.java:549)
at CRConfig.main(CRConfig.java:320)
according to IBM this should be about sufficient rights on cogstartup.xml file:
http://www-01.ibm.com/support/docview.wss?uid=swg21446734 (http://www-01.ibm.com/support/docview.wss?uid=swg21446734)
but these have not changed, nor are they insufficient..
Okay, silly to answer my own thread, but as it turned out we had goofed by explicitly setting a JAVA_HOME variable to use Pentaho Data Integrator on the same server (bad idea, I know).
Removing the JAVA_HOME entry and rebooting seems to be the cure. Another thing learned: asses what has been altered.
Cognos kept working untill we tried to restart services trying to spawn the wrong JAVA version..
Thanks for the useful info Ties! Glad you managed to figure it out! :)