System.OutOfMemory in a standar report 10706 - 2013R2

AlkroAlkro Member Posts: 115
There is no solution by Microsoft about this error when you run Report 10706 in a 2013R2 - Spanish localization?. All Customer has the same problem when run this report (standard, without changes) at the end of the year.
The solution is run with a "date filter" day by day? Is an anual report.

Anybody has the solution?

Answers

  • archer89archer89 Member Posts: 337
    It's often an issue with images. Check out If you could change the report. Do you print Company Logo or Do you use company paper with preprinted logo? Do you print many images in the report?
    best regards
    Franz Kalchmair, MVP
    Alias: Jonathan Archer

    please like / agree / verify my answer, if it was helpful for you. thx.
    Blog: http://moxie4nav.wordpress.com/
  • AlkroAlkro Member Posts: 115
    No logos, no images. Is the standard Report.
  • archer89archer89 Member Posts: 337
    Same result when you save the report as pdf or excel?
    best regards
    Franz Kalchmair, MVP
    Alias: Jonathan Archer

    please like / agree / verify my answer, if it was helpful for you. thx.
    Blog: http://moxie4nav.wordpress.com/
  • Wisa123Wisa123 Member Posts: 308
    Try to filter the date range down to a month or so, and watch the dataset afterwards. if its unusually big (like Way, way way more than is shown in the printed report) you may want to take a look at the layout.

    if theres a lot of aggregating going on you might wanna consider calculating values in C/AL instead of RDLC
    Austrian NAV/BC Dev
  • archer89archer89 Member Posts: 337
    edited 2016-08-03
    please checkout also following threads (especially the 2. one)
    http://forum.mibuso.com/discussion/46301/problem-with-a-report-with-many-pages
    https://blogs.msdn.microsoft.com/nav/2014/03/09/rdlc-report-and-performance-in-microsoft-dynamics-nav/

    try to reduce the printed data:
    * only show really needed columns
    * only show really needed rows (data)

    you could also try following
    create a codeunit
    write in trigger onrun
    report.savesasexcel(10706,filename) // or maybe try saveaspdf instead

    run the cu directly or use job queue
    best regards
    Franz Kalchmair, MVP
    Alias: Jonathan Archer

    please like / agree / verify my answer, if it was helpful for you. thx.
    Blog: http://moxie4nav.wordpress.com/
  • AlkroAlkro Member Posts: 115
    Thaks for replies.
    We have solved this run it on the server, but is very extrange that Microsoft don't review this, because is a standard Report.
    This report analize all G/L Entry in a period (Normally, the customer filter for a year for audit) and lot of customers has the same problem. Partners are selling a solution with a hardware requirements (RAM,Processor,OS...) and then, with a standard report fails. What can we say to the Customer, you must buy more and more memory if you want to run this Report?
  • archer89archer89 Member Posts: 337
    you could contact microsoft support.
    best regards
    Franz Kalchmair, MVP
    Alias: Jonathan Archer

    please like / agree / verify my answer, if it was helpful for you. thx.
    Blog: http://moxie4nav.wordpress.com/
  • AlkroAlkro Member Posts: 115
    edited 2016-08-11
    archer89 wrote: »
    you could contact microsoft support.

    Yes, We contacted with them and the answer was "If you want, we can optimize the Report" (If we pay, of course).
    Obviously, we don't accept to pay for this, when the report is standard and isn't an especial requirement.

    Is not a good support for the people who are selling their products.
  • DsmithDsmith Member Posts: 7
    edited 2016-08-12
    We've been dealing with this same issue with a few of our clients this week.

    I would add that another way to optimize the standard reports is to make use of the Report Label Designer and the Include Caption option on the column data data type lines.

    Your goal is to send data like column headers and general report information only once, not with every line in the dataset.

    For one of our client, they needed to print to PDF close to 1000 Sales Inv. reports at the same time. I basically removed all of the lines where the datasource ended in 'lbl' in the sales inv. line dataset and filled them in a more efficient way.

    Check out tips 1 and 2 from this post:
    https://blogs.msdn.microsoft.com/nav/2015/03/17/a-couple-of-rdlc-performance-optimization-tips/
Sign In or Register to comment.