We have a Crystal Reports XI server that I'm testing reports with. We use http links from an internal website directly to the java applet that processes and displays the report.
When I start a large report (something that might take more than 3-5 minutes to run), often the viewer will stop after 3 minutes and report "No data available". I'm assuming the viewer or something in the chain is timing out.
I tried editing the web.config file for IIS on the server extending the httpRuntime ExecutionTimeout value to 10 minutes. But what's odd is, once the viewer has "given up" waiting for data, if you press the browser refresh button, the applet will re-initialize, and the data from the report sometimes will appear.
What I'd like to know is where on the server can I lengthen the timeout value for this issue?
When I start a large report (something that might take more than 3-5 minutes to run), often the viewer will stop after 3 minutes and report "No data available". I'm assuming the viewer or something in the chain is timing out.
I tried editing the web.config file for IIS on the server extending the httpRuntime ExecutionTimeout value to 10 minutes. But what's odd is, once the viewer has "given up" waiting for data, if you press the browser refresh button, the applet will re-initialize, and the data from the report sometimes will appear.
What I'd like to know is where on the server can I lengthen the timeout value for this issue?