Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

IPAM scans not working after upgrading to NPM 10.2

After upgrading my NPM to 10.2, all my IP scans in IPAM state this error:

The scanning of 'x.x.x.x /24' started at 12/5/2011 3:35:39 PM has failed with error: 'Scan not responding (rescheduled)'.

I have rebooted, ran the configuration wizard, etc.

Find more posts tagged with

ipam

hotfi

Accepted answers

HBrandNSB

Looks like we found the issue. For those having the problem, open a case and reference my case #292499.

I had to uninstall the Job Engine 1.5.3 and replace with Job Engine 1.5.2 and that resolved the issue. Open a case and they will give you the files you need.

All comments

jawill8301

I am having this same issue after I upgraded to NCM 7.0.

Case Update: 291737 - IPAM and NCM

So far they had me run the configuration wizard again and replace 2 database job engines. So far its a no go.

ZycaR

Hi BrandNSP,

The problem can be connected with SolarWinds JobEngine service. You can check the status by OrionServiceManager. If it is not working after upgrade to NPM 10.2 please start it (and all other services which may be down).

When the job engine is running, please open up a support ticket and we can help you to fix the problem. Also, mention this thwack post in your support request.

HBrandNSB

I have case #292499 open for this. All my services are running fine.

HBrandNSB

Bump.

IPAM is useless for me right now.

HBrandNSB

Looks like we found the issue. For those having the problem, open a case and reference my case #292499.

I had to uninstall the Job Engine 1.5.3 and replace with Job Engine 1.5.2 and that resolved the issue. Open a case and they will give you the files you need.