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

Config Wizard Error when updating first APE from 2020.2.6 to 2023.4.2.

Im getting the following error on the first APE I'm upgrading. The main poller upgraded just fine, no issues were experienced when it created the new log and event database. When I get to the database settings for the log and event monitor, I get this error below. Any ideas? I have opened a ticket with SW and called the support line, but I am still on hold.

Find more posts tagged with

Accepted answers

bharris1

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, one of the limitations of this feature is, that when this feature is enabled, Columnstore indexes can't be created on temporary tables, hence, the error.

Disable this feature in the SQL Server. A SQL server restart is required.

So my DBA was correct. It has been disabled and I am now working through the config wizard on the first APE. I will be suggesting to support that this check be added to the upgrade tool that scans your deployment. If it was in that tool, I would have been able to disable it before we began the upgrade.

All comments

bharris1

@jreves Tagging for better visiblility.

bharris1

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.

bharris1

SW Support just got back with me with the following: