Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > NPM Scheduled report export to PDF shows login page

NPM Scheduled report export to PDF shows login page

Updated April 22, 2017


A scheduled report exported to pdf shows the login page for the Solarwinds Orion Web Console. 


From the Core.BusinessLayer.log located at C:\ProgramData\Solarwinds\Logs\Orion:

INFO  SolarWinds.Orion.Security.ProcessRunner - (null)  stdout: Input file does not exist --url http://ORIONWEB1:80/Orion/Report.asp...e-3d8bae0b1400 --outputfile C:\ProgramData\SolarWinds\Orion\4wkfgc2o.ivz or does not user as argument
Try read settings explicitly from command line args.


  • NPM 12.0
  • NPM 12.0.1
  • NPM 12.1


Possible causes include:

  • Environment (group policy vs using local system account for services)
  • A bug with 3rd party component we use


Workaround 1: Change the Orion module engine to an administrator account

  1. Open Services.
  2. Right-click on SolarWinds Orion Module Engine.
  3. Select properties.
  4. Select the Log On tab. 
  5. Select This Account.
  6. Provide credentials for Built-in Local Administrator account, click OK.
  7. Restart the Orion services.

Workaround 2: Clear C:\Windows\temp

  1. Open C:\Windows\Temp.
  2. Remove all files older than 1 month.
  3. Restart Orion services.

Workaround 3:  Use another 3rd party component

Install another 3rd party component for generating pdfs and use it instead of the default component:

This component has an issue where the a table row is split between multiple pages, even when page-break-inside: avoid is used.

  1. Download wkhtmltopdf ( and install to any folder, such as the default Program Files folder on the C drive.
    When referencing the default installation location, you must reference the EXE file in /bin (C:\Program Files\wkhtmltopdf\bin\).
  2. Execute following sql script against the Orion database in SQL Management Studio:

    UPDATE [dbo].[WebSettings]

    SET SettingValue= 'C:\Program Files\wkhtmltopdf\bin\wkhtmltopdf.exe'

    where SettingName = 'PdfExport_PrimaryEnginePath'


    UPDATE [dbo].[WebSettings]

    SET SettingValue= '--margin-bottom 0 --margin-left 0 --margin-right 0 --margin-top 0 --no-stop-slow-scripts --javascript-delay 120000 ${URL} ${PDFFileNamePath}'

    where SettingName = 'PdfExport_PrimaryEngineArgsPattern'

  3. (Optional) Modify Orionmaster.js.
    • Replace
      if (typeof (eopdf) === 'object') $('html').addClass('RenderPdf');
      if (window.location.href.toLowerCase().indexOf('x-sw-scheduler=true')>-1) $('html').addClass('RenderPdf');
  4. Restart the Orion services.


To revert to the original PDF converter:

1. Execute the following SQL script against the database in SQL Management Studio:

UPDATE [dbo].[WebSettings] SET SettingValue= '${OrionInstallFolder}ExportToPDFCmd.Exe' where SettingName = 'PdfExport_PrimaryEnginePath'


UPDATE [dbo].[WebSettings] SET SettingValue= '--url ${URL} --outputfile ${PDFFileNamePath}' where SettingName = 'PdfExport_PrimaryEngineArgsPattern'

Workaround 4: Bypass the login screen with DirectLink

  1. Create a new Orion account named DirectLink to bypass the login screen.
  2. Rerun the scheduled report.
  3. If you see this as a security issue, you may delete the DirectLink account and that should still work.


Permanent Solution: Upgrade - Fixed in CORE 2017.3 (NPM 12.2)

  1. Revert to the original PDF converter as per steps in Workaround 3.
  2. Upgrade to a module using CORE 2017.3

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified