title: 404.17 error - requested content appears to be script
body: <p>I have a similar question to <a href="https://stackoverflow.com/questions/87107/how-do-i-fix-404-17-error-on-win-server-2k8-and-iis7">this one</a>;  </p>
  
  <ul>
  <li>IIS 7.5</li>
  <li>Server 2008</li>
  <li>ASP.Net 4.0 web site</li>
  </ul>
  
  <p>The error I get when trying to run the site is this:</p>
  
  <blockquote>
    <p>HTTP Error 404.17 - Not Found<br>
    The requested content appears to be script and will not be served by the static file handler.</p>
    
    <p>...</p>
    
    <p>Most likely causes:  </p>
    
    <ul>
    <li>The request matched a wildcard mime map. The request is mapped to the static file handler. If there were different pre-conditions, the request will map to a different hander.</li>
    </ul>
  </blockquote>
  
  <p>Now here comes the weird part:</p>
  
  <h2>THE WEIRD PART</h2>
  
  <p>The weird part is that on the develop server -- <em>which is similar in every aspect to the production server</em> -- everything runs smoothly.</p>
  
  <p>Here's a list of things I <strong>cannot</strong> try, because I don't want to mess with the sever (it hosts many other sites):</p>
  
  <ul>
  <li>Reinstalling .Net</li>
  <li>Reinstalling IIS</li>
  <li>Reinstalling <em>anything</em></li>
  <li>Running aspnet_regiis</li>
  </ul>
  
  <p>Here's what I <em>did</em> try:</p>
  
  <ul>
  <li>Republishing the site</li>
  <li>Restarting the application pool</li>
  <li>Changing the application pool to .Net 2.0 and back to .Net 4.0</li>
  <li>Switching around between Integrated and Classic pipeline mode</li>
  <li>Enabling 32-bit mode</li>
  <li>Taking a look at Handler Mappings</li>
  </ul>
  
  <p>Eventually I created a new application pool, and it <em>sort of</em> started working.<br>
  <strong>Q) "Sort of"?</strong><br>
  A) Yes, sort of.</p>
  
  <p>Now the site only works when the (new) app pool is set to <code>.Net 4.0</code>, <code>Integrated</code>,<br>
  and the site's Authentication has <code>ASP.NET Impersonation</code> set to <code>Disabled</code>.</p>
  
  <p><em>Any</em> change to these settings sets the server yelping "404.17" all over again.</p>
  
  <p><strong>Q) What's wrong with that?</strong><br>
  A) What's wrong with that is that I NEED ASP.NET Impersonation for the site to function properly.</p>
  
  <p>As always, your guidance is most needed.</p>