Monday, March 19, 2012
Crystal Report Viewer on web timing out after 3 minutes
I am running CR 8.5 on the web, using IIS 6.0. The reports use stored procedures on a SQL server behind the scenes. When a report is kicked off the stored procedure begins running, and IF it completes within 3 minutes, the report viewer displays the report with no problem.
However, if the stored procedure takes longer than 3 minutes, which many longer date range reports do, the Crystal icon in the top right corner of the veiwer stops moving, and the viewer just remains blank. No error message is given. I know that the stored procedure continues to run behind the scenes, because if i hit the back button on the browser, and then forward, the icon begins moving again, and as soon as the stored procedure completes, the report returns. Sometimes i have to wait the 3 minutes, and go back and forward 3 or 4 times before the stored procedure completes and the report returns.
I have tried including a timeout request on the end of the URL calling the report, and even increasing the 'Connection Timeout' setting on the web component server, to no avail. I dont think this is the issue anyway, as the default timeout there is 20 minutes. This issue is occurring every 3 minutes.
Does anyone know of another timeout setting I should be looking for?See if this helps you
http://vyaskn.tripod.com/watch_your_timeouts.htm|||Hi I am having the same issue did you resolve this in the end?
Many thanks,
Chas|||yes i did. was a while ago and dont remember the exact steps, however, within the Crystal configuration manager on the web application server there were timeout settings which i think we just amped up to the max both the idle time & cache memory caps. worked like a charm. The only issue that still existed after that was once the cache reached that max that we set, crystal services required a manual restart, but that would normally takes weeks to happen. To alleviate that we put in a automatic cache purge to keep the cache down daily. worked like a charm, no issues since. knock on wood. :) Hope this helps
Saturday, February 25, 2012
CR-V timing belt
i have 97 honda CR-V with about 100,000 KM on it. i checked a doc on
Honda web site and it said that 60,000 miles is point to change timing
belt. compared with other Honda cars, it is pretty low. is it correct? if
yes, do you know the reason??
thanks for your help,
jji'd get it changes ASAP if i were you, i had a belt break on my old 85 civic
and it royally whacked all the rods, cost me a bunch, and it never quit ran
the same after that.
You may get a more specific response in another news group, as I think they
stopped using timing belts in SQL Server in 6.5. Though I don't know about
MySQL.
"jj" <jjcpa@.rocketmail.com> wrote in message
news:1md5u9ugrbemg$.1kiwbzt9ye2cw$.dlg@.40tude.net. ..
> Hi all,
> i have 97 honda CR-V with about 100,000 KM on it. i checked a doc on
> Honda web site and it said that 60,000 miles is point to change timing
> belt. compared with other Honda cars, it is pretty low. is it correct? if
> yes, do you know the reason??
> thanks for your help,
> jj|||LOL
--
David Portas
SQL Server MVP
--