<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: How to handle IIS Event id 1009 (Event id 5011 on IIS 7)</title>
	<atom:link href="http://martinnormark.com/2007/10/26/how-to-handle-iis-event-id-1009-event-id-5011-on-iis-7/feed" rel="self" type="application/rss+xml" />
	<link>http://martinnormark.com/2007/10/26/how-to-handle-iis-event-id-1009-event-id-5011-on-iis-7?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=rss</link>
	<description></description>
	<lastBuildDate>Wed, 10 Mar 2010 13:52:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: FlipScript</title>
		<link>http://martinnormark.com/2007/10/26/how-to-handle-iis-event-id-1009-event-id-5011-on-iis-7/comment-page-1#comment-1194</link>
		<dc:creator>FlipScript</dc:creator>
		<pubDate>Tue, 29 Sep 2009 01:33:10 +0000</pubDate>
		<guid isPermaLink="false">/post/How-to-handle-IIS-Event-id-1009-(Event-id-5011-on-IIS-7).aspx#comment-1194</guid>
		<description>Great write up.  Just a couple of questions / comments for you.

1. Is this even necessary?  Unhandled errors automatically bubble up to the Application_Error() event in global.asax, so ASP.NET really has it&#039;s own UnhandledErrorHandler.

2. You don&#039;t need to recurse an Exception&#039;s InnerException methods explicitly.  This is done automatically for you when you call Exception.ToString() [but not Exception.Message() ].


Mark
FlipScript.com</description>
		<content:encoded><![CDATA[<p>Great write up.  Just a couple of questions / comments for you.</p>
<p>1. Is this even necessary?  Unhandled errors automatically bubble up to the Application_Error() event in global.asax, so ASP.NET really has it&#8217;s own UnhandledErrorHandler.</p>
<p>2. You don&#8217;t need to recurse an Exception&#8217;s InnerException methods explicitly.  This is done automatically for you when you call Exception.ToString() [but not Exception.Message() ].</p>
<p>Mark<br />
FlipScript.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin H. Normark</title>
		<link>http://martinnormark.com/2007/10/26/how-to-handle-iis-event-id-1009-event-id-5011-on-iis-7/comment-page-1#comment-1193</link>
		<dc:creator>Martin H. Normark</dc:creator>
		<pubDate>Wed, 14 May 2008 13:55:35 +0000</pubDate>
		<guid isPermaLink="false">/post/How-to-handle-IIS-Event-id-1009-(Event-id-5011-on-IIS-7).aspx#comment-1193</guid>
		<description>@Seth

That&#039;s interesting. I guess this could be because of IIS specific settings.

Have you changed settings, or is it a clean install?</description>
		<content:encoded><![CDATA[<p>@Seth</p>
<p>That&#8217;s interesting. I guess this could be because of IIS specific settings.</p>
<p>Have you changed settings, or is it a clean install?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth Petry-Johnson</title>
		<link>http://martinnormark.com/2007/10/26/how-to-handle-iis-event-id-1009-event-id-5011-on-iis-7/comment-page-1#comment-1192</link>
		<dc:creator>Seth Petry-Johnson</dc:creator>
		<pubDate>Wed, 07 May 2008 15:37:10 +0000</pubDate>
		<guid isPermaLink="false">/post/How-to-handle-IIS-Event-id-1009-(Event-id-5011-on-IIS-7).aspx#comment-1192</guid>
		<description>I found this post through Google while trying to debug application pool restarts on a production system of my own. I set up a test site with your &quot;click here to crash IIS&quot; code, but I do _not_ get Event ID 5011 like you demonstrate. Instead, I get Event ID 1334 [complete with a stack trace] and Event ID 5000 [contains type of exception and some debugging info].

Any suggestions as to why I get a stack trace and you don&#039;t?
</description>
		<content:encoded><![CDATA[<p>I found this post through Google while trying to debug application pool restarts on a production system of my own. I set up a test site with your &quot;click here to crash IIS&quot; code, but I do _not_ get Event ID 5011 like you demonstrate. Instead, I get Event ID 1334 [complete with a stack trace] and Event ID 5000 [contains type of exception and some debugging info].</p>
<p>Any suggestions as to why I get a stack trace and you don&#8217;t?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
