Network Management

Failed SA login attempts

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.

First published date

11/1/2018 9:39 PM

Last published date

11/28/2022 5:05 AM

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_oOwner is the account used throughout the environment.

Product section

Network Performance Monitor

Resolution

Orion does not need the SA credentials to access the SQL Server or database and the db_owner role should be sufficient for anything the Configuration Wizard needs to do and will extend only to the SolarWinds database.

The reason you are seeing the failed SA logins is because the Configuration Wizard first tries SA in case the SQL Server has the SA account set with no password. Assuming this is not how it is set up, you will see a failed login attempts, then the Configuration Wizard will proceed using the proper account specified with the correct permissions.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.