Last post Dec 05, 2011 03:56 AM by andrea.temporin
Dec 04, 2011 04:17 PM|andrea.temporin|LINK
we use ReportViewer 2005 sp1 inside an ASP.NET web project . Every time a client do a call which takes a long time to end, ReportViewer control hangs on the call of the methodm "Render". If eventually you close the browser on the client with the long call
you won't be able to get the report preview from any client until you stop an restart the application pool. Handler Mappings in IIS configuration seems to be correct.
thanks in advance
Dec 05, 2011 03:25 AM|bhasi83|LINK
I have few questions on this.
1) Have u designed ur report in report server project wizard.
2) Are you able to view ur project in that report server project wizard.
3) The problem that you have mentioned occurs on every report or the first time you call the report server.
Actually report server takes some time to start up for the first time, whenever a report is called through a reportviewer client it hits the report server with respective parameters. The report server takes sometime initially to start.
This overhead can be reduced by creating subscriptions on ur report server. This can be achieved by following below steps
1) Create a sample report which shows some dummy(static) data(not even database call is required).
2) Go the subscriptions tab in ur report server and create subsciption for the sample report that u just created.
3) Schedule the subscription so that the report server will be ready before anyone hits the report server.
This will start your report server and keeps it ready to accept requests.
Hope this helps.
Dec 05, 2011 03:56 AM|andrea.temporin|LINK
we are not using reporting services. We're just using ReportViewer control to get prints-print previews inside an ASP.NET site.
We create rdlc files partially by external editing and partially by VisualStudio 2008 express and then programmatically associate the datatable to the reportviewer control and then invoke the Render Method. It's the call to the render method which hangs.
The problem rises only if someone from a browser cal a page doing a slow elaboration. The method hangs until the elaboration gets and end. If the user close his browser before the elaboration ends you have to stop and restart application pool to make Render
If this is not the case, I mean no one do a request with a long elaboration, everything works correctly.