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

NPM Upgrade to 2024.2.1 failure

Hi,

I upgraded from 2023.4.2 to 2024.2.1 ad I am getting an error when running the confg wizard

Database configuration failed

connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported

Nothing in my environment changed, I am not doing any kid of mirrored SQL server. I have 1 front end app/polling server and 1 DB server.

Any help would be much appreciated as everything is currently down now.

Find more posts tagged with

Accepted answers

All comments

bobmarley

If it is at the very end of the install or in the middle somewhere? I have received this error at the very end several times and just ignored it and the install worked fine. It was on the very last step each time of the config wizard. If you could supply a screenshot it may help.

melchiok

The error was at the beginning, about 5% into the config wizard.

bmg4357

We just hit this as well. Go to C:\Program Files (x86)\SolarWinds\Orion\ or wherever you have the product installed and edit SWNetPerfMon.DB with Notepad (we had to elevate as admin for UAC). In there you will see the setting for MultiSubnetFailover=True in the connection string. Change it to False and save the file. Run the configuration wizard on the application server and let it complete. You may have to do the same for any extra poller nodes you may have. Hope this helps. Tech support had ZERO clue on this and we just spent over four hours on it and finally stumbled upon that.

melchiok

Thanks! I’ll give that a shot. I ended up having to do a restore on my server since Solarwinds support was trying to blame my SQL infrastructure.

Kita

Appreciate the feedback @bmg4357 . We are discussing this internally on how we can help prevent this problem. Hopefully more to share in the future.

bobmarley

Thanks for posting this. I made my team aware as we will be performing the same upgrade soon.