How do I fix 404.17 error on Win Server 2k8 and IIS7

Question

I've setup a new .net 2.0 website on IIS 7 under Win Server 2k8 and when browsing to a page it gives me a 404.17 error, claiming that the file (default.aspx in this case) appears to be a script but is being handled by the static file handler. It SOUNDS like the module mappings for ASP.Net got messed up, but they look fine in the configurations. Does anyone have a suggestion for correcting this error?

Answer 1

I had this problem on IIS6 one time when somehow the ASP.NET ISAPI stuff was broke.

Running

%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

to recreate the settings took care of it.

Answer 2

This solution worked for me... (I've had aspnet_regiis.exe -i do some damage)

http://forums.iis.net/t/1157725.aspx

1. Locate your App Pool and Right Click
2. Select Basic Settings
3. Select your current .Net Framework Version
4.Restart the App Pool 

Answer 3

So far, none of these solutions have worked for me.

I have found a few other possible solutions (which did not work for me):

• http://first-reboot.blogspot.com/2009/12/error-40417-opening-asmx-page.html
• http://forums.asp.net/p/1432329/3219236.aspx

Answer 4

For me, my problem came because of a setting in my project's web.config file (and also the solution, once I understood the problem).

In my web.config file, we had these two lines in the system.webServer > handlers area:

<remove name="WebServiceHandlerFactory-ISAPI-2.0" />
<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

Notice the alternative handler has the attribute 'preCondition="integratedMode"'. So, I had to change my AppPool to use Integrated instead of Classic for my pipeline mode setting (which is the opposite of what the solutions above told me to do).

Answer 5

Only one way to solve this problem...

First Installed Windows7 Then Install IIS 7 with all features

And then installed Visual Studio 2008 / 2010

I work on visual studio 2008 and 2010 but I never seen this error before.

I can also try on my friend's PC. And also I solve this error.