Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Failed SA login attempts

Failed SA login attempts

Table of contents
Created by Norbert Skurzewski, last modified by MindTouch on Jun 23, 2016

Views: 1,142 Votes: 0 Revisions: 3

Overview

This article provides brief information on failed SA login attempts especially when running the Configuration Wizard. The SA account is not used for the database, db_Owner is the account used throughout the environment.

Environment

NPM version 11.5.2 and earlier

Detail

Orion does not need SA Access - db_Owner should be fine for anything the wizard needs to do, and will extend only to the SolarWinds database.

The reason you are seeing the failed SA logins is because the Config Wizard first tries SA in case the customer has set up their SQL server with SA login with no password (Seems like a terrible idea, but it does happen). Assuming this is not how it is set up, you will see a failed log in, then the Config Wizard will proceed with using the proper account specified with the correct permissions.

 

 

Last modified

Tags

Classifications

Public