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

Installing Previous Version of SolarWinds Platform

I have an upgrade planned and approved for tomorrow in my production environment to 2025.4.3 (from 2025.1.1). I see that 2026.1 was just released as GA.

I have the 2025.4.3 installers downloaded but if the centralized update tool discovers 2026.1, will I still be able to use 2025.4.3? Will it stay in the update tool, or can I run the SolarWinds.Installer-2025.4.3.6011.exe that's downloaded in ProgramData\SolarWinds\Installers on my primary polling engine?

Find more posts tagged with

Accepted answers

HerrDoktor

you need to use the full ISO for your corresponding version. If you have the online-installer (around 100-200MB in size) it will pull the latest version.

All comments

HerrDoktor

you need to use the full ISO for your corresponding version. If you have the online-installer (around 100-200MB in size) it will pull the latest version.

chucksimalchik

Thanks. I looked and the staging process has downloaded a bunch of .cab, .msi, and .exe files specific to 2025.4.3, but I also pulled down and staged the full ISO just to be sure.

The new centralized update tool has been good for us the last few updates, but I suspect it'll act like the online installer and pull the most recent, which we haven't gotten approved. I always prefer a release with some time and bugfixes under its belt anyway.

u303083

chucksimalchik same boat! I had planned to go to 2025.4.3 and now 2026.1 decided to come out right before my upgrade. What route did you go?

chucksimalchik

I downloaded the full ISO and went to run that on my MPE. It told me that I already had an active upgrade session and to go to the web console central update dialog. I presume that was because I already downloaded 2025.4.3 and it was showing as ready to install. Going that route it successfully upgraded to 2025.4.3. Didn't try to download or sell me on 2026.1.

I am guessing if you don't have 2025.4.3 downloaded already, and you don't download 2026.1, you can grab the offline installer ISO for the old version from the customer portal and use that.

u303083

Great news! I unfortunately hadnt predownloaded yet. Kind of scared of the offline installer vs using the centralized upgrade tool being that this is my first upgrade.

bmrad

Starting with 2026.1, when running online upgrades the GUI will present the latest release as well as the latest version of the previous release in the Updates page. You'll need to make sure you have the latest SWA (SolarWinds Administrative Service), but you should see something like this:

chucksimalchik

This is wonderful news!!!

u303083

I see your current version is 2025.4.1. My current version is 2024.4.1 I assume my v. wont see that option yet?

bmrad

It should be backwards compatible, try refreshing the Updates page, it should force the SWA to update, if it doesn't change, try updating it manually. Otherwise, open a ticket.

u303083

Had to do "check compatibility" which forced it to update the SWA services and now i see it! Thank you so much!

bharris1

Does this 2025.4.3 upgrade also appear with the offline installer @bmrad or just through the updates tab under deployment on the website?

bmrad

No, for offline you download the version you want in the customer portal.

bharris1

I am receiving this error following the upgrade from the offline installer for 2025.4.3. Install was successful, config wizard is failing.

@bmrad

Error while executing script- The index 'idx_voicdrs_orgphon_id' is dependent on column 'DateTimeDisconnectUTC'.
The index 'idx_voipcdrs_destphoneid_id_pkid' is dependent on column 'DateTimeDisconnectUTC'.
ALTER TABLE ALTER COLUMN DateTimeDisconnectUTC failed because one or more objects access this column.

u303083

my upgrade was a failure! Had to pull in sw support and they couldnt fix it. I had to revert my db and main poller. The upgrade hosed up on my main poller

20:10:58,975 [12] ERROR DBConfigProcessor - Failed on C:\Program Files (x86)\SolarWinds\Orion\OrionCoreDatabaseScheme.dbConfig script with error SolarWinds.ConfigurationWizard.Common.ConfigurationException: Error while executing script- Cannot continue the execution because the session is in the kill state.

u303083

this is my error when ran from the upgrade tool

u303083

Did you find a fix?

bharris1

Yes, my DBA and I were able to find a KB article for a similar error as we were waiting for SW support to get back to us, which was dropping the two indexes. We did that and the installer continued. As it continued, support reached out and had the same fix we already put in (dropping indexes). Halfway through the config wizard it got stuck updating applications and templates and the fix was in this KB article (https://solarwindscore.my.site.com/SuccessCenter/s/article/Configuration-stuck-in?language=en_US). The fix was to kill the process and let it continue. Once it finished, we ran the config wizard again and it completed successfully. I then used the centralized upgrade to push out the APE updates.

When that was all done, we were looking good, but as I was testing all the modules I found that our WPM environment was completely broken. The two player locations were offline, still showing the old version. I went in and manually updated the player and recorder on the servers and it was still showing "Location Not Available." The two nodes were also showing down because the agents weren't active. I found that they both were hanging doing agent upgrades and the service on both was showing "Starting". I tried to kill the processes and install manually, but I couldn't get the agents to connect to the main poller. This made no sense as it worked just fine on 2024.4.1 and there was no firewall blocks between these servers. As I was troubleshooting the agents, I found our Manage Agents page was also having problems. It would just spin and time out after a few minutes and there was no way I could get to the agent page.

It was about that time that I decided to roll back, which was successful. On power up of the servers, everything came online without issue on 2024.4.1. Before I rolled back I took diagnostics from the main poller and sent them to support. I'm hoping they can determine what happened.

u303083

Oh boy, sounds like one issue after another!

Are your databases in an AOG? I "think" our issue was because the primary db may have failed over at one point or another but cant prove it since I dont have my server logs anymore.

bharris1

https://thwack.solarwinds.com/discussion/comment/522856#Comment_522856

No I didn't. I've never disabled it or turned off auto failover since we switched to AO like 4-5 years ago. We've done at least one upgrade a year during that time and never had any issues.

bharris1

@u303083 will you be retrying to upgrade? I'm trying to decide whether to attempt 2025.4.3 again or try 2026.1. I'm expecting the same errors to happen again so I would probably upgrade and take diagnostics from every poller right away to allow for troubleshooting.

u303083

@bharris1 i think im going to try to upgrade next Wednesday to 2025.4.3. SW support reviewed my diagnostics and said my error was related to AOG. Apparently I had a failover happen during my upgrade. This is my first one so i really wasnt watching the DBs or expected them to failover

u303083

@bharris1 if you go to 2026.1 doesnt that version require additional ports to be opened? I feel like a vaguely remember reading that somewhere.

bharris1

Yes it does. I'm tentatively scheduling another try at 2025.4.3 for 3/10. Hopefully now that I am aware of the issues, I can quickly get through them and troubleshoot the agents if they fail again.

u303083

Mine is scheduled for 2025.4.3 on 3/4. best of luck.

u303083

did support review your logs for the agent issue?