Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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,204 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