With each configuration wizard, the websites table creates new records for each website in the environment, but still keeping old records as well as not updating the WebsiteID column in the ReportJobs table, causing that any scheduled report fails indicating "Unable to retrieve url: https://<Websites.ServerName>:443/Orion/Report.aspx?ReportID=### using HTML type.".
To fix this I run this script once a week to make sure I keep it straight, but it will be nice to have it fixed while running the configuration wizard.
update [NetPerfMon].[dbo].[ReportJobs] set [NetPerfMon].[dbo].[ReportJobs].[WebsiteID] = (select WebsiteID from [NetPerfMon].[dbo].[Websites] where Type='primary')
update [NetPerfMon].[dbo].[Websites] set ServerName = '<ServerName.FQDN>' where Type = 'primary'
update [NetPerfMon].[dbo].[Websites] set FQDN = '<ServerName.FQDN>' where Type = 'primary'
update [NetPerfMon].[dbo].[Websites] set FQDN = '<ServerName.FQDN>' where Type = 'additional'
Yes! I have the ORION WEB SERVER ADDRESS configured in the web console settings to use ensmonitor.miamidade.gov, but keep in mind the ReportJobs table uses the WebSiteID from the Websites table. The error shows when the WebsiteID do not match in the ReportJobs table and the Websites table.
Look at this thread for reference. I still have to change the Websites table and the ReportJobs table for the websiteID. The engines
Why do I use ensmonitor.miamidade.gov?
In my case, S0144659.miamidade.gov is my AWS with a CNAME in DNS ensmonitor.miamidade.gov. By doing this, I force my users to go to my AWS using the CNAME, and in the "detail URL" variables, which I use in my alerts emails to click on it and open the view. This also allows me to move my AWS if required without asking users to use a different server name.
What version are you using? Have you ever raised this with support? If so can you share the case number? While the workaround looks good I would like to better understand this behaviour to determine if it is something we can improve.
I have 2020.2 installed with the assistance of the DAU team lead by Adrian Cook and Jeff Blank.
NPM 12.2 introduced the ORION WEB SERVER ADDRESS in the web console settings, and I have a CNAME I use for my AWS (https://ensmointor.miamidade.gov) so that fixed the "Details URL" variable using this CNAME instead of my main poller in the links I have in my alerts emails. However, my emailed reports still using the main poller because these use the websites table. Additionally, the reports fail after running ConfigWizard because is create a new record in the table not updating the ReportJobs table websiteID column with the new websiteID created every time is runs. Case # 885636 and Case #1128094 refer to this issue and it was partially fix in another NPM version fixing the EngineID information in few tables, but the Websites table still giving mt hard time.
I have many tickets and feature requests in relation to this. Here's a recap.
Feature request related to Case #1168424
ENSURE ORION DATABASE TABLES HAVE CORRECT ENGINEIDS AND WEBSITEIDS SO NPM CAN OPERATE PROPERLY
Feature request related to Case #0027884
WEBSITES TABLE USAGE WITH HA AND ADDTL WEBSERVER
My goal is to have a 99.95% up-time environment. Our network engineers rely 1000% in NPM, and having to make even MS Windows updates with outage is a pain in the butt because now they take an average of 25 minutes once it ask to restart the windows until NPM is back operational.
I had HA implemented for my main poller, but making a Solarwinds update has become a nightmare as well. Last time took me a week! because of an HA table dusts left over. Refer to Case # 00364319 and Case # 00368159.
I'm scared to death to try implementing it again without knowing if it is reliable, and I would like to also use the HA option for my AWS if any... but!
I really love this product, and will really love to make any contributions to it.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.