nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
- SolarWinds Academy
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

Configwizard issue

zap123

I have upgraded solarwinds to 2026.2 but due to snmp devices going into critical we decided to roll back to old version.

Now my db is on 2026.2 but application is on old versions. It is impacting few features.l and config wizard is not completing successfully.

any suggestions?

thanks in advance!

Find more posts tagged with

sam

solarwindsorion database

orion

npm

ncm

Accepted answers

All comments

naveensingh43

Did you take DB backup before upgrade?

naveensingh43

if yes try restoring DB server first.

vinay.by

Hi @zap123

1. Ideally it should work, but then its best to raise a vendor support case for this.

2. I am not sure from which version did you upgrade to 2026.2 and even if there any changes on the database be it schema tables etc SolarWinds support engineers will help you with the queries that can fix them if you want to revert back to previous version.

3. Worst case scenario is if you can't fix it with the above approach, follow what @naveensingh43 has mentioned in his response - that's the only alternative way to fix it. Restore your DB if that as well doesn't work then Restore both your VM's + DB for a known data - try to use the backup for same date if possible (if you have backups for VM's and DB for the same date use it - this would be the best approach, if you dont its ok)

vinay.by

Hi @zap123

What is the error that you see on config wizard? Can you please paste that here. Did you as well check the logs that config wizard

cnorborg

Maybe upgrade to 2026.2.2? It's out now and supposed to fix those issues…

zap123

yes we restored the db 1st and even powered on the db server 1st. Still the issue exist some on the db schema went to 2026.2 even i have raised the vendor case they are not sure why this happened. Correction db is on 2024.4 but some schema is on 2026.2. We are planning to upgrade i guess that is the last option.

bmrad

Please post the ticket number you have with support.