Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Ping stops working on the Orion Polling Engine

Ping stops working on the Orion Polling Engine

Updated May 3, 2018


When Orion Services are running, PING stops or hangs.When services stop, the PING service resumes and works again. When this issue occurs, the assigned node statuses are stale at the last polled status. 


  • NPM 12.2 HF3
  • Orion 2017.3 HF 5


The JobEngineV2 service fills up due to permissions or A/V in the environment, which prevents jobs from processing correctly. As a result, the Microsoft Windows TCP sharing service stops PING when enough stress is placed on the system.


  1. Click Start > All Programs > SolarWinds Orion > Advanced Features > Orion Services Manager.
  2. Stop all SolarWinds services.
  3. Navigate to the JobEnginev2 folder.

    If you are running Microsoft Windows Server 2008, the default location is:


    If you are running Windows Server 2003, the default location is:

    C:\Documents and Settings\All Users\Application Data\SolarWinds\JobEngine.v2\Data\

  4. Rename the JobEngine35.sdf - blank file.
    1. Copy and paste JobEngine35 - Blank.sdf  into your current folder, creating the following file:
      JobEngine35 - Blank - Copy.sdf.

    2. Rename JobEngine35 - Blank - Copy.sdf to JobEngine35.sdf.
  5. Right-click JobEngine35.sdf and select Properties.

  6. De-select the Read-only option, and save the file.

  7. Return to the Orion Services Manager.

  8. Start all SolarWinds services. 
    Ping should start working again.

  9. Check your antivirus software and the permission checker to identify which is causing JobEngineV2 to fill up. 



Last modified