StackOverflow exception when creating telerik report with large designer filesize on IIS 7

[ITIS]

Hi,

I have a problem with Telerik.Reporting. When I create a report containing a lot of markup (many panels, textboxes etc.) with designer file size of about 1,2MB I get StackOverflow exception calling report object constructor in InitializeComponent() method:

private void InitializeComponent()
        { //in this line a StackOverflow exception happens
            System.ComponentModel.ComponentResourceManager resources = new System.ComponentModel.ComponentResourceManager(typeof(MyOffer));
            Telerik.Reporting.TableGroup tableGroup7 = new Telerik.Reporting.TableGroup();
            Telerik.Reporting.TableGroup tableGroup8 = new Telerik.Reporting.TableGroup();
            Telerik.Reporting.TableGroup tableGroup9 = new Telerik.Reporting.TableGroup();
            Telerik.Reporting.TableGroup tableGroup1 = new Telerik.Reporting.TableGroup();
            Telerik.Reporting.TableGroup tableGroup2 = new Telerik.Reporting.TableGroup();
            Telerik.Reporting.TableGroup tableGroup3 = new Telerik.Reporting.TableGroup();
            Telerik.Reporting.TableGroup tableGroup4 = new Telerik.Reporting.TableGroup();
            Telerik.Reporting.TableGroup tableGroup5 = new Telerik.Reporting.TableGroup();
            Telerik.Reporting.TableGroup tableGroup6 = new Telerik.Reporting.TableGroup();

Exception message:
"An unhandled exception of type 'System.StackOverflowException' occurred in MyApplication.DLL"

What is interesting it takes place before executing method's first line of code - it breaks on bracket '{'. Described situation happens when I run my application on IIS 7, the exception causes my application proccess to break and I get server error page. When running on built-in Visual Studio 2010 development server everything seems fine. I noticed that when I decreased the report designer file size (removing some elements) down below 600KB the exception is gone and everything seems fine on IIS 7. It looks like 600KB is a boundary and larger designer files cause problem.
Thanks for any support.

[Steve]

Hi Samir,

We would appreciate if you open a support ticket and attach a sample runnable project with a report that exhibits the problem, so we can test this on our end.

Looking forward to your reply.

Regards,
Steve
the Telerik team

[ITIS]

I opened a support ticket and sent you sample application. Thanks for reply.

[Sridhar Bolisetti]

I am also having the same issue. I used 1500 text boxes and 15 panels to design the report. It just need to display boxes for entering first  name and last name and middle name for each letter.

I am using 4.2.10.1221 version. Getting stack over flow exception and IIS getting stopped by this.

Could you please help on this? Please find attached design layout. Same layout should be in 3 pages. I used report header for one page. Group header for 2nd page and Group Footer for 3rd page.


Regards,

B.Sridhar

[Steve]

Hi Sridhar,

This issue is caused due to the limited stack size of IIS (250kb) while the Casini server has a stack limit of 1MB. However, in our local tests we have noticed that if we Enable 32-Bit Applications in the ASP.NET's application pool the report is rendered successfully.
Another possible solution is to use SubReport items in order to divide your report in multiple smaller reports and then unify the report in one master report.

Generally the purpose of the Telerik Reporting product is different - to serve as template for your data, not to create huge forms that would be used for filling up information by hand. The latter is handled by word processing software, so you might reconsider whether using a reporting product is the right choice for your requirement.

All the best,
Steve
the Telerik team

[Sridhar Bolisetti]

Thanks Steve,

Sorry for delayed response. I needed to display session information on the page header from database. So I created this report. I could solve this problem by adding single section in detail. Controlled number of records from the database by creating temp table for number rows and joining to main query. Then problem solved.

I think, when all the controls are created in initializecomponents method, it is exceeding iis memory size.