the error i got in command line is

HResult 0xFFFFFFFF: An error occurred while obtaining the DAC port.
And login timeout expired

many thanks for your great articles. One question: Why you don’t handle the worst case in the trigger itself by design:
IF OBJECT_ID(‘AuditDb.dbo.ServerLogonHistory’, ‘U’) IS NOT NULL
INSERT INTO AuditDb.dbo.ServerLogonHistory
SELECT SYSTEM_USER,USER,@@SPID,GETDATE()

With this check works the login, even if the table is not available. But is this a performance issue?

Thanks again for any and all responses. it’s greatly appreciated.

Great article, unfortunaately, i also have a similar issue to Jan, above. if you or anyone else can provide any assistance it would be greatly appreciated. This is the only site I have found that has been in any way useful.

Many thanks for a great resource.
====================================

Error message as below:

E:\SQLDATA\MSSQL10_50.SQLSERVER01\MSSQL\Binn>SQLCMD -s SRV-sql-01 -d master -A
HResult 0x274D, Level 16, State 1
SQL Server Network Interfaces: Could not establish dedicated administrator connection (DAC) on default port. Make sure that DAC is enabled [10061].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.

I have an even worse accident. I get the message:
“C: \ Documents and Settings \ George> sqlcmd-S surf \ SQLEXPRESS-d master-A
HResult 0xFFFFFFFF, Level 16, State 1
SQL Server Network Interfaces: An error occurred while Obtaining the dedicated and
dministrator connection (DAC) port. Make Sure That SQL Browser is running, or ch
eck the error log for the port number [xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0: A network-related or in
stance-specific error has occurred while Establishing a connection to SQL Server
. Server is not found or not accessible. Check if instance name is correct and i
f SQL Server is configured to allow remote connections. For more information see
SQL Server Books Online ..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0: Login timeout expired. ”
I can not connect in any way with the server.
It also finds you the solution!
Regards

I have 1 qn tho.. The circumstance through which I arrived at this same error was a bit different from what you described. I got this problem just after creating a logon trigger which does similar to what your logon trigger in this post does. No database was deleted. I encountered the error right after creating the trigger and attempting to logon to the database to test the audit. Any ideas why this is the case?

Thanks for this, I am getting the same error on my sql server logs,

Date 3/26/2012 2:39:39 PM
Log SQL Server (Current – 3/25/2012 1:28:00 AM)

Source Logon

Message
Logon failed for login ‘Mydatabase’ due to trigger execution.

I have checked and done with the steps you have given above, but there is no server trigger present on master database.

Can you please help me finding the issue here.

Regards
Rohit Malik

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

Thanks,
Varun

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.

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………….

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!

worked like magic for me too

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.

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.

SELECT object_definition( < objectID > )
GO