This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SCM - MS SQL Server Essentials Connection Error

I'm receiving an error <ERROR [28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user... > when attempting to use the MS SQL Server Essentials profile for the first time. I noticed that the connection string is: Driver={ODBC Driver 17 for SQL Server};Server=${NodeIP};Uid=${Username}; Pwd=${Password};, which if I read the online documentation correctly is for SQL version 2019.

I'm running on 2016, so I created a new profile and replaced the connection string to Driver={ODBC Driver 13 for SQL Server};Server=${NodeIP};Uid=${Username}; Pwd=${Password};. Now I receive the below error. Has anyone set this profile up for a 2016 DB? If so, can you help me out?

Top Replies

Parents

0 s-bolyard over 3 years ago

Anyone else add the SCM SQL profiles to their database servers yet? Hopefully someone from the SolarWinds SCM team can answer why I can't get these profiles to work.
Cancel
Vote Up 0 Vote Down

Cancel
0 tmcurry over 3 years ago in reply to s-bolyard

Did you ever get resolution? Can you share?
Cancel
Vote Up 0 Vote Down

Cancel
0 s-bolyard over 2 years ago in reply to tmcurry

Sorry tmcurry, just saw this message. I worked with SolarWinds support and I guess for these SQL queries to run you have to have a local account on the SQL database server you are monitoring. I was using a domain account to connect and I guess that won't work. Once I added the local SQL account on the database destination server, it worked fine. Unfortunately I'm going to have to add a local account to all the database servers we want to monitor.
Cancel
Vote Up +1 Vote Down

Cancel

Reply

0 s-bolyard over 2 years ago in reply to tmcurry

Sorry tmcurry, just saw this message. I worked with SolarWinds support and I guess for these SQL queries to run you have to have a local account on the SQL database server you are monitoring. I was using a domain account to connect and I guess that won't work. Once I added the local SQL account on the database destination server, it worked fine. Unfortunately I'm going to have to add a local account to all the database servers we want to monitor.
Cancel
Vote Up +1 Vote Down

Cancel

Children

0 spaghettishapes over 2 years ago in reply to s-bolyard

had to do likewise
Cancel
Vote Up +1 Vote Down

Cancel
0 tmcurry over 2 years ago in reply to spaghettishapes

Unfortunately that is the case. That of course is not recommended for various government organizations.
Cancel
Vote Up +1 Vote Down

Cancel