Network Management

Configuration wizard issues due to Basic SQL AlwaysOn on SQL 2016

SQL AlwaysOn not storing the correct connection string due to uncommon SQL AlwaysOn Configuration. After running the SolarWinds Orion online installer, the Configuration wizard fails with an SQL exception. You can re-run the Configuration wizard on the main polling engine. After installing the SolarWinds Platform, you may not be able to run the Configuration wizard on the main polling engine and on any additional polling engine server.

First published date

10/22/2018 3:43 PM

Last published date

6/20/2025 9:32 PM

Overview

After running the SolarWinds Platform online installer, the Configuration wizard fails with an SQL exception.

  • Every time the Configuration wizard runs, it adds a new connection entry to the SWNetPerfMon.db file.
  • The source only states the SQL server name (not the SQL server name/instance as is required).

 

Configuration error that occurred after running the SolarWinds Orion online installer:

ERROR Configuration Progress Scene - Exception while configuring plugin Orion Core Services component Orion Database>. System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred


Product section

Orion Platform

Cause

This issue is on the SQL side.

  • You are using Basic AlwaysOn on your SQL server, and the AlwaysOn listener has a named instance, for example: mylistener\myinstance. The Configuration wizard strips the instance and fails.
  • Your SolarWinds Platform product is having issues because you are using SQL AlwaysOn with no instance, but only a server name.


As a result, the file C:\Program Files (x86)\SolarWinds\Orion\SWNetPerfmon.DB is incorrect
because there are no users with Named Instance on the listener. It's not common nor expected.

SQL Setup in SQL Mgmt Studio



In the SWNetPerfmon.db file:


 Alternative Example:


Resolution

If SQL AlwaysOn is always running on a unique port (For Example 1451 or 2055),

Then you need to add the port to Configuration wizard to stop instance from being stripped.

 

To resolve the issue:

  1. Run the Configuration wizard.
  2. In the Database Settings, use "mylistener,port" as the SQL Server if the port is unique for every instance on the listener.

 

The Configuration wizard now completes successfully.

You can also specify the SQL AlwaysOn port in the SWNetPerfMon.db file:

  1. Open C:\Program Files (x86)\SolarWinds\Orion\SWNetPerfmon.DB in a text editor.
  2. Specify the following as the Instance Name:  [ServerName], [SQLalwaysOnPort]
    Example: DBServer-11, 1451  

The database file will remain correct and you can run the Configuration wizard on any polling engines.