Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > 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 Jonathon.Privett on Jul 24, 2018

Views: 1,463 Votes: 3 Revisions: 6

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

Tags

Classifications

Public