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

Unable to upgrade Solarwinds Orion platform from v2020.4 into v2022.4 - Orion Website FAILED?

Hi Folks,

I am unable to perform the inline upgrade of my Solarwinds platform to the latest version v2022.4 using the Offline installer method:

I have initiated the SolarWinds.Installer.exe as Administrator, and then stopped all of the services, but it is always stuck in the above process.

Another attempt has not been successful despite all services being up and running.

This is just a single now main polling engine with the SQL Server 2019 instance on the same VM.

How can I proceed with the upgrade process?

Find more posts tagged with

Accepted answers

adam.beedell

The fix is probably "Delete the website, then redo" (upon which it's recalled from the DB bar certificates and custom stuff.

That said ask support

That said I had this same problem, and probably there's a better way for this installer to proceed - having a website is normal after all.

All comments

Seashore

You should probably call support for this one.

C:\ProgramData\SolarWinds\Logs\Orion\ConfigurationWizard.log might give you some more insights, but Support is suggested. You payed for it so use it :-)

adam.beedell

The fix is probably "Delete the website, then redo" (upon which it's recalled from the DB bar certificates and custom stuff.

That said ask support

That said I had this same problem, and probably there's a better way for this installer to proceed - having a website is normal after all.

itengineer

Yes, you are correct :-)

itengineer

Yes, @adam, this is correct, that was the support suggestion.