Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Discovery failing with error: "Could not save discovery profile"

Discovery failing with error: "Could not save discovery profile"

Created by Con Finucane, last modified by MindTouch on Jun 23, 2016

Views: 1,646 Votes: 0 Revisions: 6

Overview

 

When running a network discovery, the following error occurs.

Environment

  • NPM 11.5.2

Cause 

Could not reach the job engine as stated.

 

Resolution

  1. Check the job engine service.
  2. If the job engine service is not running, restart it.
  3. Rerun the discovery.

 

 

 

Last modified

Tags

Classifications

Public