We recently upgraded to a Windows Server 2008 and App Studio 8.1.3 from a Windows Server 2003 and Dev Studio 7.7.3.
We are now (getting page cannot be displayed) after we click on a Web report or run from App Studio if the report/browser takes around 2 minutes or longer to return to the screen.
We have very little IT support and have try find any option that state a 2 minute limitation with no luck. Any ideal what could be causing this situation.
We did not have this problem on our old setup.

Thanks
Chuck

This message has been edited. Last edited by: <Emily McAllister>,

Hi Chuck,


1) Is your App Studio working? Can you TABLE FILE any .foc from ibisamp for testing?

2) Which is your database?

3) What is your report code?

4) Try this simple code:

 
TABLE FILE YOUR_METADATA
PRINT *
IF READLIMIT EQ 10
END
 

Oops. I misunderstood that.

You will might be able to configure that at your server console, under workspace tab.

IBI has some products to help you to control that. They are resource analyzer and governor.

This message has been edited. Last edited by: Ricardo Augusto,

Thanks for the suggestion Ricardo.

We think it might be an registry setup.
We are setup as a 2 tier system web page on frontend and the database/fexs on backend.
we are now using LDAP to pass our access, not sure if that has anything to do with it. we sometime get (credentials requested) after the 2 min passed instead of the (page cannot be displayed screen) it like is drop who we was when we initiated the report/query

Found under Microsoft help screen
This article describes how to change the default HTTP keep-alive value in Microsoft Internet Explorer.

When Internet Explorer establishes a persistent HTTP connection with a Web server (by using Connection: Keep-Alive headers), Internet Explorer reuses the same TCP/IP socket that was used to receive the initial request until the socket is idle for one minute. After the connection is idle for one minute, Internet Explorer resets the connection. A new TCP/IP socket is used to receive additional requests. You may want to change the HTTP KeepAliveTimeout value in Internet Explorer.

If either the client browser (Internet Explorer) or the Web server has a lower KeepAlive value, it is the limiting factor. For example, if the client has a two-minute timeout, and the Web server has a one-minute timeout, the maximum timeout is one minute. Either the client or the server can be the limiting factor.

By default, Internet Explorer has a
KeepAliveTimeout
value of one minute and an additional limiting factor (
ServerInfoTimeout
) of two minutes. Either setting can cause Internet Explorer to reset the socket.


More information
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 How to back up and restore the registry in Windows


You may have to increase the default time-out value for persistent HTTP connections in Internet Explorer if you are using a Web program that must communicate with Internet Explorer over the same TCP/IP socket after one idle minute. To change the default time-out value for persistent HTTP connections in Internet Explorer, add a DWORD value that is named
KeepAliveTimeout
to the following registry key, and then set its value data to the time (in milliseconds) that you want Internet Explorer to wait before resetting an idle connection:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings
To do this, follow these steps: 1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following key in the registry:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings

3.On the Edit menu, point to New, and then click DWORD Value.
4.Type KeepAliveTimeout, and then press ENTER.
5.On the Edit menu, click Modify.
6.Type the appropriate time-out value (in milliseconds), and then click OK. For example, to set the time-out value to two minutes, type 120000.
7.Restart Internet Explorer.
If you set the
KeepAliveTimeout
value to less than 60,000 (one minute), you may have problems communicating with Web servers that require persistent HTTP connections. For example, you may receive a "Page cannot be displayed" error message.

If you must have a
KeepAliveTimeout
value higher than 120000 (two minutes), you must create an additional registry key and set its value equal to the
KeepAliveTimeout
value that you want. The additional registry key is
ServerInfoTimeout
. It is a DWORD with a value (in milliseconds) and in the same location as
KeepAliveTimeout
.

For example, to use a three-minute
KeepAliveTimeout
value, you must create the following registry keys:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings


KeepAliveTimeout DWORD value 180000 (in milliseconds)
ServerInfoTimeout DWORD value 180000 (in milliseconds)By default, HTTP 1.1 is enabled in Internet Explorer except when you establish an HTTP connection through a proxy server. When HTTP 1.1 is enabled, HTTP connections remain open (or persistent) by default until the connection is idle for one minute or until the value that is specified by the
KeepAliveTimeout
value in the registry is reached. You can modify HTTP 1.1 settings in Internet Explorer by using the Advanced tab in the Internet Options dialog box.

Thanks again Ricardo.

Chuck, what is happening there?

1) Do you have a report that takes more than 2 min?
2) What this report is doing?
3) Can you run it under deferred?


Ricardo.

Chuck,

Enable SET XRETRIEVAL=OFF and see your view source, try seeing errors if you get any.

1) yes, to return to the screen. report is still running in background due to it places the output into it's folder as it's suppose to. just no indication it finished due to the 2 min page timeout.
2) just grabbing a year worth of data, new hires / separation.
3) no access to run in deferred.

----------------------------------
Enable SET XRETRIEVAL=OFF and see your view source, try seeing errors if you get any
[COLOR:BLUE](no errors, output will be placed in correct folder, just no indication it finished due to the 2 min page timeout.)

but thanks for your feed back.

Chuck,

as you note above, it is either an IE setting or a web server setting. Don't forget to also check with your team that maintains your web server, because changing your registry value might now be enough. You may need to also change the keep alive setting on the web server

It seems like your bigger issue is that your query is inefficient. To check this you will need to run a trace on the SQL being generated. you can do so by adding the following code above your Table File request:

 SET TRACEOFF=ALL
 SET TRACEON=SQLDI
 SET TRACEON=SQLCALL
 SET TRACEON=SQLAGGR//CLIENT
 SET TRACEON=STMTRACE//CLIENT
 SET TRACEON=STMTRACE/2/CLIENT
 SET TRACEUSER=ON
 SET TRACESTAMP=OFF
 SET XRETRIEVAL=OFF  

Make sure that the SQL is efficient. If its not efficient. Then post your focus code so that we can help you understand what pieces of information can be translated into SQL and what can not.

As for not being able to run deferred... That doesn't sound like a good decision. That might be something you want to discuss with who ever turned that feature off. Sometimes its necessary as certain queries will always take time to run.

we found the culprit to our timeout issue. we increase the timeout limit under AppPool. IIS>>Active AppPool >>Advanced settings>>Shutdown timelimit to 600

thanks all