IE 7 Scripting Error while running reports or queries with select and search prompt in Cognos 8.4

ERROR DESCRIPTION
----------------------------------
Because some scripts may take an excessive amount of time to run, Internet Explorer prompts the user to decide whether they would like to continue running the slow script. Some tests and benchmarks may use scripts that take a long time to run and may want to increase the amount of time before the message box appears. In Internet Explorer, the script time-out value can be changed on specific client machines by modifying a registry entry.

DESCRIPTION
----------------------------
There are situations when a Web page contains script that takes an unusually long time to run. If you are scripting an ActiveX control on a Web page to transfer a very large file or do a large database query, this will often cause a significantly long delay. Internet Explorer 3.02 detects the long delay and prompts the user with a dialog box reading the following:

This page contains a script which is taking an unusually long time to finish. To end this script now, click Cancel.

ERROR MESSAGE
-------------------
The equivalent message box for Internet Explorer versions 4.0, 5.0, 6, and 7 reads:


A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script?"
This mechanism allows the user to stop misbehaved script that runs into an endless loop or otherwise is performing slowly.

In Internet Explorer 3.02, this message box can appear on machines running Windows 95. The version 3.02 browser is specifically looking to see if the script thread has pumped any windows messages in the last five seconds. There is no way to override this time-out period for Internet Explorer 3.02. If you are using an ActiveX control with long blocking operations, that ActiveX control should either employ an event mechanism and return control to the caller or call PeekMessage every five seconds to reset the time-out.

As of Internet Explorer 4.0 and later versions, the time-out is no longer a fixed value based on Windows messages. Internet Explorer now tracks the total number of executed script statements and resets the value each time that a new script execution is started, such as from a timeout or from an event handler, for the current page with the script engine. Internet Explorer displays a "long-running script" dialog box when that value is over a threshold amount. Internet Explorer doesn’t check on each instruction to see if it is over the limit. Periodically the script engine polls Internet Explorer with the number of statements executed and Internet Explorer checks if that is over the limit. Because of this mechanism, it is possible to execute more than the default limit without the dialog if the entire script execution finishes before the script engine polls Internet Explorer.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows


To change this time-out value in Internet Explorer 4.0, 5.0, 6, or 7, follow these steps:
Using a Registry Editor such as Regedt32.exe, open this key:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles

Note If the Styles key is not present, create a new key that is called Styles.
Create a new DWORD value called "MaxScriptStatements" under this key and set the value to the desired number of script statements. If you are unsure of what value you need to set this to, you can set it to a DWORD value of 0xFFFFFFFF to completely avoid the dialog.
By default the key doesn't exist. If the key has not been added, the default threshold limit for the time-out dialog box is 5,000,000 statements for Internet Explorer 4 and later.

Because the Internet Explorer 4.0, 5.0, 6, and 7 time-out is based on the number of script statements executed, the time-out dialog box will not display during ActiveX control or database-access delays. Endless loops in script will still be detected.

--------------------------------------------------------------------------------

APPLIES TO
Windows 7 Enterprise
Windows 7 Enterprise N
Windows 7 Home Basic
Windows 7 Home Premium
Windows 7 Home Premium N
Windows 7 Professional
Windows 7 Professional N
Windows 7 Starter
Windows 7 Starter N
Windows 7 Ultimate
Windows 7 Ultimate N
Windows Internet Explorer 8
Microsoft Internet Explorer 3.0
Microsoft Internet Explorer 3.01
Microsoft Internet Explorer 3.02
Microsoft Internet Explorer 4.0 128-Bit Edition
Microsoft Internet Explorer 5.0
Microsoft Internet Explorer 5.5
Microsoft Internet Information Services 6.0
Windows Internet Explorer 7

RSV-SRV-0042

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

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 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.

Resolving the problem

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.

More Details
WinInet limits the number of simultaneous connections that it makes to a single HTTP server. If you exceed this limit, the requests block until one of the current connections has completed. This is by design and is in agreement with the HTTP specification and industry standards.



WinInet limits connections to a single HTTP 1.0 server to four simultaneous connections. Connections to a single HTTP 1.1 server are limited to two simultaneous connections. The HTTP 1.1 specification (RFC2616) mandates the two-connection limit. The four-connection limit for HTTP 1.0 is a self-imposed restriction that coincides with the standard that is used by a number of popular Web browsers.

The only evidence of this limitation to your application is that calls such as HttpSendRequest and InternetOpenURL appear to take longer to complete because they wait for previous connections to be freed up before their requests are sent.

You can configure WinInet to exceed this limit by creating and setting the following registry entries:

Note By changing these settings, you cause WinInet to go against the HTTP protocol specification recommendation. You should only do this if absolutely necessary and then you should avoid doing standard Web browsing while these settings are in effect:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

MaxConnectionsPerServer REG_DWORD (Default 2)
Sets the number of simultaneous requests to a single HTTP 1.1 Server

MaxConnectionsPer1_0Server REG_DWORD (Default 4)
Sets the number of simultaneous requests to a single HTTP 1.0 Server

These settings are made for a particular user and will have no affect on other users who log on to the computer.

In Internet Explorer 5, it is possible to change the connection limit programmatically by calling the InternetSetOption function on NULL handle with the following flags (note that it will change connection limit for the whole process):

INTERNET_OPTION_MAX_CONNS_PER_SERVER INTERNET_OPTION_MAX_CONNS_PER_1_0_SERVER

Note If the process has established a connection to a server, if you change the connection limit by calling InternetSetOption, the function does not have any effect to subsequent connections on the same server. This occurs even if a previous connection is disconnected prior to the call to InternetSetOption. Connection limit does affect all other servers.

APPLIES TO

• Microsoft Internet Explorer (Programming) 6.0
• Microsoft Internet Explorer 5.5
• Microsoft Internet Explorer 5.0
• Microsoft Internet Explorer 4.01 Service Pack 2
• Microsoft Internet Explorer 4.0 128-Bit Edition

RQP-DEF-0371

Error RQP-DEF-0371 Operation unsupported in forward only cursor mode was used.

Cause

The query property "Execution Optimization" was set to "All Rows".

Environment

OS: Windows Server 2003 Database: Oracle Product Version: 8.1

Resolving the problem

Set the Execution Optimization to Default. Open the report in Reprot Studio. Go to the query explorer. Select the first query and under the properties pane set the Execution Optimization to Default. Run the report. If the problem persists, you may need to try setting this property for your other queries defined.