Network Management
Blank PDF report in the schedule report email after upgrading to SolarWinds Platform 2024.1, 2024.2, 2024.4, 2025.1 and 2025.2
After upgrading to SolarWinds Platform versions 2024.1, 2024.2, 2024.4, 2025.1, or 2025.2, scheduled report emails may contain blank PDF attachments. This issue prevents users from viewing report data in the attached PDF files.
First published date
Last published date
Overview
After upgrading to SolarWinds Platform versions 2024.1, 2024.2, 2024.4, 2025.1, or 2025.2, scheduled report emails may contain blank PDF attachments. This issue prevents users from viewing report data in the attached PDF files.
Symptoms
- Scheduled report emails include a blank PDF file with no report data.
- No specific error messages when generating the PDF file in the
OrionWebPdf.logfile - The following message may appear in the
Core.BusinessLayer.logfile (C:\ProgramData\SolarWinds\Logs\Orion):
INFO SolarWinds.Orion.Security.ProcessRunner - (null) stdout: Input file does not exist --url https://xxx.com:443/Orion/Report.aspx?ReportID=245&X-SW-Scheduler=true&InlineRendering=TRUE&Printable=true&SkipExportData=true&LoginNonce=874c1ff6-91cf-486f-aaf1-eacd18250b0 --outputfile C:\ProgramData\SolarWinds\Orion\d1jctklg.kry or does not user as argument Try read settings explicitly from command line args. SUCCESS:C:\ProgramData\SolarWinds\Orion\d1jctklg.kry:Title:OrionExportProduct section
Cause
Resolution
To workaround this issue, perform the following steps below:
- On the SolarWinds web console, navigate to Settings > All Settings > Manage SMTP Servers.
- Select and edit the SMTP server.
- Under MailBee, there is a drop-down option for Extended SMTP options, select No Chunking
- Click Save
- Run the report schedule to verify that the issue is resolved.
Additional Recommendations
- If the issue persists after disabling chunking, try switching the SMTP client from MailBee to Native within the SMTP server settings.
- If the problem continues, please open a support ticket with SolarWinds for further assistance. The SolarWinds team is actively investigating this issue to provide a permanent fix.