COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Cognos Administration => Topic started by: cognoslearner1 on 05 Nov 2013 05:10:26 AM

Title: Urgent help required.
Post by: cognoslearner1 on 05 Nov 2013 05:10:26 AM
Hi All,

I am having issues with testing the dispatchers. I am getting the error :
Handler trace back: [the_dispatcher]
com.cognos.pogo.handlers.performance.PerformanceIndicationHandler [the_dispatcher]
com.cognos.pogo.handlers.logic.ChainHandler [service_lookup]
com.cognos.pogo.handlers.engine.ServiceLookupHandler [adminRequestChain]
com.cognos.pogo.handlers.logic.ChainHandler [AdminRequestHandler]
com.cognos.pogo.handlers.configurable.AdminRequestHandler

When I am testing the dispatchers.  Please let me know if you have any idea of this error.

Thanks,
Title: Re: Urgent help required.
Post by: Grim on 05 Nov 2013 08:30:11 AM
Was there an error code? xxx-err-####?

This is only part of the java stack output and is pretty useless.
Title: Re: Urgent help required.
Post by: cognoslearner1 on 06 Nov 2013 09:15:10 PM
Failure   <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>Failed to send HTTP request or read HTTP response</messageString></message></messages>   DispatcherNameParser parse failureFailed to send HTTP request or read HTTP responsecom.cognos.pogo.bibus.CommandExecutionException: Failed to send HTTP request or read HTTP response   at com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:310)   at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:203)   at com.cognos.pogo.config.DispatcherNameParser.doQuery(DispatcherNameParser.java:115)   at com.cognos.pogo.config.DispatcherNameParser.queryCM(DispatcherNameParser.java:96)   at com.cognos.pogo.config.DispatcherNameParser.getPort(DispatcherNameParser.java:64)   at com.cognos.pogo.config.AdminCommand.isSameDispatcher(AdminCommand.java:137)   at com.cognos.pogo.config.AdminCommand.execute(AdminCommand.java:67)   at com.cognos.pogo.handlers.configurable.AdminRequestHandler.invokeImpl(AdminRequestHandler.java:96)   at com.cognos.pogo.pdk.BasicHandler.invoke(BasicHandler.java:207)   at com.cognos.pogo.handlers.logic

Audit.dispatcher.caf   Request         Warning      secure error - did not find userCapabilities

DPR-SYS-6000 The product is ready to use.
xx xx xx :9910   25330   2013-11-05 09:00:15.246   +0   na   na         Thread-94   DISP   6235   1   Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices   StartService   CPS Producer Registration Service      Success      
xx xx xx :9910   25330   2013-11-05 09:02:10.800   +0               WebContainer : 4   caf   2047   2   Audit.dispatcher.caf   Request         Warning      secure error - did not find userCapabilities
xx xx xx :9910   25330   2013-11-05 09:08:46.630   +0                Thread-94   CM   6235   3   Audit.RTUsage.cms.CM.Request   Request   ContentManagerService      Warning      CM-CFG-5214 Content Manager encountered the error '' while parsing the subscription descriptor file '/WEB-INF/cm/subscriptions/updatePolicies.xml'.
x xx xx :9910   25330   2013-11-05 09:11:16.664   +0                Thread-94   CM   6235   3   Audit.RTUsage.cms.CM.Request   Request   ContentManagerService      Warning      CM-CFG-5214 Content Manager encountered the error '' while parsing the subscription descriptor file '/WEB-INF/cm/subscriptions/updatePolicies.xml'


WebContainer : 6   DISP   6235   2   Audit.Other.dispatcher.DISP.com.cognos.pogo.handlers.engine.ServiceLookupHandler   Request         Failure   <messages><message><messageString>CM-REQ-4342 An error occurred with the



DPR-DPR-1035 Dispatcher detected an error.</messageString></message></messages>   Service did not stop in timely fashion: dispatcher
xx xx xx xx:9910   1944   2013-11-05 10:36:29.985   +0   shutdown   na   na   0   main   DISP   6235   1   Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices   StopService   dispatcher      Failure   <messages><message><messageString>DPR-ERR-2070 The service dispatcher did not stop within a reasonable amount of time.</messageString></message></messages>


------------------------------------------------------------------
These were the errors found
Title: Re: Urgent help required.
Post by: Grim on 07 Nov 2013 07:27:46 AM
DPR-DPR-1035 during startup of services...is that right?

