Crystal Reports Runtime Memory error

[jramsell]

We recently upgraded from Crystal Reports Runtime SP27 to SP37.  We then started receiving this error.  We run a service that processes reports and has threading.  We get it randomly and pretty frequently.  We did not get this error at all previously.  We have additionally tried uninstalling and reinstalling SP27 but we now still get the same error.  Rolling back to a server that never got SP37 does not experience the problem..  Was there a major change in SP37 that would have changed files we can't roll back?  Anybody experiencing this?

System.Runtime.InteropServices.COMException (0x80041004): Not enough memory for operation.
at CrystalDecisions.ReportAppServer.Controllers.SubreportControllerClass.GetSubreport(String Name)at CrystalDecisions.CrystalReports.Engine.ReportDocument.GetSubreport(String subreportName)at CrystalDecisions.CrystalReports.Engine.Subreports..ctor(ReportDocument doc)at CrystalDecisions.CrystalReports.Engine.ReportDocument.get_Subreports()

[DonWilliams · Accepted solution]

Upgrade to SP 38, 37 has a lot of Viewer issues, see if that helps.

Error indicates it's in the Subreport Controller, I suggest debugging each subreport to see if you can narrow down what in the subreport is triggering the error.

Try removing one at a time etc. 

How many subreports do you have in the reports causing the error?

[jramsell · Accepted solution]

We currently have hundreds of different reports with anywhere from no subreports to 5 maybe? We are using the auto import feature. It is not specific to a single report file. Debugging has been difficult since it is a windows service. Most of our subreports are shared subreports though. I'll look at that. Thanks.

[DonWilliams · Accepted solution]

Possibly you could add a logging component to your current version with a reg key to enable it to capture more info, specifically the work flow of the report. Something to help determine to source of the issues. Are you opening multiple reports in sequence or using threading? Sequencial openings and not cleaning up on close or could be due to Windows reosurce timing issues or memory. Without details it's hard to say what the cause is...