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
Store

Ensure Orion database tables have correct EngineIDs and WebsiteIDs so NPM can operate properly

Please automate this process on link: For NPM to work properly, ensure Orion database EngineIDs and WebsiteIDs are correct for the following tables

Find more posts tagged with

Status: None

Comments

rodolfomanrique

An example for this is, the ReportJobs table which WebsiteID column value should be validated every time the configWizard runs because a new record is added to the websites table, and the WebsiteID value increase by one. Scheduled reports jobs use this WebsiteID value in the ReportJobs table, but the following error is been recorded in the CoreBusinessLayer.log file if the WebsiteID does not exists.

2017-02-27 15:23:46,805 [21] ERROR SolarWinds.Orion.Core.BusinessLayer.ReportJobInitializer - (null) Errors in ReportJob-29(Weekly - Core Network Availability) @ Engine 0 & Website 38
Invalid URL /Orion/Report.aspx?ReportID=537

In this case, primary website WebsiteID was 44, but the value in the ReportJobs table was using an old value (38)

Either the Configuration wizard should keep the Websites table intact, or it should look for every table and update the WebsiteID/EngineID with the new value generated.

abdulraheemsidz

This is very very important, even in case of making website as SSL (https) enabled, we faced issue and had to manually update these tables to get proper URLs in email alerts.

SolarWinds should consider the impact on these important tables.