Groups | Blog | Home
all groups > sql server reporting services > march 2007 >

sql server reporting services : Reports don't finish



Herman K
3/27/2007 5:16:19 PM
We are experiencing an issue that leaves us confused. We have a variety of
reports that are run by a variety of people and for the most part, they run
without any trouble. Every now and then we’ll get a report that we expect to
complete within a matter of seconds (let’s say up to 20 seconds) and it never
completes (we see ‘Report is being rendered’ and the spinning icon in Report
Manager). Eventually, we’ll see an entry in the ExecutionLog table with a
Status of rsReportTimeoutExpired or rsProcessingAborted and we’ll see column
values of 0, some very big number, and 0 for TimeDataRetreival,
TimeProcessing, and TimeRendering respectively. If we try to run the report
again, it more often then not fails again. If I try to run the stored
procedure behind the report it completes in a matter of seconds as expected.

It’s as if the report tries to get the data and some how get’s hung up or
gives up. As far as anything unique goes in our environment, we do have a
DPE and I always suspect that my work (the DPE) is at fault; however, when
this problem appears there are also a lot of other reports run in the same
time proximity, both more complex and simple that run just fine.

Are there any suggestions that someone can make that would allow me to
further pinpoint this problem?
AtulA
4/2/2007 9:42:01 PM
Hello,
Any solution for your problem. I am also facing same problem. But we do not
have DPE.

Thanks,
Atul

[quoted text, click to view]
Parameswaran Rajan
4/5/2007 7:42:04 AM
Hi Herman,

We are also facing similar problem with the reports.We are
generating reports asynchronously.The reports are getting timed out.We are
calling the reporting services from our VB.Net code through
Reportservicemanager class.We are getting a "System.Net.WebException: The
operation has timed-out." messsage in our logs.We still could not solve the
problem.
We really apperciate your help if you have solved the problem in your side.


[quoted text, click to view]
Al
4/30/2007 2:12:01 PM
I am also having the same issue.
Has anyone solved this issue?
Thanks.

[quoted text, click to view]
EMartinez
4/30/2007 8:05:16 PM
[quoted text, click to view]


You can try expanding the timeout value (individual report properties)
for the report in the Report Server (which may temporarily resolve the
problem). It sounds like the stored procedure/query needs to be tuned
for performance improvement (via the Database Engine Tuning Advisor).
Also, I would suggest being conservative w/multiple datasets in the
same report. It seems to be related to query performance in my
opinion. Hope this helps.

Regards,

Enrique Martinez
Sr. Software Consultant
AddThis Social Bookmark Button