DB related issues in 2019.4

Hi,

I have installed Orion 2019.4 version recently and it was successful. Database for Orion and NTA were created while doing the configuration wizard. However due to some policy restrictions I need to change the passwords of the DBs and have tried the same via configuration wizard.

But my config wizard is failing and from the logs I can see the below error. I am not using the SA user anywhere, but still getting the error.

ERROR SWEventLogging - Service was unable to open new database connection when requested.

SqlException: Login failed for user 'sa'.

Connection string - Data Source=<DB server name>;Initial Catalog=master;User ID=sa;Password=*******;Pooling=False

Another issue I observed is while running the active diagnostics getting the warning for DB user do not have permission to ready the SQL logs. The DB user was created by the confg wizard, but still getting this error.

Can some one help me in resolving these.

Find more posts tagged with

orion 2019.4 installation failed

Accepted answers

All comments

hpstech

You can check the config in here as a start - SWNetPerfMon.DB config file in C:\Program Files (x86)\SolarWinds\Orion

jblankjblank

This would be best resolved through a support case. Please log a case and upload diagnostics. This will allow us to properly investigate. Share your support case number here so I can also track it.

sreenathmp

HI Hpstech,

SWNetPerfMon.DB config file doesn't show any entry with the SA user. Is there any other file which need to be checked.

pratikmehta003

is you SA account locked out by any chance?

sreenathmp

Hi Pratik,

I am not using SA account for DB in Solarwinds.

pratikmehta003

I asked the question as in your screenshot it was showing error for SA

user....

sreenathmp

Yes Pratik, That's where I am confused. I haven't used SA account during the installation or in the config wizard. But while trying to run the config wizard again its getting failed and have seen that log in the log file.

gkjono

I've noticed in several environments that the configuration wizard triggers failed logons for the SA account, even though the account was never used. There has to be some code in the configuration wizard that wasn't cleaned up correctly or something. Usually it will still complete successfully after the failure using the credentials that were supplied during the configuration. I would try not to focus too much on the SA account failures and make sure that your credentials and permissions are correct for the account that you are defining.

Access to the SQL logs can be resolved by adding the user to the SecurityAdmin role in SQL. This is a required role for the account doing the install, but I don't believe it's actually needed for the account that Orion uses to connect to the database for daily operations.
Success Center

These may be helpful too.
Success Center

-Greg Kjono

Loop1 Systems: SolarWinds Training and Professional Services

LinkedIN: Loop1 Systems
Facebook: Loop1 Systems
Twitter: @Loop1Systems