Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SQL error events logged when using "SQL Server User Experience Monitor" components in a template

This is a little bit of an odd one. We are using a few SQL Server User Experience Monitors to capture some basic query stats and while the data is being captured and there are no errors on Solarwinds, the SQL event logs are being filled up with "Login failed for user '<domain>\SolarWinds.Service'. Reason: Could not find a login matching the name provided."

The account is added to a group that has sysadmin to the SQL servers. We tried directly adding the account to the SQL servers and it still worked but then gave messages of "Login failed for user '<domain>\SolarWinds.Service'. Reason: Attempting to use an NT account name with SQL Server Authentication."

These SQL servers all have mixed authentication active.

Can the SQL Server User Experience Monitor be used with an AD account? I mean it works but the DBAs are getting annoyed at the event logs filling with these events.

Any help would be appreciated.

Thanks

-Jim

Find more posts tagged with

Accepted answers

jburke

Think I may have figured this one out, there's a check box in the component to use windows authentication first. I just made that change so I'll verify if it works over the next 30 minutes or so...

-Jim

All comments

jburke

Think I may have figured this one out, there's a check box in the component to use windows authentication first. I just made that change so I'll verify if it works over the next 30 minutes or so...

-Jim

i_like_eggs

jburke did you manage to get it to work in the end? if so what did you do?

thanks

jburke

I marked it as the correct answer. If you don't use the check box to use Windows authentication first, it will try SQL authentication first which fills the event logs with SQL authentication failures.

-Jim

FormerMember

Strange. I did the same thing with the AppInsight for SQL server, but I still get the "attempting to use an NT account name with SQL Server Authentication" error. I can used sqlcmd or SQL Management student and the same account to connect to the SQL Server db without any problems.