Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Job Scheduler service running on additonal polling engines

Job Scheduler service running on additonal polling engines

Table of contents

Updated November 9, 2016


The Job Scheduler service is not running on all additional pollers.

Likely scenarios:

  • Two environments with one main and three additional pollers.
  • The Job Scheduler is running on two of the additional pollers, one in each on two separate Orion environments and is not running on the third. 
  • It has been suggested that this is a known issue resulting from a repair of the job engine.
  • Disabled the Job Scheduler via services on the APs and both environments appear to be polling as normal.



All Orion platforms


  • JobEngine installer contains 2 components: JobEngine and JobScheduler.
  • The Orion installer always install proper components based on target engine (main, additional). 
  • If the JobEngine installer is manually run from %ProgramData%\SolarWinds\Installers\, you can choose which component to install (this is by design and is for debugging purposes). 

Is this an issue?

  • No. It does not have an impact on any functionality.
  • The Job Scheduler is a passive service which waits until a job is submitted.. Because nobody knows that scheduler service exists on additional poller, nobody tries to talk to it. So, the Job Scheduler service is an orphan and it works in idle mode. 


No further action is required. In case you want to get rid of the scheduler component, do the following steps:

  1. Run the installer from c:\ProgramData\Solarwinds\Installers\JobEngine.msi.
  2. Choose the Change option.
  3. Select Job Engine Scheduler and switch it to Entire feature will be unavailable.
  4. Finish the installation.


Last modified