Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Configuration wizard issues due to Basic SQL AlwaysOn on SQL 2016

Configuration wizard issues due to Basic SQL AlwaysOn on SQL 2016

Created by Kevin Twomey, last modified by Alexis Pasao on Dec 07, 2018

Views: 834 Votes: 0 Revisions: 29

Updated December 7,  2018

Overview

After running the SolarWinds Orion 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

 

33333.png

Environment

  • NPM 12.2 HF4, SAM 6.5
  • SQL 2016
  • SQL AlwaysON

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 Orion 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

SQL AlwaysON Setup.PNG

In the Orion SWNetPerfmon.db

22222.PNG

 

 Alternative Example:

  • db.jpg
  • cluster.jpg

 

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.

    222.PNG

The Configuration wizard now completes successfully.

The connection string is hard-coded for the instance, and thus stays locked in place. ​​​​​

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.

 

Config Wizard options:

  • CW Settings: Incorrect          

    • Instance Name: DBServer-11                                      

    • Instance gets Stripped away.

  • CW Settings: Correct: (But Still errors out)              

    • Instance Name: DBServer-11\Solarwinds             

    • Edit SWNetPerfmon DB file to this and CW continues, but will error out as above

  • CW Settings: Alternative Workaround Correct: (This is the solution)       

    • Instance Name: DBServer-11, 1451                          

    • Edit SWNetPerfmon DB file to this and CW continues and completes.

 

 

Suggested Tags:  HA-4367

 

A reason for rework or Feedback from Technical Content Review:

 

 

Last modified

Tags

Classifications

Public