hotfix CRNET11WIN_EN.ZIP

[Former Member]

Please help me to find the hotfix to download CRNET11WIN_EN.ZIP

Thanks

[former_member188030 · Accepted solution]

Could you please elaborate what exactly are you looking for.

The zip file seems a collection of samples apps.

Thanks,

Bhushan

[Former Member · Accepted solution]

Hi Bhushan,

Thanks for showing interest.

Here are the details:

We are using Crystal runtime for visual studio 2010

Scenario:

From the Crystal reports preview mode, if a Crystal report file (.RPT) is exported to a .txt file it popups the "Not enough memory for operation" error.

Observations:

This error is occurring only for the file formats .txt, .csv, .TTX

For the formats  .XML,.RTF, .DOC etc it's exporting perfectly

Error: Not enough memory for operation

I guess SAP CR has released a fix  to address this issue for handling Buffer Overflow Vulnerability

Please help us to get the fix

[former_member188030 · Accepted solution]

Upgrade to SP9 for CR for VS 2010.

http://scn.sap.com/docs/DOC-7824

Does this happen on development or production machine?

Could you reproduce the issue on multiple environments?

If the issue persists even after upgrading to SP9, please post the complete stack trace of the error.

Also, how did you come to know about the fix being released, could you point me to the perticular document.

- Bhushan

Senior Engineer

SAP Active Global Support

Follow us on Twitter

Got Enhancement ideas? Try the SAP Idea Place

Getting started and moving ahead with Crystal Reports .NET applications.

[Former Member · Accepted solution]

Hi,

I tried to enclose a hot fix release document from SAP "cr90mainwin_en.PDF".

Since the file upload  is not allowing for PDF,doc formats i was not succeeded to send you the document.

If you can share your mail id  i can send it to you.

Please refer the section for Patch ID: 36653953.

Here is the excerpt from the document:

ADAPT00324522  Patch ID: 36653953

Description:

Reports with saved data that contain subreports, with and without shared variables, will prompt for the data source

when exported to any record-based export format (for example: Microsoft Excel (Data Only), Text, Separated Values,

and so on). Also, when users attempt to export a successful report instance in Crystal Enterprise, an error appears: "Error

retrieving data from the server: Not enough memory for operation."

The cause of the problem is that the state of shared variables is cached before they are evaluated; the association between

the share variables and the saved data becomes lost.

New Behavior:

This problem is resolved.

So i assume this issue was existed in the old versions as well. I'm not sure how this was not handled in the later versions.

Here is a link that relates to the issue but the downloads are expired/broken.

http://www.securityfocus.com/bid/21261/solution

In the mean while i will try your suggestion.

This is happening on production environment on client machines. We are also able to reproduce this issue on all environments.

Here enclosed a screen shot of the error as well

Thank you.

[former_member188030 · Accepted solution]

The issue and the fix was for Crystal reports XI (11.0). This version is not supported anymore.

You are currently using CR for VS 2010 (13.0). Upgrade to SP9. The issue would probably get resolved.

Make sure that your application uses 13 version CR assembly references.

We have never tracked such an issue for CRVS2010.

Thanks,

Bhushan

[Former Member · Accepted solution]

Hi

We have applied SP9 on top of CR For VS 2010 (13). But the issue is still persisting

We earlier got same error with Pervasive database with CR for VS2010(13), but it got resolved when we applied SP8 . Now the issue is with SQL Server Database.

Please suggest if there anything else we can try.

Thanks

[former_member183750 · Accepted solution]

How many records are you exporting?

If you export a report that has one record, do you get the same error?

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow us on Twitter

[Former Member · Accepted solution]

Yes Ludek. We will get the same error even with a single record while exporting.

[former_member183750 · Accepted solution]

What OS are you on?

If you can duplicate the issue with a saved data report, can you attach it here? Also, paste the code used inhere. To attach the report, rename it to *.txt. Do a reply, click on the "Use advanced editor" link and attach.

- Ludek

[Former Member · Accepted solution]

Hello  Ludek,

I'm just looking for the feasibility if i can send the code and  report file to you. i 'll get back to you.

We have replicated the issue on Windows 7 Professional with SP1.

[Former Member · Accepted solution]

Basically the code written like this using crystal api

// here we are setting the CrystlDecisions.Shared.ExportOptions calss object say exOps

    try

            {

                    //calling Export function on a ReportDocument calss object say rpt;

                     //CrystalDecisions.CrystalReports.Engin.ReportDocument.Export

                rpt.Export(exOps);

                return true;

            }

            catch (Exception ex)

            {

                MessageBox.Show(viewer, ex.Message);

            }

The Export function is throwing an exception.

The Exception message is "Not Enough Memory for operation"

[former_member183750 · Accepted solution]

Try this code:

D

im crReportDocument As New CrystalDecisions.CrystalReports.Engine.ReportDocument
        Dim crExportOptions As ExportOptions
        Dim crDiskFileDestinationOptions As DiskFileDestinationOptions

        ''The path/location where the exported file will be saved
        Dim exportFilePath As String = Application.StartupPath + "\exported.pdf"

        crReportDocument.Load("C:\TESTS\formulas.rpt")
        ''Set the options for saving the exported file to disk
        crDiskFileDestinationOptions = New DiskFileDestinationOptions()
        crDiskFileDestinationOptions.DiskFileName = exportFilePath

        ''Set the exporting information
        crExportOptions = crReportDocument.ExportOptions
        With crExportOptions
            .DestinationOptions = crDiskFileDestinationOptions
            .ExportDestinationType = ExportDestinationType.DiskFile
            .ExportFormatType = ExportFormatType.PortableDocFormat
        End With

        ''Export the report
        crReportDocument.Export()

        ''Display a message letting the user know the export is complete
        MessageBox.Show("Report exported to: '" & exportFilePath & "'")

- Ludek

[Former Member · Accepted solution]

Hi Ludek

i've coded like the same way, pls have a look at this

is there anything missing here from your suggested code

private bool ExportToDisk(ExportFormat format, ExportFormatOptions formatOptions, string fileName)

        {

            DiskFileDestinationOptions destOptions = ExportOptions.CreateDiskFileDestinationOptions();

            destOptions.DiskFileName = fileName;           

            ExportOptions exportOptions = new ExportOptions();

            exportOptions.ExportDestinationType = ExportDestinationType.DiskFile;

            exportOptions.ExportDestinationOptions = destOptions;

            exportOptions.ExportFormatOptions = formatOptions;

            exportOptions.ExportFormatType = format.Type;

            try

            {

                report.Export(exportOptions);

                report.Export();

                return true;

            }

            catch (Exception ex)

            {

                MessageBox.Show(viewer, ex.Message);

            }

            return false;

        }

-Thanks

Andrews

[Former Member · Accepted solution]

We have also noticed that if we remove some of the sub reports from the main report the memory consumption going down and the error is not coming up. Some times the memory consumption is going up to 1 GB on the task manager for that process. I've tried with your code ..it's also giving the same exception error. I'm not sure but the export function is  failing due to exhausted memory, it could be a memory handling issue with crystal runtime.... any thoughts please share

[former_member183750 · Accepted solution]

Hi Gallen

I'll want to get more details on this:

"if we remove some of the sub reports from the main report the memory consumption going down and the error is not coming up"

How many subreports? What section of the main report are these subreports in? Check the database connectivity and make sure it is the same as for the main report. E.g.; if main rpt = ODBC, then all subreports = ODBC.

What database are you connecting to?

- Ludek