Hi,
I am in the process of installing Cognos8 but I've run into a problem. I followed the installation and configuration manual and I'm at the final steps of the installation – Cognos Configuration.
I entered all required data fields and saving the configuration generates no errors. When starting up the service, I only get the error that the mail service is not configured correctly (indicated as normal by the manual). When I click continue, I receive checkmarks for all the following steps but in the section "details" an error occurs: "DPR-DPR-1035 Dispatcher detected an error"
Below you can find a piece of the pogo logfile:
2012-03-19 13:55:30.589 INFO [ogo.contentmanager.coordinator.CMBootstrap] Thread-20: Dispatcher was successfully registered in Content Manager.
2012-03-19 13:55:36.125 FATAL [m.cognos.pogo.reportservice.ProcessManager] warpmta-ProcessManager-ProcessMgrThread: External Report Server process BIBusTKServerMain cannot be started java.lang.NullPointerException
at com.cognos.pogo.reportservice.ReportServerProcess.start(ReportServerProcess.java:143) at com.cognos.pogo.reportservice.ProcessFacade.createServerProcess(ProcessFacade.java:232)
at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:122)
at com.cognos.pogo.reportservice.RSComponentFactory.newProcessFacade(RSComponentFactory.java:70)
at com.cognos.pogo.reportservice.ProcessManager.createProcessFacade(ProcessManager.java:497)
at com.cognos.pogo.reportservice.ProcessManager.startProcess(ProcessManager.java:476) at com.cognos.pogo.reportservice.ProcessManager.run(ProcessManager.java:332)
2012-03-19 13:55:36.133 FATAL [m.cognos.pogo.reportservice.ProcessManager] metadataServiceHandler-MDSRVProcessManager-ProcessMgrThread: External Report Server process BmtMDProviderMain cannot be started java.lang.NullPointerException
at com.cognos.pogo.reportservice.ReportServerProcess.start(ReportServerProcess.java:143)
at com.cognos.metadataService.bibusHandler.mdprovider.MDProviderProcess.start(MDProviderProcess.java:58)
at com.cognos.pogo.reportservice.ProcessFacade.createServerProcess(ProcessFacade.java:232)
at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:122)
at com.cognos.metadataService.bibusHandler.mdprovider.MDProviderProcessFacade.<init>(MDProviderProcessFacade.java:61)
at com.cognos.metadataService.bibusHandler.mdprovider.MDProviderComponentFactory.newProcessFacade(MDProviderComponentFactory.java:52)
at com.cognos.pogo.reportservice.ProcessManager.createProcessFacade(ProcessManager.java:497)
at com.cognos.pogo.reportservice.ProcessManager.startProcess(ProcessManager.java:476)
at com.cognos.pogo.reportservice.ProcessManager.run(ProcessManager.java:332)
at com.cognos.metadataService.bibusHandler.mdprovider.MDProviderProcessManager.run(MDProviderProcessManager.java:67)
I think that in spite this the service is running because when I browse to UiNode.be.ibm.com:9300/p2pd/servlet and p2pd/servlet/dispatch, I get the results as described in the manual. However, when I go to http://UiNode.swg.be.ibm.com:80/cognos8/cgi-bin/cognos.cgi, I receive the error: "Premature end of script headers: cognos.cgi" .
Could someone help me with this problem? We are running Cognos8 on a VM based on Linux (sles). All the installation and configuration steps have been done remotely via mRemote.
If you require more information or other and/or complete logfiles, don't hesitate to ask me.
Thanks in advance!
Greetings,
Tom Cuypers
Turn off DEP. Follow steps here:
http://www-01.ibm.com/support/docview.wss?uid=swg21339361
If that doesn't get rid of the DPR error yet your services still start and the portal is up and running you can ignore the error.
Thank you for your quick reply. I am configuring this in Linux (Suse) though and this seems to be for windows.
Ah. Missed the linux part, and that is for windows.
Are you running with SELinux on? If yes turn it off temporarily and see if that helps get rid of it. If not then as mentioned, check that your portal is up and you can acces it wthout error. If you can ignor the error message. There was a bug in 8.4 that they were supposed to fix in regards to that error. It's a "False positive".
I am running GNU and it seems like SELinux is not installed on this distribution. At least, I cannot find a dir etc/selinux. Nor do the commands sestatus or echo 1 >/selinux/enabled work, I even receive the command not found error.
I figured it could be AppArmour, but I check it's status under YaST > System > System Services > Expert Mode and it's disabled.
Am I missing something or do you have any other ideas?