The request failed because the associated report service process is unavail

[koolbachi]

Hi ,

I am seeing all the comments on the this topic :

I my case alll the reports are runnung expect for few...

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 [rxBalancedRequest] com.cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler [reportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warp_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_warp] com.cognos.pogo.handlers.logic.ChainHandler [warpmta] com.cognos.pogo.reportservice.ReportServerHandler


In my case if i run in tabular View i am getting the output, but when i run it whole its giving the error.

Thanks
Gop

[koolbachi]

Hi ,

I am seeing all the comments on the this topic :

I my case alll the reports are runnung expect for few...

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 [rxBalancedRequest] com.cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler [reportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warp_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_warp] com.cognos.pogo.handlers.logic.ChainHandler [warpmta] com.cognos.pogo.reportservice.ReportServerHandler


In my case if i run in tabular View i am getting the output, but when i run it whole its giving the error.

Thanks
Gop

[goose]

Just to clarify, this error occurs everytime you run the report, while other reports run fine, or does it happen intermintently?

[lloydke]

I have seen this a lot when you have a report that has a really bad (long) query to the DBMS.  When you submit the request you lock the report engine in 'Absolute Affinity' which means it can do nothing else until it gets a response back from the database.  You do this enough and all your report processes will get used up.  Since your session (and all your previous requests) are on that server you will keep going there and not to another server in the pool.  Since that server is busy waiting there are no available processes to handle your next request, thus the message.

Look at your Cogserver.log file, this should help you narrow down which report has locked your process in absolute affinity and you can work on streamlining those queries.

Hope this helps,
Kevin

[sir_jeroen]

An extra comment:
'Absolute Affinity' means that it is necessary that the connection from which the request originated from is reused. E.g. If you Run report 1 and press the cancel button then it's mandatory that the request is cancelled for Report 1 therefore Cognos uses the Absolute Affinity connection type to Report 1.

If you run a report the type of action that you are doing determines the connection type: Low Affinity or High Affinity. If you want to know more about this look in Cognos KB.