Page 3 of 3

Error in paging a report

Posted: Mon Jun 07, 2010 7:57 am
by MikeD
The 401 error was actually a false error. So ignore it.

I cleared out the log...and ran the test again..got the same problem, but no 401 error showed up. In fact no error showed. All that was logged was code 200 (success).


I tried setting the RenderMode, but getting the same problem.


Couple of things.

RenderMode is NOT a string. To set RenderMode I used the following line.

ReportWebViewer.RenderMode = Stimulsoft.Report.Web.StiRenderMode.UseCache;

Second...I was told earlier to set the property on the aspx page to RenderMode="AjaxWithCache"

In code I then changed it to the following line.

ReportWebViewer.RenderMode = Stimulsoft.Report.Web.StiRenderMode.AjaxWithCache;

And getting the same problem.


Another developer I work with things it's a session problem. That the view control is loosing session state.

Are you using cookies to keep track of session??

We're grasping at straws here.




Error in paging a report

Posted: Mon Jun 07, 2010 1:29 pm
by MikeD

We found the problem...And a little uncertain why.

In our web.config file were had the following lines of code.





By changing the privateBytesLimt="0" and percentagePhysicalMemoryUsedLimit="0" fixed the problem.

We were wondering why changing these would have any effect on the reports viewer. These reports we ran were well within the limits of these parameter settings.


Error in paging a report

Posted: Tue Jun 08, 2010 3:19 am
by Vladimir
Hello, Mike

We can not answer this question precisely. Most likely, these parameters affect the storing of reports in the server cache.

Thank you.

Error in paging a report

Posted: Tue Jun 08, 2010 9:59 am
by MikeD

The one question that came up yesterday..

Is that it seems that the report Viewer is expecting the cache to be there. That might be guaranteed if the viewer was in a dedicated reporting system. But in our application reports is just a very small part of the overall application. Cache can be flushed at any time in other parts of the application. There is no guarantee that the cache will be around when someone is viewing a report.

My changing those parameters we seem to have minimized the problem..but we don't have a guarantee that this problem won't come back. Our customers who buy our product have many many different configurations and uses. I guess we'll just have to wait and see.

Error in paging a report

Posted: Wed Jun 09, 2010 12:58 am
by Vladimir
Hello, Mike

To make a WebViewer worked without using the server cache, you need to realize the load report in the Page_Load event, and set the property RenderMode="Standard".

Thank you.