IIS 7 & IIS 8
ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Last post Dec 22, 2011 09:21 AM by ctarpy
Sep 27, 2006 10:59 PM|LINK
Oct 12, 2006 09:07 PM|LINK
I just put vista on my machine and IIS7 with it.
I have enabled ALL the features including development of asp.net
I can see the aspx handler in the handler console of IIS7 and when executing:
C:\>%windir%\system32\inetsrv\appcmd list config "Default Web Site/" -section:handlers
but still when I browse to any aspx page in my virtual directory I get error 404.3 (MIME not configured etc...)
I made sure aspx is registered using aspnet_regiis -i
I also removed and reinstalled IIS (enabling all its features) but still 404.3
What Can I do?
Oct 16, 2006 05:12 PM|LINK
I had a similar problem and ran across an blog here:
Basically what fixed this for me was opening up the ISAPI and CGI Restrictions manager in IIS 7 and found that the "Restriction" column for ASP.NET 1.1.4322 was "Not Allowed". Once I allowed this it started working.
Hope that helps.
Oct 17, 2006 01:00 PM|LINK
Hi -- I am also getting this problem. Running on Vista RC2 with all ASP install options checked.
I also noticed that the handlers that should have been installed by Visual Studio 2005 (e.g., for
*.cs, *.csproj, *.vsdisco, etc.) are missing from the applicationHost.config.
When I execute appcmd on "Default Web Site", I do not see the handlers for aspx, asmx, etc.
I do not have .NET 1.1 installed on the system. Have tried re-installing VS2005, ASP Feature many times.
Do advice how this problem can be solved. Thanks!
Oct 23, 2006 05:51 AM|LINK
It sounds like several different problems. Let me try to separate them:
1412228: Some program, or possibly a bug in our ABO compatibility layer, has caused your handler list to be cleared for the "Default Web Site", removing the globally configured handler mappings for ASP.NET 2.0.
By removing the location tag that introduces the <clear> in the <handlers> section, you should be able to recover.
However, if you can provide a more detailed description of what led to that config, we can investigate whether this was a bug.
1427193: You are having a similar issue. I posted a (likely) solution on your other thread - .1437278
1431322: You are using ASP.NET 1.1 and required to enable the ASPNET_ISAPI.dll for ASP.NET 1.1 in order to make it work. This is expected, unless you also ran the ASPNET_REGIIS tool and expected it to enable your ISAPI and it didnt. If so, that is a separate
issue we should look into.
1431322: Are you any of the above? :) If not, what is it?
IIS Core Server
Visit mvolo.com for more inside information on IIS7, IIS and ASP.NET
Nov 05, 2006 11:42 PM|LINK
I got into the same issue as jbristowe. Doing what you said, deleting the <clear> in the <handlers> section for the Default Web Site did the trick. I also had a bunch of duplicate add statements in there for other mappings, once i deleted those too it inherited
all of the global mappings which is what i wanted it to do. How it came up with this config is a mystery to me. Here is the <handlers> part that was in my applicationHost.config file
<add name="TRACEVerbHandler" path="*" verb="TRACE" type="" modules="ProtocolSupportModule" scriptProcessor="" resourceType="Unspecified" requireAccess="None" preCondition="" />
<add name="OPTIONSVerbHandler" path="*" verb="OPTIONS" type="" modules="ProtocolSupportModule" scriptProcessor="" resourceType="Unspecified" requireAccess="None" preCondition="" />
<add name="StaticFile" path="*" verb="*" type="" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" scriptProcessor="" resourceType="Either" requireAccess="Read" preCondition="" />
Nov 05, 2006 11:57 PM|LINK
Nov 06, 2006 06:44 AM|LINK
How are you creating these vdirs, that is causing the web.config to be generated?
Nov 06, 2006 04:40 PM|LINK
Very sorry, more careful inspection shows that this may have been a remnant from before I removed the <clear> tag from the applicationHost.config file. I tried it with a brand new virtual directory (added using IIS Manager) and new physical location and
there is no web.config file. It also inherited all the mappings from the Default Web Site.
Any idea how come the <clear/> tag was in the applicationHost.config file to begin with?
Nov 11, 2006 12:02 AM|LINK
We are trying to determine this ... if anyone has a set of repro steps that result in this configuration, please share it!