<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Identifying the source of SQL Server login failures (18456 errors)</title>
	<atom:link href="http://www.eraofdata.com/blog/2009/01/loginfailures/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eraofdata.com/blog/2009/01/loginfailures/</link>
	<description>SQL Server posts that DBAs will (hopefully) find useful.</description>
	<pubDate>Fri, 30 Jul 2010 16:30:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Rick Morgan</title>
		<link>http://www.eraofdata.com/blog/2009/01/loginfailures/#comment-2457</link>
		<dc:creator>Rick Morgan</dc:creator>
		<pubDate>Sat, 05 Jun 2010 23:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=114#comment-2457</guid>
		<description>Very informative and helpful - save me from utter frustration. Thanks for the work.</description>
		<content:encoded><![CDATA[<p>Very informative and helpful - save me from utter frustration. Thanks for the work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The SQL Server Default Trace &#124; Ajmer Dhariwal's SQL Server blog</title>
		<link>http://www.eraofdata.com/blog/2009/01/loginfailures/#comment-2286</link>
		<dc:creator>The SQL Server Default Trace &#124; Ajmer Dhariwal's SQL Server blog</dc:creator>
		<pubDate>Fri, 25 Sep 2009 23:15:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=114#comment-2286</guid>
		<description>[...] The query references the trace file from the period of the login failure and retrieves the columns containing all the information that should be needed to pin down where any login failure recorded in that file came from. I&#8217;ve already covered how to use this information in another blog posting covering how to identify the source of login failures. [...]</description>
		<content:encoded><![CDATA[<p>[...] The query references the trace file from the period of the login failure and retrieves the columns containing all the information that should be needed to pin down where any login failure recorded in that file came from. I&#8217;ve already covered how to use this information in another blog posting covering how to identify the source of login failures. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason TEPOORTEN</title>
		<link>http://www.eraofdata.com/blog/2009/01/loginfailures/#comment-2181</link>
		<dc:creator>Jason TEPOORTEN</dc:creator>
		<pubDate>Wed, 15 Jul 2009 01:43:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=114#comment-2181</guid>
		<description>Hi.

Thank you VERY much for making the effort of leaving a well-written and easy to follow article.

It helped me isolated a login failure on our MS-SQL 2000 server that was occurring every second.

Kind Regards,

Jason</description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>Thank you VERY much for making the effort of leaving a well-written and easy to follow article.</p>
<p>It helped me isolated a login failure on our MS-SQL 2000 server that was occurring every second.</p>
<p>Kind Regards,</p>
<p>Jason</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.eraofdata.com/blog/2009/01/loginfailures/#comment-2151</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Thu, 25 Jun 2009 15:07:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=114#comment-2151</guid>
		<description>THANK YOU!!! I have been searching days to resolve this error and your instructions worked wonders for me!!!!</description>
		<content:encoded><![CDATA[<p>THANK YOU!!! I have been searching days to resolve this error and your instructions worked wonders for me!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daily Blog List - Kev&#39;s Life</title>
		<link>http://www.eraofdata.com/blog/2009/01/loginfailures/#comment-2149</link>
		<dc:creator>Daily Blog List - Kev&#39;s Life</dc:creator>
		<pubDate>Mon, 22 Jun 2009 01:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.eraofdata.com/blog/?p=114#comment-2149</guid>
		<description>[...] Identifying the source of SQL Server login failures (18456 errors) [...]</description>
		<content:encoded><![CDATA[<p>[...] Identifying the source of SQL Server login failures (18456 errors) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
