Author Topic: DPR-ERR-2077 Failed to forward the request because the associated external proce  (Read 150 times)

Offline kvca11

  • Full Member
  • ***
  • Join Date: Jan 2018
  • Posts: 12
  • Forum Citizenship: +0/-0
Hi All,

we are facing below error for one of the report

DPR-ERR-2077 Failed to forward the request because the associated external process with PID 10268 is unavailable, either because the process is shutting down, or this was an absolute affinity request and the requested process does not exist anymore. For more information, enable the dispatcher and the external process detailed logs, and reproduce the conditions that caused 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 [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [batchreportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warptask_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_batch_warp] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmtaChain] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmta] com.cognos.pogo.reportservice.BatchReportServerHand

please help us to solve this issue

Thanks
kvca11

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 10,411
  • Forum Citizenship: +627/-10
  • Cognos Software Muppet
Hi All,

we are facing below error for one of the report

DPR-ERR-2077 Failed to forward the request because the associated external process with PID 10268 is unavailable, either because the process is shutting down, or this was an absolute affinity request and the requested process does not exist anymore. For more information, enable the dispatcher and the external process detailed logs, and reproduce the conditions that caused 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 [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [batchreportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warptask_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_batch_warp] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmtaChain] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmta] com.cognos.pogo.reportservice.BatchReportServerHand

please help us to solve this issue

Thanks
kvca11

Hi,

Does the below Technote help?

http://www-01.ibm.com/support/docview.wss?uid=swg21615939

Cheers!

MF.
Meep!

Offline kvca11

  • Full Member
  • ***
  • Join Date: Jan 2018
  • Posts: 12
  • Forum Citizenship: +0/-0
Hi MF,

Thanks for the quick help

I followed the same but again failed with the diff error

DPR-ERR-2077 Failed to forward the request because the associated external process with PID 8768 is unavailable, either because the process is shutting down, or this was an absolute affinity request and the requested process does not exist anymore. For more information, enable the dispatcher and the external process detailed logs, and reproduce the conditions that caused 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 [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [batchreportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warptask_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_batch_warp] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmtaChain] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmta] com.cognos.pogo.reportservice.BatchReportServerHandler

Ragards,
kvca11

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 10,411
  • Forum Citizenship: +627/-10
  • Cognos Software Muppet
Hi MF,

Thanks for the quick help

I followed the same but again failed with the diff error

DPR-ERR-2077 Failed to forward the request because the associated external process with PID 8768 is unavailable, either because the process is shutting down, or this was an absolute affinity request and the requested process does not exist anymore. For more information, enable the dispatcher and the external process detailed logs, and reproduce the conditions that caused 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 [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [batchreportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warptask_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_batch_warp] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmtaChain] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmta] com.cognos.pogo.reportservice.BatchReportServerHandler

Ragards,
kvca11

Unless I'm missing something, that looks like the same error message - just with a different process ID? Can you detail the exact steps you took?

MF.
Meep!

Offline kvca11

  • Full Member
  • ***
  • Join Date: Jan 2018
  • Posts: 12
  • Forum Citizenship: +0/-0
Hi MF,

I opened the report and opened the Query explorer.

we have 4 report pages and  4 report queries .

for each query i made the processing to limited local and saved the report and ran the report.

Thanks,
kvca11

Offline Lynn

  • Statesman
  • ******
  • Join Date: Apr 2008
  • Posts: 2,657
  • Forum Citizenship: +339/-1
Hi MF,

I opened the report and opened the Query explorer.

we have 4 report pages and  4 report queries .

for each query i made the processing to limited local and saved the report and ran the report.

Thanks,
kvca11

At this point you need to do some basic troubleshooting to try and isolate the problem. Try scaling it back to just one query and one page at a time to find out if all are problematic or just one. Try evaluating the generated SQL. Try removing portions of a single problematic query to see if you can find where the problem is.

I don't think you've provided anyone with enough information to help you further so best to investigate further and then report back with additional detail.

 


       
Twittear