<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:cs="http://blogs.iis.net/"><channel><title>Troubleshooting a 404</title><link>http://blogs.iis.net/tomkmvp/archive/2009/04/27/troubleshooting-a-404.aspx</link><description>Since IIS 6, Microsoft has made it very easy to troubleshoot the cause of a 404 "not found" error from the web server. Most admins don't realize that the IIS log file can now include the substatus code along with the 404. The first step is to make sure</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: Troubleshooting a 404</title><link>http://blogs.iis.net/tomkmvp/archive/2009/04/27/troubleshooting-a-404.aspx#3363876</link><pubDate>Mon, 24 Aug 2009 03:31:12 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:3363876</guid><dc:creator>fairyvoice</dc:creator><description>&lt;p&gt;wonderful&lt;/p&gt;
&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=3363876" width="1" height="1"&gt;</description></item></channel></rss>