0

Bug Report - Critical Excel Export Failures

I am observing consistent failures when attempting to Export to Excel, particularly with large datasets (e.g., ~300k cells). Notably, exporting the exact same report to PDF succeeds, which suggests the issue is specific to the Excel generation engine.  (2025.02.222 (Linux environment).

Symptoms & Errors:
The export fails almost immediately, and I am seeing the following errors in the system logs:

  1. Code Exception (NPE):
    java.lang.NullPointerException: Cannot invoke "api.models.printing.enums.ExportTitleContext.ordinal()" because "titleContext" is null
    at bl.printingEngine.PrintingEngineImplementors.ExcelSheetFactory.getSubTitle(ExcelSheetFactory.java:212)

  2. Renderer Crash:
    ... got errors All puppeteer process tabs have died

  3. Timeouts:
    On some attempts, the task simply times out (even after increasing maxTimeForProcess to 600s).

Troubleshooting attempted:
I have already tried the following tuning steps with no improvement:

  • Reduced printing parallelism in Task Services.

  • Increased printing/conversion memory limits (Max Active Server Size).

  • Increased all relevant timeouts (Printing job timeout, Query limits).

  • Restarted the Task Engine.

Please verify this on your side. This appears to be a critical bug with the Excel export functionality in the new release.

Thanks.

2 replies

null
    • VP Product Management
    • Ian_Macdonald
    • 7 days ago
    • Reported - view

    Hi 

    Please open a support ticket with our Help Desk.

    Thank you,

    Ian

    • Lead Consultant Advanced Analytics
    • Michael_Daun
    • 7 days ago
    • Reported - view

    We had similar issues especially with larger exports/prints - and we hope that in the latest release V2025.03.047 that we are going to install soon these issues are fixed. Have a look at the release notes: https://community.pyramidanalytics.com/t/h7ypgy5/pyramid-2025-03-released

    For the "titleContext" error:
    We think (i.e. we are not sure!!!) that this has something to do with the fact that the Context export settings ("None", "Light Breadcrumb", "Explicit Details" etc.) are a new feature since V2025.02. Export schedules which had been defined with an older version failed when running on V2025.02 because the Context setting has not be defined yet. After opening the schedule definition and selecting one of the Context options at least this kind of error disappeared. 

    Hope this helps
    Michael

Login to reply

Content aside

  • 7 days agoLast active
  • 2Replies
  • 32Views
  • 3 Following