Network Management

Network Discovery failing to start with Could not save discovery profile error in the Orion Platform

"Could not save discovery profile" error occurs when attempting to run a Network Discovery job.

First published date

11/8/2018 9:28 PM

Last published date

12/27/2022 11:23 PM

Overview

Network discovery fails before scanning IP addresses with this message or similar:

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

Product section

Network Performance Monitor

Cause

The cause is a problem with JobEngine v2.

Resolution

  1. Stop all services.
  2. Uninstall Collector, Information Service, Job Engine v1, and Job Engine v2 through the Control Panel Programs and Features.
  3. Install Collector, Information Service, Job Engine, and Job Engine v2 from installer packages at C:\ProgramData\Solarwinds\Installers
  4. Start all services.
  5. Create a new, small, discovery job and execute it immediately to ensure it runs and completes successfully.
For the Full Article, please check "Repair a failing Job Engine, Collector, and Information Service in the Orion Platform".

Note: The full article has the instructions for the SolarWinds Platform 2022.2 and above to repair the SolarWinds Job Engine and the SolarWinds Collector services by deleting the .db and .db-journal files as needed.