Report Never Renders

We are having a problem where a report never actually renders out to
the page. Just to clarify, the report itself does work, just not with
a larger recordset. For example, I can pull the report using a smaller
client and it returns 8k records. When I use a larger client with a
recordset of lets say 16k records it never actually makes it. When I
look at the log it shows the following:
TimeDataRetrieval = 271.18 secs
TimeProcessing = 17.31 secs
TimeRendering = 25.46 secs
And yes, I have resolved the milliseconds to seconds. So according to
the log, the page is rendered, but in reality it isn't. To add another
curious bit, yesterday I ran this report at roughly 3pm CST. When I
looked at the log, it showed the TimeStart as 2005-05-16 15:54:09.920.
And yes, I'm sure the server time and my system time are updated off
the same timeserver.
So now for my questions:
A) Is there some sort of caching of the data?
B) What would cause the page not to render even though the data is
there?
C) Could there be a disconnect between the ReportServer and IIS?
Possibly a timeout?
Any help would be greatly appreciated,
ScottPropwash,
Check out the report properties in Report Manager (the properties tab on the
web browser). There are caching properties there, I believe in the General
screen, that you might want to verify. Additionally, double check your data
source screen to make sure that everything looks okay there.
After hitting the properties tab above the browser, you can find the other
"tabs" to the left of the screen, below the tabs.
Hope that helps.
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)
"Propwash" wrote:
> We are having a problem where a report never actually renders out to
> the page. Just to clarify, the report itself does work, just not with
> a larger recordset. For example, I can pull the report using a smaller
> client and it returns 8k records. When I use a larger client with a
> recordset of lets say 16k records it never actually makes it. When I
> look at the log it shows the following:
> TimeDataRetrieval = 271.18 secs
> TimeProcessing = 17.31 secs
> TimeRendering = 25.46 secs
> And yes, I have resolved the milliseconds to seconds. So according to
> the log, the page is rendered, but in reality it isn't. To add another
> curious bit, yesterday I ran this report at roughly 3pm CST. When I
> looked at the log, it showed the TimeStart as 2005-05-16 15:54:09.920.
> And yes, I'm sure the server time and my system time are updated off
> the same timeserver.
> So now for my questions:
> A) Is there some sort of caching of the data?
> B) What would cause the page not to render even though the data is
> there?
> C) Could there be a disconnect between the ReportServer and IIS?
> Possibly a timeout?
> Any help would be greatly appreciated,
> Scott
>|||Propwash wrote:
> We are having a problem where a report never actually renders out to
> the page. Just to clarify, the report itself does work, just not with
> a larger recordset. For example, I can pull the report using a smaller
> client and it returns 8k records. When I use a larger client with a
> recordset of lets say 16k records it never actually makes it. When I
> look at the log it shows the following:
> TimeDataRetrieval = 271.18 secs
> TimeProcessing = 17.31 secs
> TimeRendering = 25.46 secs
> And yes, I have resolved the milliseconds to seconds. So according to
> the log, the page is rendered, but in reality it isn't. To add another
> curious bit, yesterday I ran this report at roughly 3pm CST. When I
> looked at the log, it showed the TimeStart as 2005-05-16 15:54:09.920.
> And yes, I'm sure the server time and my system time are updated off
> the same timeserver.
> So now for my questions:
> A) Is there some sort of caching of the data?
> B) What would cause the page not to render even though the data is
> there?
> C) Could there be a disconnect between the ReportServer and IIS?
> Possibly a timeout?
> Any help would be greatly appreciated,
> Scott
>
What service pack and what format. I had the same problem with Excel
files until I loaded Service Pack 2.sql