Looking for a way to debug the following report failed to load error

[Former Member]

At the bottom of this posting is the web information returned when I tried to run my report:

Note this report is a proof type report with over 100 sections and 5 sub reports.

It was necessary to place each and every field in its own section because of bleeding of long growing text fields

The fact that I could not even load the report makes this very difficult to debug especially when it loads and runs fine

from within Crystal XI development program.

When I load this report and I have loaded other reports in its place by copying them and overwriting the .rpt file being loaded

So I verified the specific report is failing to load.

I know others in this forum could greatly benefit by any suggestions anyone may have to further debug this problem. Perhaps resource settings or even some way to turn on an extra level of debugging within the load report process.

(To my knowledge I could have 1000 and 1,000 fields one per section) sections with a field per section and get the report to load.

My question here is not how do I fix this problem but what things might I do to get better information as to why the report failed to load. e.g A resource problem? Any registry values I can tweak to test that theory out or is

there a way obtain more detailed information

Microsoft .NET gives a detailed exception listing but this far I have not seen anything from the report viewer itself.

Note that the report runs fine in the the Crystal

Does anyone have any ideas to help me debug this problem further??

Note the following platform under windows xp:

In my web.config file:

<compilation debug="true">

<assemblies>

<add assembly="CrystalDecisions.CrystalReports.Engine, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

<add assembly="CrystalDecisions.Web, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

<add assembly="CrystalDecisions.ReportSource, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Shared, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Enterprise.Framework, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Enterprise.InfoStore, Version=11.0.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

</assemblies>

</compilation>

Error in File C:\DOCUME_{1\userx_r\LOCALS}1\Temp\{A7BBB612-E887-4169-88B3-B243E0DB76DD}.rpt:

Invalid section.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Error in File C:\DOCUME_{1\silver_r\LOCALS}1\Temp\{A7BBB612-E887-4169-88B3-B243E0DB76DD}.rpt:

Invalid section.

Source Error:

Line 40: //ReportFilename = @"C:\tmpy\SettlementEvalx\SettlementEvaluaationTab7.rpt"; //All cases

Line 41: ReportFilename="SettlementEvaluaationTab7.rpt";

Line 42: m_ReportDoc.Load(Server.MapPath(ReportFilename));

Line 43: //m_ReportDoc.Load(ReportFilename);

Line 44: SetDBLogonForReport(connectionInfo, m_ReportDoc);

Source File: c:\tmpy\SettlementEvalx\Default.aspx.cs Line: 42

Stack Trace:

[COMException (0x80000206):

Error in File C:\DOCUME_{1\user_x\LOCALS}1\Temp\{A7BBB612-E887-4169-88B3-B243E0DB76DD}.rpt:

Invalid section.]

CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.Open(Object& DocumentPath, Int32 Options) +0

CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Open(Object& DocumentPath, Int32 Options) +64

CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened() +195

[Exception: Load report failed.]

CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened() +254

CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, OpenReportMethod openMethod, Int16 parentJob) +830

CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename) +47

_Default.ConfigureCrystalReports() in c:\tmpy\SettlementEvalx\Default.aspx.cs:42

Default.PageInit(Object sender, EventArgs e) in c:\tmpy\SettlementEvalx\Default.aspx.cs:189

System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14

System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35

System.Web.UI.Control.OnInit(EventArgs e) +99

System.Web.UI.Page.OnInit(EventArgs e) +12

System.Web.UI.Control.InitRecursive(Control namingContainer) +333

System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +378

-

---

[Former Member · Accepted solution]

I forgot to mention the error indicates

Invalid section - How do I determine the invalid section? It is referring to ? Other than to go through and eliminate each section I think is the problem - presumably a section using the a sub report that uses a source of stored procedure. I can not think of what else to do.

I was hoping someone would have some setting I could set to get more detailed information.

[former_member184995 · Accepted solution]

Make sure that you do not have more than 80 sections in one area (ie in the detail section).

[Former Member · Accepted solution]

Is there any way to increase the that section limit? Did get fixed in Version 12?

That is one really dumb limit especially considering that the fields bleed when placed in the same section.

A proof report or vertical field report should have less limitations.

This is an expensive product to be stuck with such lame limitations!!!