Stackoverflow when displaying large report in ReportViewer
Posted: Sat Mar 21, 2015 12:00 am
I have an ASP.NET WebForms web page that uses the StiWebViewer web control to display a Simulsoft report. This report is loaded programmatically using the following code:
We have one report that is rather large (~1,500KB, maybe 30 Data Sources, 25+ report pages in the Designer) that when we viewed through a web page is throwing a Stackoverflow Exception.
The call stack at the time of the Exception follows.
We are using Stimulsoft version 2013.1.1600.0.
Any ideas on why this is happening, or how to make it work? Is there a maximum limit on report size?
Thanks
Code: Select all
StiReport report = new StiReport();
report.Load("BigReport.mrt");
if (!Page.IsPostBack)
reportViewer.ResetCurrentPage();
reportViewer.Report = report;
We have one report that is rather large (~1,500KB, maybe 30 Data Sources, 25+ report pages in the Designer) that when we viewed through a web page is throwing a Stackoverflow Exception.
The call stack at the time of the Exception follows.
Code: Select all
cywezaga!Reports.Load_Analysis_Report.InitializeComponent22() + 0x28 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent21() + 0x104da bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent20() + 0x103fd bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent19() + 0x104db bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent18() + 0x102fe bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent17() + 0x106fe bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent16() + 0x104b0 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent15() + 0x104b7 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent14() + 0xfef9 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent13() + 0x10417 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent12() + 0x10233 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent11() + 0x1077c bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent10() + 0x105df bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent9() + 0x1053e bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent8() + 0x10516 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent7() + 0x100a2 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent6() + 0x102f2 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent5() + 0x1035a bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent4() + 0x103b5 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent3() + 0x102e1 bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent2() + 0xf9fa bytes
cywezaga!Reports.Load_Analysis_Report.InitializeComponent() + 0xfc67 bytes
cywezaga!Reports.Load_Analysis_Report.Load_Analysis_Report() + 0x25 bytes
We are using Stimulsoft version 2013.1.1600.0.
Any ideas on why this is happening, or how to make it work? Is there a maximum limit on report size?
Thanks