SQL Server log being filled with login errors by SQL Server SAM

wan-der-dog

Hi all,

Our company is relatively new to Solarwinds Orion Application monitors and we have been slowly rolling out our monitoring package. We are using the SQL Server application monitors extensively however they all exhibit the same issue, the application monitor is causing our SQL Error log to be filled with permission errors like the following:

Login failed for user 'Domain\account'. Reason: Could not find a login matching the name provided.

Error: 18456, Severity: 14, State: 5.

Now this error occurs when SQL tries to interpret a Windows login as a SQL Login. It is my preference to not use SQL Logins in order to monitor our SQL estate, however I cannot seem to find a method of telling the application monitor that the login is a Windows one.

The frustrating thing is that the applicaiton monitor is working however the amount of noise in the log file is unacceptable.

Has anyone else run into this issue and worked around it?

Cheers

aLTeReGo

The SQL User Experience Monitor defaults to using SQL authentication first, then tries Windows authentication if that fails. This can be changed within the application template by clicking the checkbox in the image below for each SQL user experience monitor. This is a good chance to try out the in SAM 5.2.