herbet
  • herbet
  • 91% (Exalted)
  • Newbie Topic Starter
2 years ago
Hello

We are trying to run pretty small reports with Sage 1000 SP 8 and we keep getting:
An error has occurred when processing report 10053870_287E26F7-2DEB-4633-8F2F-FD0F84EF0737_nl_trial_balance.pdf. Please contact your administrator.

ExportReportPDF - DBName: SageUKUniqueID: 10053870ReportPath: \\evdcisdmpapsg01\Reports\287E26F7-2DEB-4633-8F2F-FD0F84EF0737_nl_trial_balance.reportOutputPath: \\evdcisdmpapsg01\Reports\Output\10053870_287E26F7-2DEB-4633-8F2F-FD0F84EF0737_nl_trial_balance.pdfOut of Memory : The report being generated is too large for the amount of memory currently available.

Surely we do not need to allocate more RAM? It is hardly using any...?

Is it the share where the files are sent? Do we need to clear it out?

 
Sponsor

Want to thank us? Use: Patreon or PayPal or Bitcoins: bc1q4whppe29dw77rm4kv4pln0gqae4yjnxly0dny0hky6yhnafukzjsyrsqhk

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.

Lemonde
  • Lemonde
  • 100% (Exalted)
  • Advanced Member
28 days ago

It sounds like Sage 1000 is hitting a memory limitation while generating the report, but the actual cause may not be a lack of system RAM. Here are some key areas to check:


1. Check Free Disk Space on the Shared Drive



  • Since the reports are being written to \\evdcisdmpapsg01\Reports\Output\, ensure that the drive has sufficient free space.

  • If the drive is full, Sage may interpret this as an "Out of Memory" error.


2. Permissions & Write Access



  • Ensure that the user running the report has full read/write access to \\evdcisdmpapsg01\Reports\ and its subdirectories.

  • Try manually creating and deleting a file in the output directory to confirm access.


3. Clear Old Report Files



  • The shared folder might be cluttered with old reports, causing storage or indexing issues.

  • Try clearing out older files from \\evdcisdmpapsg01\Reports\Output\ to see if it resolves the issue.


4. Check Sage Report Engine Memory Allocation



  • Even if your server has plenty of RAM, Sage 1000 may be limited in how much memory it can use.

  • If Sage 1000 runs in a 32-bit environment, it may be restricted to 2GB or 4GB of memory per process.

  • Try increasing the memory allocation settings within Sage if configurable.


5. Check the Report Itself



  • If the report queries a huge dataset, it might be consuming too much memory.

  • Test by running a smaller trial balance to see if the error persists.

  • If large reports are necessary, consider breaking them into smaller date ranges.


6. Restart Sage 1000 Services



  • Restarting Sage services (or the full server if possible) might clear any memory leaks or stuck processes.


7. Check Windows Event Logs



  • Look in Event Viewer → Windows Logs → Application/System for errors related to Sage or memory issues.

  • This might give clues if there's a deeper issue with the reporting engine.


8. Test with a Different Output Format



  • Try exporting the report to Excel or another format to see if the issue is specific to PDF generation.


Would you like assistance checking any of these areas further?


Refurbished Computers Berkshire 
Data Recovery Berkshire 
Similar Topics
Users browsing this topic