bharris1 ✭✭✭✭✭

I agree. I thought it was odd that it was asking for a credential to save a file on the local drive. It seems it should only be required if you are pointing to a share.

SW Support just got back with me with the following: With regards to the error message, here is a workaround; This feature is not in use and is not supported in any SolarWinds Orion products. This feature was introduced in SQL 2019, and since we keep compatibility with SQL 2016 SP1, we don't use it anywhere. Additionally,…

As I am still waiting for Solarwinds support, my DBA suggested he disable this metadata mode. This mode has been enabled for a while and I find it odd it is only throwing this error on the log and management database setting screen.

@"jreves" Tagging for better visiblility.

Thanks for your info. We are planning on upgrading in January and hoping we can get on 2023.4 to get SDWAN polling. Are there any gotchas to be aware of going from 2020.2.6 to 2023.x?

We had our 2023.2 / 2023.3 upgrade postponed because of all the polling issues in 2023.2 (and maybe 2023.3). Did these polling engine issues end up getting fixed?

Did the polling issues get fixed in 2023.3? It looks like the latest post in here was from about 3 months ago.

I'm sorry, I grabbed the wrong screenshot. This is the host boot time shown on the ESX Host resource. 

How would I add a column that would include "Last Boot Time" that is getting polled via ESX polling. This might be coming from the hardware table.

Have you run into any issues with your job engine crashing per this thread? https://thwack.solarwinds.com/product-forums/network-performance-monitor-npm/f/forum/98977/anyone-else-having-job-engine-issues-affecting-polling We ended up upgrading to a service release instead of 2023.2.1 because of polling issues discussed in…

I have decided to upgrade from 2020.2.4 to 2020.2.6 so we are still in support until next May vs this November. How do I approach upgrading to the .6 Service Release vs it upgrading to 2023.2? Do I just grab the installer for 2020.2.6 and drop it on all pollers the old fashion way? I really don't want to accidentally go to…

I guess I will be waiting and staying on our 2020.2.4 environment until this is fixed.

Any updates from your rep?

I am unfamiliar with the merging - is this what you are referring to? https://thwack.solarwinds.com/product-forums/the-orion-platform/b/news/posts/the-day-of-instant-evaluations-has-arrived It looks to have started in 2022.3.

I'm so happy I found this thread yesterday and didn't go forward with the upgrade today. This sounds like a mess. If the fix for this issue isn't out by end of July we are positioning to just do a half step upgrade until the fix is out. We are currently on 2020.2.4 and am trying to decide between 2020.2.6, which seems like…

I have decided to postpone our upgrade from 2020.4.2 => 2023.2.1 until this fix goes out. We are very stable now and would hate to upgrade and have this bug bite us.

Has there been a more recent update than about 2 weeks ago mentioning 2023.3 will be coming out in July? I would imagine they would want to put out a buddydrop or hotfix to fix this before a version upgrade. This seems like a major issue that has me leaning towards waiting for 2023.3 before upgrading.

We have a 2023.2.1 upgrade scheduled for tomorrow. Is this issue occurring for all large environments?

We have an upgrade to 2023.2.1 scheduled for tomorrow and I just found this thread. Is it a given that this will happen in an environment? We have 9000+ nodes so I'd consider ours a large environment.

This is the first time I've heard that 2022.x was not stable. Is that actually true? We have an upgrade scheduled for next month, but with the 2023.x issues we are planning on going to 2022.x.

I was wondering the same thing.

How did you get past those errors messages? When I see access denied I am wondering if the old version was still running so it couldn't remove it. Did you manually stop all Solarwinds services? As far as the disks showing different statuses, have you customized the thresholds for the servers or types of disk it is?

Any updates on this? We will be performing an upgrade in a short while and want to keep up to date on any issues people are experiencing.

SAM would be the best way because there is a component specifically for this. This is how we monitor it. There might be a way to do it with a script but I have never looked into it because we have SAM.

I logged in this morning to turn this off and its gone without me doing anything. 

Yeah its blocking buttons and resources on our dashboards.

@"dilbert1234" This just appeared on our page this afternoon too. What is this? We haven't done any upgrades or installations recently.

That worked. Thanks! Is there a way to filter by the trend percentage? The report has been requested to show any servers that are trending up. RIght now I have it showing current CPU higher than 75% but that isn't exactly what I'm looking for.

Checking for any updates on these?

Will there be any updates regarding CVE-2021-4104 and if older version of log4j in SAM or DPA, which are not a part of CVE-2021-44228, are affected by 4104? nvd.nist.gov/.../CVE-2021-4104