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

just wanna know what does it mean

Started by pooja, 21 Nov 2008 01:52:34 PM

Previous topic - Next topic

pooja

we were running a report ,,,,,and after sometime we got this error..........???
we appreciate any comments and explanation......please


RSV-BBP-0022
The absolute affinity request 'asynchWait_Request' failed, the requested session does not exist.

RSV-SRV-0042 Trace back: RSReportService.cpp(629): RSException: CCL_CAUGHT: RSReportService::process() RSReportServiceMethod.cpp(177): RSException: CCL_RETHROW: RSReportServiceMethod::process(): asynchWait_Request MethodImpl/RSWaitMethod.cpp(65): RSException: CCL_THROW: RSWaitMethod::run()


pj

pooja

adding----------

we validate all the data...and are correct......and we even run report by single customer....and that was also correct.....
but when we tried to run for whole client......the it happens..??

blom0344

#2
A quick search:


This error typically indicates a timing condition in long-running reports. Reports that run for more then 7 seconds enter an "asynchronous communication" mode. In this mode, the session sends periodic "wait()" requests to retrieve the data. If this request isn't received for over 30 seconds (the default async timeout) due to delays in the architecture, the dispatcher closes the session. This error is generated when the dispatcher then receives the "wait" request for the closed session.

Solution:

Possible environmental causes and solutions of this error:

Ensure that the minimum hardware requirements for Cognos 8 have been met.Ensure that settings for a local firewall are not interfering with Cognos 8. Either disable the local firewall, or if that is not an option, modify the firewall settings for the Cognos 8 ports.Ensure that multiple browsers (more then 2) aren't being used on the workstation, as this may interfere with the communications.



From KB:


Adjust the async_wait_timeout_ms setting in the reportservice.xml file (webapps/p2pd/WEB-INF/services).  The default setting is 30000 (30 secs).

pooja

Ohhhhhh...got it

thank you So much

very effective information


pj