Are you on Windows? If yes, then turn of DEP. Right click "My computer" and select properties>Click advanced system settings>Select "Advanced" tab>Click settings under performance>click "Data Execution Provention" (DEP) and select "turn on DEP for essential Windows programs and services only" > Reboot. Try restarting Cognos services and see if you still get the DPR-DPR-1035 error.
Title: Re: Urgent help required.
Post by: cognoslearner1 on 07 Nov 2013 09:29:24 PM
Thanks Grim for the reply yes the error msg which I posted is correct and  our environment is on LINUX
Title: Re: Urgent help required.
Post by: Grim on 12 Nov 2013 12:59:41 PM
Quote from: cognoslearner1 on 07 Nov 2013 09:29:24 PM
Thanks Grim for the reply yes the error msg which I posted is correct and  our environment is on LINUX

What flavor and version of Linux?
What java JRE are you using?
Title: Re: Urgent help required.
Post by: cognoslearner1 on 14 Nov 2013 07:48:23 AM
we are using
os : Red Hat Enterprise Linux Server release 6.4 (Santiago)
JAVA : 1.6.0
we are using websphere as the application server.
Title: Re: Urgent help required.
Post by: Grim on 14 Nov 2013 08:24:28 AM
Ah, Websphere. What version of Websphere? Did you check that it was supported?

What version of Cognos are you running with? 10.1, 10.1.1, 10.2, 10.2.1? FPs?

Another thing I would try too is see if you get the same error starting the services from Cognos using tomcat instead of Websphere.

Might be this bug...
http://www-01.ibm.com/support/docview.wss?uid=swg1PM49296
Title: Re: Urgent help required.
Post by: cognoslearner1 on 14 Nov 2013 11:53:44 PM
We are using websphere 8.0.0.5
cognos 10.1.1, FP1,FP2
IBM IHS 8.0.0.5 as the webserver.

When I try testing the dispatcher I get the below logs generated in the cogserver.log

     20738   2013-11-15 10:51:37.570 +0      CPS                             WebContainer : 38       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:37.835 +0      CPS                             WebContainer : 38       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:37.872 +0      CPS                             WebContainer : 38       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:37.884 +0      CPS                             WebContainer : 44       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:37.849 +0      CPS                             WebContainer : 38       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:37.860 +0      CPS                             WebContainer : 38       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:51.363 +0      CPS                             WebContainer : 44       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:51.601 +0      CPS                             WebContainer : 44       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:51.546 +0                                      Thread-235      xts     6235    2       Audit.ps.xts    Info PresentationService              Success PRS-PRO-0511 A partial reinitialization of the XTS processor is required.
     20738   2013-11-15 10:51:51.563 +0      CPS                             WebContainer : 44       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:51.587 +0                                      Thread-236      xts     6235    2       Audit.ps.xts    Info PresentationService              Success PRS-PRO-0511 A partial reinitialization of the XTS processor is required.
     20738   2013-11-15 10:51:51.573 +0      CPS                             WebContainer : 44       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:51.522 +0                                      Thread-234      xts     6235    2       Audit.ps.xts    Info PresentationService              Success PRS-PRO-0511 A partial reinitialization of the XTS processor is required.
     20738   2013-11-15 10:51:51.586 +0      CPS                             WebContainer : 44       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success
     20738   2013-11-15 10:51:51.537 +0      CPS                             WebContainer : 44       CM      6235    3       Audit.RTUsage.cms.CM  QUERY   PORTLETFOLDER   /Portal/Connection/Portlets     Success

-----------------------------------------------------------------------------------

Getting thos error in cognos portal after testing the  dispatcher.
Handler trace back: [the_dispatcher]
com.cognos.pogo.handlers.performance.PerformanceIndicationHandler [the_dispatcher]
com.cognos.pogo.handlers.logic.ChainHandler [service_lookup]
com.cognos.pogo.handlers.engine.ServiceLookupHandler [adminRequestChain]
com.cognos.pogo.handlers.logic.ChainHandler [AdminRequestHandler]
com.cognos.pogo.handlers.configurable.AdminRequestHandler
Title: Re: Urgent help required.
Post by: cognoslearner1 on 14 Nov 2013 11:54:23 PM
Same issue with the tomcat ..
Title: Re: Urgent help required.
Post by: murali999 on 19 Nov 2013 07:46:40 AM
Hi,

have you changed/edited any thing in system.xml file ?
some days back i got this error , when i edited the system.xml file

if this is the case restore the original sytem.xml file from backup will resolve this issue..