cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to Export Memory Full CR 2016 SP 6 blob field

mercedes_green
Participant
0 Kudos

https://apps.support.sap.com/sap/support/knowledge/public/en/1439011

This offers no solution. I am not using a picture but a blob field that pulls images from SQL Server so I can't simply delete the image and insert it back. This happens on all reports that use blob fields. I do not have a memory issue on my laptop.

This issue has been around for over 10 years. Why has this not been fixed? How do we export our reports to pdf if it crashes each time?

FYI: I'm unable to find that KB they reference as I'm not able to search KBs due to this message whatever that means.

"You are signed in with a P-user ID"

Accepted Solutions (0)

Answers (5)

Answers (5)

mercedes_green
Participant
0 Kudos

I have over 250Gb of free space on my laptop. How can a simple report with 3 images on it take more than that just to simply export it? The images themselves are only 3mb each.

DellSC
Active Contributor
0 Kudos

At this point it's probably not so much a memory issue as a disk space issue. Crystal will do a lot of swapping to disk when generating large export files (and at other times as well...) using its own temp files, not the Windows virtual memory swap space. Then, when you get an error, it's not good about cleaning up after itself, so you potentially have large temp files taking up space on the drive.

The best place to look for these files is C:\Users\<user id>\AppData\Temp. Note that "AppData" is a hidden folder, so you'll probably need to set Explorer options so that you can see hidden folders. Once you get there, delete everything with a ".tmp" file extension and anything with a file name that starts with "~" and ends in ".rpt". Make sure that Crystal is closed before you do this. Afterward, I would delete files from any other temp folders you may have just so that you can free up as much space as possible. Then try the export again.

-Dell

mercedes_green
Participant
0 Kudos

I'm not sure how to tell what the binary size of the blob field is. Is that from SQL Server or from the properties on the field itself in CR? What is considered a "small" size blob image? I can't control the size of the original image as it's hosted in a SQL table, but am resizing it after I insert it on a report (4 x 6).

I'm not getting the errors associated with the KB article. The images show fine when I run the report but CR Designer crashes when I try and export.


If I upload this report into our ERP applcaition which is installed locally, it exports without any errors (it uses the CR Runtime). The issue is specifically with CR Designer.

mercedes_green
Participant
0 Kudos

So....we just can't use Blob Fields in CR without it crashing every time?

vitaly_izmaylov
Employee
Employee
0 Kudos

The blob image should work, but there are some potential problems like the size of the BLOB file:

Do you know the size of the binary data for the blob field?

Can you try a new report with a single small size Blob image ?

The image resolution also used to be a problem. See: https://apps.support.sap.com/sap/support/knowledge/public/en/1297026

vitaly_izmaylov
Employee
Employee
0 Kudos

The actual KBA 1283043 - Crystal Reports crashes when using a Oracle BLOB field was deleted by the author long time ago. We do not even see what was there. I corrected the KBA 1439011 and deleted the reference.