Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

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: 60 Votes: 0 Revisions: 3


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.


NPM version 11.5.2 and earlier


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
22:21, 22 Jun 2016