Network Management

Network Discovery fails in NPM with the error Could not save discovery profile

This article addresses an error message that NPM displays when you run a network discovery. Error: Could not save discovery profile.

First published date

10/9/2018 7:29 PM

Last published date

2/26/2025 3:42 AM

Overview

When you run Network Discovery, the following error is displayed:

Could not save discovery profile: JobSchedulerException: PolicyExists: 
Could not reach job engine v2 service. 
net.pipe://localhost/solarwinds/jobengine/router after 3 retries. Please fix the error and try this action again.

Product section

Network Performance Monitor

Cause

Could not reach the Job Engine Service. 

Resolution

  1. Check the job engine service. If the job engine service is not running, restart it.
  2. Re-run Network Discovery. 
If this does not help, follow steps in How to run a repair on SolarWinds Orion Core Services