Network Management

Discovery Profile error: Could not start/store discovery job in Orion

The following error appears when Discovery Profiles fail: Could not start/store discovery job.​

First published date

10/9/2018 7:48 PM

Last published date

10/5/2021 6:12 PM

Overview

When running a Network Discovery, The following error appears when Discovery Profiles fail:  

Could not start / store discovery job.

could_not_start_store_discovery_jobs.PNG

 

Product section

Network Performance Monitor

Cause

  • A SQL database user without DBO access to the Orion database is specified in the Configuration Wizard.
  • The Orion database is not specified as the default database. 

Resolution

  1. Go to the SQL Management Studio.
  2. Navigate to Security > Logins.
  3. Select Properties for the Database User.
  4. Verify the following settings:
    • The Orion database must be specified as the default database.
    • Check the User Mapping section from the Login Properties. The user must have a Public and Database Owner (DBO) access to the Orion Database.

oriondb.PNG
Screenshots property of © 2017 Microsoft.
 
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.