Crystal Reports causing memory problems for Visual Studio 2008

[Former Member]

Iu2019ve been having some issues with running out of memory when compiling Crystal reports. The error is: u201CUnexpected error writing metadata to fileu2026 'Not enough storage is available to complete this operation.'u201D

My solution is broken up into different projects, with all of the Crystals reports in their own project. It is this particular project that is causing the complier to error out. I only have about 30 reports in the in the Crystal Reports project and I also have plenty of memory on my computeru2026not even using all of it.

Iu2019m using Visual Studio 2008 with the bundled Crystal Reports 10.

I can compile if I restart Visual Studiou2026but itu2019s such a waste of time to have to restart VS several times a day. Any ideas about how to fix this?

[Former Member · Accepted solution]

Hi,

First of all lets make sure that it's this module and Crystal that is causing this; How does a new application using crystal, not dependent on any other modules behave?

Try with a simple application with a simple report, you can even use samples available under Samples directory.

Let the crystal report prompt for parameters etc. Does it behave the same?

Also complexity in report would slow down the performance like using formulas, subreports etc. I think we need to simplify the report first step by step so that we know where we are moving out of track.

Does that help?

Thanks,

AG.

[Former Member · Accepted solution]

I'm not having issues until I get a lot of reports. Please keep in mind that this is happening at compile time only...it works fine at run time.

Also, I do have all of the reports in their own project...and it only has the basic Crystal and .Net data references.

I'm not sure why you are asking about parameters as it is not a run-time issue.

All of the reports are quite basic...basic sorting, no subreports, basic grouping, basic running total calculations. It seems to be related to the number of reports...I have about 30 reports...if I make simple changes (such as adding a simple text object) to 2 or 3 reports, then Visual Studio runs out of address space to compile the project...note: I have tried ripping out the Crystal Reports...and the rest of the solution has no issues with compiling.

[Former Member · Accepted solution]

Also, when I looked up this error for Visual Studio, Microsoft stated that this error happens when a project is too large...the recommendation is to break the solution into smaller projects...the thing is that I am already doing this...it just seems rather odd to me that a project that contains only 30 crystal reports is too large to compile.