on 01-08-2009 1:36 AM
We are running Crystal Reports XI an a Windows 2003 server with IIS 6.0 and when running reports that take longer then 20 minutes we get the following message" "The page server you are trying to connect to is not accessible."
I have increased every timeout I could find to 60 minutes, we have checked the IIS time out and that is not causing the issue.
Any ideas on how to resolve this would be appreciated.
Please let me know if you need any more information. There are no event log messages being generated when this occurs.
This is about to drive me nuts and it is probably something simple but I cannot find it.
Thanks
IIS defaults to 20 minute time out also.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi even I am having exactly the same problem.
Is this bug with BOE , that we cant run report more that 20 min.
Please let me know I have increase every timeout to 300 min still not working.
I have even tried changing registry values (which is not recommended, dont try this). but no use.
Experts, Please help us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would like to start by saying if a report takes more than 20 minutes to run, it should be scheduled. Even if you are scheduling it to 'run now', and viewing the instance as soon as it is done, I do not believe anyone is running a report, then staring at their screen for 20 minutes +.
If all other timeout settings have been extended, it may be the httpRuntime executionTimeout that is stopping you. This setting is global, and will keep all http sessions open for this period of time (as long as the browser is open). This results in increased resource use on your server, which is not recommended. To adjust this, edit the WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG\machine.config file, and look for the httpRuntime Attributes section. There is a value executionTimeout set in seconds. The default setting is 90 seconds. Increase this value as necessary.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the input, this is what we have the httpRunTime values set to in the <configuration><system.web>
<httpRuntime
executionTimeout="7200"
maxRequestLength="4096"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100"
enableVersionHeader="true"
/>
We are still seeing the issue occur any other ideas?
I agree they should schedule the report but the end user in this case likes to run the report and then go do something else and feels that it should "Just work".
The product\version is: BusinessObjects Enterprise XI Release 2
Viewer: DHTML
In the CMC I have set the following settings
Cache Server
Minutes Before an Idle Connection is Closed: 60
Oldest On-Demand Data Given To a Client (in minutes):: 0
Page Server:
Minutes Before an Idle Connection is Closed: 60
Minutes Before an Idle Report Job is Closed: 60
RAS server:
Oldest on-demand data given to a client (in minutes): 60
Input File Repository Server
Maximum Idle Time" 60
Input File Repository Server
Maximum Idle Time" 60
In IIS for the application pool we have disabled(unchecked) the shutdown worker Process after being idle (time in minutes)
Please let me know if you need anything else and thanks for the help.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.