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

After upgrade to 2020.2 - Getting "Availability Statistics: Server error 500-Internal Server Error"

I upgraded on saturday to 2020.2 from 2018.4 - no issues.

Only I just discovered this:

On a Node Details - Summary pages:

I see
Availability Statistics
Server error: 500-Internal Server Error

The IIS log:

2020-06-16 12:53:52 10.4.0.55 POST /Orion/Services/AsyncResources.asmx/GetAvailabilityStats - 80 USERNAME 10.1.5.3 Mozilla/5.0+(Windows+NT+10.0;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/83.0.4103.97+Safari/537.36 http://solarwinds.local/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:284 500 0 0 1089 - -

Any Idea what this is and how to fix it ?

image.png

Find more posts tagged with

Accepted answers

All comments

Prineel

Have the same issue on one of our sites. Any resolution before i open a ticket?

marcv

I have this issue to. Have anyone opened a case?

-marc

jorge.dargence

Same issue here after upgrading to 2020.2. Looks like there have been no updates

aaguilar1

This is a bug tracked under NPM-15939. SolarWinds developers are working on a fix but do not yet have a time-frame. In the meantime open a case with SolarWinds support to provide a Buddy Drop

jeremc2

Me too

koushikkr

I have the same issue, will open a case with Support.

spaghettishapes

Same here, as of the weekend's upgrade

robertcbrowning

how did this manage to get through?

It's a "me too" here as well

highstone351

I upgrades to the latest and I received this error (among a lot of others, thanks DEV for checking so badly), and have logged this as an additional problem with the upgrade path.

I have not gotten a reply as well.

I checked the page source code and it looks like they forgot a value setting that is proper.

MHH

fakeusername

Same issue here. I got a user complaint about it this morning. I do not see where there is a fix coming soon.

Edit: I opened a ticket, and they sent me a workaround file. I will be installing it late Thursday afternoon (you know how Change Control is), and I will let you know if it resolves the issue.

Edit 2 - Resolution. Support gave me a new dll. I put it in place on the polling engine and the web server. I did not have to stop any processes. I checked the Node Details again, and the problem was resolved. The whole resolution took about a minute, with no downtime. Nice!

equator

Looks like this was resolved in 2020.2.1

marcv

Yes - this is fixed after I went to 2020.2.1