Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Server & Application Monitor (SAM) > Logon errors in SQL Logs on a monitored SQL server

Logon errors in SQL Logs on a monitored SQL server

Table of contents
Created by William Muhle, last modified by Annette.Kirkpatrick on Aug 04, 2017

Views: 98 Votes: 3 Revisions: 4

Overview

This article provides brief information on the following error appearing within your SQL logs on a monitored SQL server despite the application monitor being able to poll the server without issues:

 

20151022 11:30:46.70 Logon Error: 18456,
Severity: 14, State: 6.


20151022 11:30:46.70 Logon Login failed for
user 'DOMAIN\USERNAME'. Reason: Attempting to use an NT account name with SQL
Server Authentication.

Environment

Any SQL server monitored by SAM

Detail

The reason for the errors is SAM will attempt log into the SQL server via both Windows credentials and SQL credentials.  This is by design and will cause a login failure for the version of authentication that it is not using.

 

 

Attempt, NT, NT account, SQL Server, Authentication, message, log, logon, 18456, login, AppInsight

Last modified
11:08, 4 Aug 2017

Tags

Classifications

Public