Comments on: SQL SERVER – Fix : Error : 17892 Logon failed for login due to trigger execution. Changed database context to ‘master’.

By: namanthakral

namanthakral — Tue, 31 Jan 2012 06:48:09 +0000

Wonderful article i messed my servers and was really clueless what to do next but ur article and mainly DAC inplementation saved my life thanks a lot

By: Varun Mehta

Varun Mehta — Mon, 30 Jan 2012 13:32:52 +0000

Hi Pinal,

That is a very good information you gave in this article. :)

Thanks,
Varun

By: Amar

Amar — Thu, 13 Oct 2011 23:03:02 +0000

Question: Would using login triggers cause performance issue in applications.

I am trying to implement login trigger that would restrict the SQL account used by application to login from particular host only.

This would avoid other instance of same application to accidentally connect to production instance.

Could you please let me know what are the pros and cons.

By: Tawab

Tawab — Sat, 06 Aug 2011 04:44:36 +0000

hi, as u mentioned above how to use sqlcmd on real mode …….

By: Satheesh Kumar . P

Satheesh Kumar . P — Thu, 14 Jul 2011 07:09:39 +0000

Hi pinal,

My database contains 2200 stored procedure,the developers didnt include SET NOCOUNT ON to all the stored procedures…
Is there any options to activate SET NOCOUNT ON to whole database or server?
if it is there please tell me how to do this or otherwise i have to do manually………….

By: favorable

favorable — Fri, 18 Feb 2011 20:50:26 +0000

Pinal,

You have excellent information. I was bombed with a similar error: Logon failed for (user) due to trigger execution.
Changed database context to ‘master’.
Changed language setting to us_english. (Microsoft SQL Server, Error: 17892) for over 30 hrs.
Tried SQLCMD, and DAC none would work for me. However, today decided to search your forum and thank God, the solution was right there.
It’s a miracle!

By: Dove265

Dove265 — Thu, 16 Dec 2010 05:29:16 +0000

C:\Documents and Settings\dove165>sqlcmd -s ghdb78 -e -A -q “Disable trigger tr
igLogon_CheckForSysAdmin ON ALL SERVER”
Disable trigger trigLogon_CheckForSysAdmin ON ALL SERVER
1>

worked like magic for me too

By: Arun J M

Arun J M — Tue, 30 Nov 2010 04:51:13 +0000

Thanks for your explanation

By: Judi

Judi — Mon, 29 Nov 2010 05:25:18 +0000

Mega Thanks! Along with Terry I thought I was really in for it when this error occurred and when I read further about the script that I ran… well it was a little too late! You most definately saved my bacon and made my day. Thanks, thanks and again thanks.

By: wolft

wolft — Sat, 16 Oct 2010 20:04:03 +0000

Thanks for your explanation

By: Nagnath Kendre

Nagnath Kendre — Sat, 21 Aug 2010 06:57:08 +0000

DAC is not connecting to remote server databse

Error: Login timeout expired

make sure that dac is enabled …
error occured while establishing connection

i have to kill trigger becuase of this my work is stopped please help me.

By: Selvakumar

Selvakumar — Tue, 27 Jul 2010 06:27:26 +0000

SQL Server

By: Sanjay Dubey

Sanjay Dubey — Sat, 24 Jul 2010 11:50:19 +0000

Hi,
I am getting the same error but it did not work for me. But below steps resolve my problem.

1.Connect SQL Server using sqlcmd go to run type cmd. You can get the command prompt. Now type below command:

sqlcmd -S LocalHost -d master –A

2.Now search for trigger :

SELECT * FROM sys.server_triggers
GO

Found the trigger i found the trigger “tddl_limitconnections”

3. Than i drop the trigger.

drop trigger tddl_limitconnections on all server
GO

Now i am able to login using SQL Server Management Studio.

It resolves my problem may be this resolves yours too. If the triggers are not same please find trigger first than replace with tddl_limitconnections trigger it may resolve your issue.

Thanks.

By: Gergo

Gergo — Tue, 08 Jun 2010 13:43:52 +0000

hm, my ‘objectID’ text was deleted, maybe because I used < > instead of & lt; & gt; …so the correct phrase is:

SELECT object_definition( < objectID > )
GO

By: Gergo

Gergo — Tue, 08 Jun 2010 13:38:37 +0000

You may have to select from sys.server_triggers table. I mean the statements you should use at sqlcmd are the followings:

SELECT * FROM sys.server_triggers
GO

You can use the statement below to make sure what you will drop

SELECT object_definition()
GO

where the objectID is the object_id you got from the select and whose code you want to see.

By: Saby

Saby — Fri, 07 May 2010 10:51:44 +0000

hi Dave i m getting the same error but i dnt no the trigger name where i can drop the trigger please let me where i can find this trigger as i m enable to find out the trigger name

By: Terry

Terry — Wed, 31 Mar 2010 21:29:32 +0000

Holy Crap… that was a life saver!!!! One of those where I thought I was in for it! Thanks….

By: Darshan Shah

Darshan Shah — Mon, 29 Mar 2010 14:09:48 +0000

Thanks Pinal , It solved my issue.

By: Prashant

Prashant — Thu, 25 Feb 2010 14:31:31 +0000

Hi Pinal,

Thank you for such a nice article. While reading this I am puzzling with one question. Is it possible to track INVALID LOGINs to Sql Server. I mean if there is a Login attempt to Sql Server with incorrect login details, then a that should be recorded into one database table?

Please suggest.

Thanks Again

By: KLEBER

KLEBER — Wed, 25 Nov 2009 15:13:03 +0000

Thanks a lot! great help.

Firing these types of triggers or procedures should also be instructed to run the fix.

Thanks again.

By: Mark Morgan

Mark Morgan — Mon, 26 Oct 2009 18:05:56 +0000

Good article, however this fix will not work for me. I am receiving the error on a cluster instance. Remote DAC is disabled and I can’t connect to the instance locally as the cluster node doesn’t see any of the instances as local.

Any advice / work-around would be most appreciated.