cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error: Memory full. Not enough memory for operation.

Former Member
0 Likes
1,135

Hi everyone,

I've been having intermittent memory related issues with the Crystal Reports, but only on one computer. Some of them make sense, but regarding the rest, I don't even know where to start troubleshooting. The following errors were received while trying to preview a one-page report inside the report viewer. I think the client may have tried once or twice, and these were the errors she got collectively:

  • Memory full. Not enough memory for operation.

  • Error in File temp_e8aa8005-1652-4575-882e-3908b3e396e5 {65D7CB66-BA85-A545-4E99122D7D4C}.rpt: The request could not be submitted for background processing.

  • Load report failed.

The client's computer specs are:

The application hosting the report viewer is a VB.NET 3.5 application, compiled for the x86 platform.

The software used to create the report are:

  • Visual Studio 2010 Version 10.0.30319.1

  • SAP Crystal Reports runtime engine for .NET Framework 4 (64-bit) Version 13.0.0.99

  • SAP Crystal Reports, version for Visual Studio 2010 Version 13.0.0.99

Any help would be appreciated. Let me know if you need any more information. Thanks for the help in advance.

View Entire Topic
Former Member
0 Likes
Former Member
0 Likes

Thanks for your help. I imagine this will sound silly, but unfortunately, we have been holding off SP1 because it requires the new 2011 CR runtime distributable, which requires .NET 4. We prefer to wait for .NET 4 SP1 to be released before using it in our application and requiring our users to upgrade. If upgrading the CR runtime is the only solution, that's totally okay. It'd be nice, though, to know why we've never encountered this issue with any of our other clients.

Former Member
0 Likes

This is a pretty big misconception. SP1 is simply that. A Service Pack for CRVS2010. There is no framework changes or implications of any sort...

Going to SP1 will be your 1st line of attack on this issue...

Ludek

Former Member
0 Likes

I'm sorry, I should have clarified. We've been redistributing the 2008 runtime while developing with 2011, and we've been holding off upgrading to 2011 SP1 because SP1 isn't backwards compatible with 2008.

I'll close this question as answered. Thanks for all the help!