title: Finding Classic ASP errors in a custom 404 error page in IIS7
body: <p>We are migrating some Classic ASP sites from an IIS6 box to a new Server 2008 box running IIS7.</p>
  
  <p>We have been through a learning process with regard to custom errors and now have these working correctly and Server.GetLastError is now working.</p>
  
  <p>The sites we are migrating use a bespoke CMS that utilises a custom 404.asp error page to pull content from a database depending on the URL.  This, too, works perfectly.</p>
  
  <p>However, when the 2 are combined (e.g. we have a 500 error on a page that runs via the custom 404 page) we receive a completely blank page.  No error, no information nothing.  Just a plain white page.</p>
  
  <p>Example 1: <a href="http://snavebelac.com/thisdoesnotexist" rel="nofollow">http://snavebelac.com/thisdoesnotexist</a> results in the custom 404 page
  Example 2: <a href="http://snavebelac.com/st-test" rel="nofollow">http://snavebelac.com/st-test</a> blank page.  This has an intentional 500 error within the custom 404 page.</p>
  
  <p>I assume that because it is running through the custom 404.asp error page that this somehow blocks the custom 500 error page from functioning.</p>
  
  <p>Does anyone know how I might be able to configure the sever so that the custom 404 page fires but 500 errors are output to the browser as they were in IIS6 OR is there a way to configure the server to process the custom 404 as well as the custom 500?</p>
  
  <p>Thanks in advance.</p>