Report w/ multiple subreports returns "A required resource was unavailable"

[timothyromine]

I have a fairly simple report that contains 2 subreports. When it runs in Crystal Reports 2008 SP3, it returns "A required resource was unavailable". The CR Designer screen has several icons missing or flat out blacked out. The report ran fine in CR 10. I have tried recreating the report from scratch in CR 2008. The new report returns the same error.

The report does pull a good bit of data, but I can run reports that pull more data, use more subreports, and produce larger and more dense printouts and not have a problem.

I have tried running the report under the following configurations:

Single Machine Configs:

Windows Server 2003 R2 SP2 (32-bit) - 2GB RAM / MS SQL Server 2008 SP1 / Crystal Reports 2008 SP3

Windows Server 2003 R2 SP2 (32-bit) - 2GB RAM / MS SQL Server 2008 SP1 / Crystal Reports 2008 SP3 HF 3.2

Muliple Machine configs:

Data Server: Windows Server 2003 R2 SP2 (32-bit) - 2GB RAM / MS SQL Server 2008 SP1

Workstation : Windows XP SP3 (32-bit) - 728 MB RAM / Crystal Reports 2008 SP3 (and with HF 3.2)

Data Server: Windows Server 2008 R2 Standard (64-bit) - 32 GB RAM / MS SQL Server 2008 Standard Edition (64-bit)

Print Server: Windows Server 2008 R2 Standard (64-bit) - 32 GB RAM / Crystal Reports 2008 SP3 HF 3.2 (32-bit)

(This last config combo was tried in two different physical offices with different physical sets of hardware).

In ALL situations where CR 2008 is used, the report fails to run. I do not believe that this is a problem with RAM.

If I remove either one of the subreports, the report runs without incident.

Anyone have any suggestions as to what this is?

[Former Member]

Hey Timothy,

Did you ever get a resolution to this issue?  I am having the same issue and am pulling my hair out trying to find how it can be fixed.

Any help would be appreciated.

Tracey

[timothyromine]

Sort of, but not really.

I think what it really comes down to is a memory overrun issue.  If the main report only executes once, there is no issue since the subreports are not called multiple times.  Once a report starts running and rerunning subreports due to multiple records in the main report, memory usage starts building up.  Eventually it just maxes out.  If I had to guess, some memory may not be getting released as each iteration of a subreport closes out.  Eventually it maxes out and kills CR.  I have not seen this behavior when running the same reports from within our web app using the CR .Net runtime engines, so I have not worried about it too much.