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
Quote from: kvca11 on 09 Nov 2018 11:00:39 AM
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.
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
Quote from: kvca11 on 11 Nov 2018 01:16:24 AM
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.
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
Quote from: kvca11 on 13 Nov 2018 04:43:55 AM
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.