Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.





Home > Success Center > IP Address Manager (IPAM) > IPAM scans not running

IPAM scans not running

Table of contents
Created by Interspire Import, last modified by Nanette.Neal on Apr 18, 2017

Views: 15 Votes: 5 Revisions: 18


When users view a Scan Job Status (IPAM Settings > Scan Job Status), all jobs display the following status: Status "Next Scan: ASAP", Last Discovery: {Past Date}


If you receive the above Scan Job Status, verify the following:

  • All services are running in the Servers Manager.
  • There are no reported IPAM errors in the SolarWinds.Net Event Log under the Windows Applications and Services Logs.


If these are not an issue continue to the resolution below.


Try the following resolutions to restart IPAM scanning:

  • Replace the job engine. In general, IPAM scans are stuck due to a stalled job engine. SolarWinds recommends replacing the job engine to flush the IPAM jobs out and then allow them to restart.
  • Review your subnets. If you have added an excessively large subnet, either manually or from a scope, scanning may stall.
  • Verify your zones. If IPAM is conducting a DNS zone transfer and a DNS is being monitored this can corrupt the zone. Verify all zones are correct and not corrupted.

Replace Job Engine:

  1. Stop all Orion services from Orion Service Manager.
  2. Go to C:\ProgramData\SolarWinds\JobEngineV2\Data\JobEngine35.sdf file and rename it to JobEngine35_OLD.sdf.
  3. Create a copy of C:\ProgramData\SolarWinds\JobEngineV2\Data\JobEngine35 - Blank.sdf one and rename it to JobEngine35.sdf. This way you have the old one to revert back to and you always have a blank copy in case an issue reoccurs.
  4. Right click the properties of the JobEngine35.sdfyou created and clear the read only box. Click OK.
  5. Restart all Orion Services. 

Note: If using Windows Server 2003 or older, replace C:\ProgramData\ with C:\Documents and Settings\All Users\Application Data\


This issue can also mask a separate issue with the same symptoms documented here

Last modified
15:23, 18 Apr 2017