If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

urgent - Cognos 1.1 reportnet service broken

Started by dfite, 14 Oct 2008 01:28:31 PM

Previous topic - Next topic

dfite

I deleted and recreated a reportnet service to change the template from SMall Configuration to Large Configuration, then saved the configuration and stopped/started the service.  When I try to launch Cognos Connection, I get an error "The Cognos BI server is not available".  The service is running, tho.  Any ideas??

dfite

More information - from my crnserver.log file.  It is now logginf these errors:

10.10.20.5:9400   3176   2008-01-26 10:59:15.375   -8   na   na         Thread-25   DISP   1265   1   Audit.Other.DISP.pogo   pogo   com.cognos.pogo.contentmanager.coordinator.ActiveCMControl      Failure   <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString></messageString></message><message><messageString>null&#13;</messageString></message><message><messageString>com.cognos.pogo.bibus.SoapFaultException&#13;</messageString></message><message><messageString>   at com.cognos.pogo.bibus.BIBusCommand.handleResponse(BIBusCommand.java:485)&#13;</messageString></message><message><messageString>   at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:246)&#13;</messageString></message><message><messageString>   at com.cognos.pogo.contentmanager.StandbyContentManagerElectionCommand.executeIfLocal(StandbyContentManagerElectionCommand.java:58)&#13;</messageString></message><message><messageString>   at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.sendElectCommand(ActiveCMControl.java:224)&#13;</messageString></message><message><messageString>   at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.access$100(ActiveCMControl.java:24)&#13;</messageString></message><message><messageString>   at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl$GetActiveCMTask.run(ActiveCMControl.java:215)&#13;</messageString></message><message><messageString>   at java.util.TimerThread.mainLoop(Unknown Source)&#13;</messageString></message><message><messageString>   at java.util.TimerThread.run(Unknown Source)&#13;</messageString></message></messages>   <trace>DPR-CMI-4007 An request to perform an active content manager election failed.</trace>

kolonell

#2
Well,

It could be that there is not sufficient RAM available. Try reducing the "Max Dispatcher Memory in MB" entry for the service. Does is start again if you set it to 768 ?

EDIT: you might want to clear out the crnserver.log and attach it after you tried again so we a a complete picture off what is happening.

dfite

Thanks, I tried reducing the memory setting as you suggested, but it didn't work.  I cleared the log file and stopped/started the service then tried cognos conenction, and the log file just has about 20 line that look like this (so perhaps the other log file error I cut/paste in my other post was unrelated):

10.10.20.5:9400   6232   2008-10-14 12:12:18.304   -8               main   LOGSV   991   1   server.Audit.IPF   StartService   LogService      Success      <parameters><item name="Port"><![CDATA[9462]]></item><item name="Mode"><![CDATA[UDP]]></item><item name="Secure"><![CDATA[FALSE]]></item></parameters>

kolonell

hmm .. looks like a port usage issue to me (a reboot of the server machine might do wonders)

Are you sure that there is nothing else in the log ? The line you attached just says the log service started successfully. eg     server.Audit.IPF   StartService   LogService.

Just search through the logfile for "StartService" to see what other services start (will be useful to try determine the actual issue or which component)

If the reboot doesn't help then try changing the "Shutdown port" entry for the newly created service to an available port. Can you also check whether the old windows service (Admin tools > services) has been removed (or set to Disabled) . if the old one is still there that might be an issue as well.

dfite

WHEW!  Thank you SO MUCH, Kolonell!  It was indeed a port issue.  I guess when you delete the reportnet service and make another one it doesn't necesarily pick the same port again, and I hadn't noticed the difference.

Thank you very much for your time!