Cognos Error Rsv-bbp-0022
the requested session does not exist.' with single sign-on device or anonymous authentication is enabled Single Sign On Anonymous RSV-BBP-0022 requested session does not exist report run Technote (troubleshooting) Problem(Abstract) Whene running reports or opening prompts in IBM Cognos Business Intelligence or IBM Cognos Express the user is presented with 'The absolute affinity request 'asynchWait_Request' failed, the requested session does not exist.' or it will show up in the logs Symptom For this situation you must either have: 1. A single sign-on device allowing access to Cognos without providing authentication details or 2. Anonymous authentication is enabled on the Cognos namespace in Cognos configuration and the following error will appear intermittently when being prompted for reports or running reports without prompts. As well the the cookie setting is either set incorrectly or not at all which may be invalid for the domain and path for which Cognos is accessed from This error will occur and usually will be presented to any user with permission to see error messages: 'RSV-BBP-0022 - The absolute affinity request 'asynchWait_Request' failed, the requested session does not exist.' This document does not cover other situations when this error may occur. See the below link for technote #1385378 if your issue does not have the same symptoms Cause The session may no longer exist in Cognos. Single Sign on works by authenticating the user automatically in any situation that would require authentication, for instance if the users session times out or if the cookie is lost. Environment Single Sign On or Anonymous authentication are enabled Diagnosing the problem 1. Running a AAA trace, see #1343375 which outlines that during the time of the error many user sessions are created for the user that is presented this error. The AAA trace will slow down your environment so after reproducing ensure that you remove the ipfclientconfig.xml file. 2. Removing Single Sign On or Anonymous authentication (or both) as both will mask the Basic Authentication prompt that would normal be generated in these situations. If you get a Basic Authentication prompt in this situation you will know your session has been lost. Resolving the problem 1. Open up Cognos configuration for your Content Manager installs. (replicate all changes on all active and stand by content managers) 2. Under the Actions tab, click Edit Global Configuration 3. You should be on the General tab, if not go to that tab 4. Under the Cookie heading, for both Domain and Path verify that the syntax of these entries are correct, or remove
request 'asynchWait_Request' failed, the requested session does not exist. cache cached IE link favourites favorites hyperlink URL error Technote (troubleshooting) Problem(Abstract) When trying to access a previously saved link to a report in Cognos Connection, the user receives the following error: RSV-BBP-0022 The absolute affinity request 'asynchWait_Request' failed, the requested session does not exist. DPR-ERR-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID: Symptom http://www-01.ibm.com/support/docview.wss?uid=swg21688871 A user cannot access a previously saved link to a report when using Internet Explorer. The user can access the link using a different web browser (such as Firefox), or on another machine. Cause Internet Explorer is using a cached version of the page rather than the most recent version. Environment Operating System: Windows Web Browser: Internet http://www.ibm.com/support/docview.wss?uid=swg21457081 Explorer Diagnosing the problem The link to a report may have worked previously but now is no longer working (the session has expired). Other users can access this link with no issues, or the user can access the same link using a different browser. Resolving the problem Set the browser settings to check for newer versions of stored pages on every visit to the page. Steps: 1. Open Internet Explorer 2. Go to Tools -> Internet Options... 3. In the General tab, under Temporary Internet Files, click on Settings... 4. Select 'Every visit to the Page' for Check for newer versions of stored pages, then click OK. 5. Close and re-open the browser and try accessing the link again. Document information More support for: Cognos 8 Business Intelligence Cognos Connection Software version: 8.4.1 Operating system(s): Windows Reference #: 1457081 Modified date: 2010-12-09 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
'asynchWait_Request' failed' when running Controller standard reports. Technote (troubleshooting) Problem(Abstract) User http://www-01.ibm.com/support/docview.wss?uid=swg21499710 launches Controller. User runs a standard report (also known as a "system report"). User receives error message. Typically the problem is intermittent - if the http://www.cogknowhow.com/index.php/cognos-error-base/230-rsv-bbp-0022 user runs the report later in the day (or the next morning) then the report works OK. Symptom RSV-BBP-0022 The absolute affinity request 'asynchWait_Request' cognos error failed Cause There are many different potential causes for this error message. For example: Scenario #1 - (most likely) Underpowered / virtual (VMWare/ESX) hardware being used, causing timeout issues See separate IBM Technote #1470677 for more details Scenario #2 - (very rare) Old/incompatible version of Adobe Acrobat Reader installed cognos error rsv-bbp-0022 on client device Scenario #3 - (fairly likely) Networking problems/issues See separate IBM Technote #1385378 for more details However, this IBM Technote shall specifically look at the following scenario from now on: Scenario #4 - Customer using an external 'load-balancing' network device to distribute requests to multiple gateway servers. In this scenario, the Cognos BI Report Server is incorrectly configured to use "Weighted Round Robin" (instead of the correct "Cluster Compatible"). More Information on Scenario#4 The setting " Weighted Round Robin" causes the Cognos Reporting Engine to handle multiple gateways/dispatchers itself. In other words, it will distribute requests to different gateways/dispatchers according to the Cognos BI logic. The setting " Cluster Compatible" causes the Cognos Reporting Engine to allow an external load balancing device (a network router designed to help with failover/fault-tolerance/redundancy etc.) to take over the job of distributing the requests to multiple gateways. E
BaseKnowledge ArticlesCognos LinksNew Releases and FixesLibraryRSS FeedsAbout the Author LoginRegisterForgot your Username?Forgot your password? RSV-BBP-0022 The absolute affinity request 'asynchWait_Request' failed, the requested session does not exist 230 1 2 3 4 5 (3 votes, average 3.67 out of 5) Errorcode RSV-BBP-0022Decription"The absolute affinity request '' failed"ComponentRSVReport ServerSubComponentBBPSolutionSymptom In Cognos 8: RSV-BBP-0022 The absolute affinity request 'asynchWait_Request' failed, the requested session does not exist. Details: RSV-SRV-0042 Trace back In ReportNet: RSV-SRV-0021 The server cannot find a primary request with ID XXXXXXXXX Traceback: WPBIBusMethod.cpp(176): WPEnginePluginException: CCL_CAUGHT: WPBIBusMethod::run WPWaitMethod.cpp(157): WPEnginePluginException: CCL_THROW: WPWaitMethod::getRequest Problem This field is displayed on the search results webpage seen by customers, and effects search ranking and relevance. When a report is run, an error message occurs. If the same report is run again it may run with no error message. Cause 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 is not 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) are not being used on the workstation, as this may interfere with the communications.www.cogknowhow.com Comments Please login to post comments or replies. CogKnowHow Newsletter Newsletter Please register to the site before you can sign for a list. No account yet? Register