Previous Next

• 09-21-2006, 12:41 PM

  jbristowe Joined on 09-21-2006, 3:32 PM Calgary, Alberta, Canada Posts 6

  ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact I am unable to serve up an ASP.NET page from IIS 7.0 on Windows Vista RC 1 (Ultimate Edition). Requests for an ASP.NET page (i.e. default.aspx) return the following message: HTTP Error 404.3 - Not Found Description: The page you are requesting cannot be served because of the Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web server. The page you requested has a file name extension that is not recognized, and is not allowed. Error Code: 0x80070032 ASP.NET is installed and enabled on IIS 7.0 (via the "Windows Features" applet in the Control Panel). When I examine the handler mappings for the machine (itself), the following entries are listed: PageHandlerFactory-Integrated | *.aspx | Enabled | Unspecified | System.Web.UI.SimpleHandlerFactory | Local PageHandlerFactory-ISAPI-1.1 | *.aspx | Enabled | Unspecified | IsapiModule | Local PageHandlerFactory-ISAPI-2.0 | *.aspx | Enabled | Unspecified | IsapiModule | Local Note: These entries (above) are not listed for the default Web site or any of its applications. (I can only assume that they are inherited.) When I explicitly add a handler for the path, "*.aspx" to one of my applications, the error no longer appears. However, the ASP.NET does not appear to execute. (The content served back from IIS 7.0 is empty.) I would appreciate any advice to help resolve this issue.

  Tags: "ASP.NET" Configuration "IIS 7.0"

• 09-21-2006, 4:02 PM

  In reply to

  thomad Joined on 08-20-2002, 3:28 PM Redmond Posts 387

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact I assume you request the .aspx page in the root app on the default site, e.g. http://localhost/mypage.aspx Can you send the output of the following commands: %windir%\system32\inetsrv\appcmd list apppools %windir%\system32\inetsrv\appcmd list apps and %windir%\system32\inetsrv\appcmd list config "Default Web Site/" -section:handlers If you don't request the page from the root app on the default web site you might have to change the 'appcmd list config' command to list the handler section from your app.     Thomas Deml Senior Program Manager Internet Information Services Microsoft Corp.

• 09-21-2006, 6:16 PM

  In reply to

  jbristowe Joined on 09-21-2006, 3:32 PM Calgary, Alberta, Canada Posts 6

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact No. The same behaviour (i.e. HTTP Error 404.3 - Not Found) occurs when a request is made to an ASP.NET page in the root app on the default site (i.e. http://localhost/foo.aspx). The following is the output of the commands specified above: C:\>%windir%\system32\inetsrv\appcmd list apppools APPPOOL "DefaultAppPool" (MgdVersion:v2.0,MgdMode:Integrated,state:Started) APPPOOL "Classic .NET AppPool" (MgdVersion:v2.0,MgdMode:Classic,state:Started) C:\>%windir%\system32\inetsrv\appcmd list apps APP "Default Web Site/" (applicationPool:DefaultAppPool) APP "Default Web Site/Hello" (applicationPool:DefaultAppPool) C:\>%windir%\system32\inetsrv\appcmd list config "Default Web Site/" -section:handlers <system.webServer>   <handlers accessPolicy="Script, Read">     <add name="TRACEVerbHandler" path="*" verb="TRACE" type="" modules="Protocol SupportModule" scriptProcessor="" resourceType="Unspecified" requireAccess="None " preCondition="" />     <add name="OPTIONSVerbHandler" path="*" verb="OPTIONS" type="" modules="Prot ocolSupportModule" scriptProcessor="" resourceType="Unspecified" requireAccess=" None" preCondition="" />     <add name="StaticFile" path="*" verb="*" type="" modules="StaticFileModule,D efaultDocumentModule,DirectoryListingModule" scriptProcessor="" resourceType="Ei ther" requireAccess="Read" preCondition="" />   </handlers> </system.webServer> C:\>%windir%\system32\inetsrv\appcmd list config "Default Web Site/Hello" -section:handlers <system.webServer>   <handlers accessPolicy="Script, Read">     <add name="iframecall.axd_*" path="iframecall.axd" verb="*" type="Microsoft. Web.Services.IFrameHandler" preCondition="integratedMode,runtimeVersionv2.0" />     <add name="atlasglob.axd_*" path="atlasglob.axd" verb="*" type="Microsoft.We b.Globalization.GlobalizationHandler" preCondition="integratedMode,runtimeVersio nv2.0" />     <add name="atlasbatchcall.axd_*" path="atlasbatchcall.axd" verb="*" type="Mi crosoft.Web.Services.MultiRequestHandler" preCondition="integratedMode,runtimeVe rsionv2.0" />     <add name="*.asbx_*" path="*.asbx" verb="*" type="Microsoft.Web.Services.Scr iptHandlerFactory" preCondition="integratedMode,runtimeVersionv2.0" />     <add name="*.asmx_*" path="*.asmx" verb="*" type="Microsoft.Web.Services.Scr iptHandlerFactory" preCondition="integratedMode,runtimeVersionv2.0" />     <add name="TRACEVerbHandler" path="*" verb="TRACE" type="" modules="Protocol SupportModule" scriptProcessor="" resourceType="Unspecified" requireAccess="None " preCondition="" />     <add name="OPTIONSVerbHandler" path="*" verb="OPTIONS" type="" modules="Prot ocolSupportModule" scriptProcessor="" resourceType="Unspecified" requireAccess=" None" preCondition="" />     <add name="StaticFile" path="*" verb="*" type="" modules="StaticFileModule,D efaultDocumentModule,DirectoryListingModule" scriptProcessor="" resourceType="Ei ther" requireAccess="Read" preCondition="" />   </handlers> </system.webServer> In both instances (above), the HTTP handler for the .aspx file extension appears to be missing from the application configs. It would appear as though the "Windows Features" applet did not correctly establish the appropriate configuration entries. For example, when I explicitly add the HTTP handler for the .aspx file extension to the web.config file for one of my applications, the page is processed correctly. The following element was added to /configuration/system.webServer/handlers in web.config: <add name="*.aspx" path="*.aspx" verb="*" type="System.Web.UI.PageHandler" preCondition="integratedMode,runtimeVersionv2.0" /> When this element (above) is added to the web.config file, the ASP.NET page is processed and the expected response is served to the browser. It seems that a problem exists with the "Windows Features" applet; enabling ASP.NET to run in IIS 7.0 does not establish the necessary configs. Unless I'm mistaken, once ASP.NET has been enabled, the expected behaviour is for IIS 7.0 to process any ASP.NET pages from that point on. Is this not the case? Are developers required to explicitly define a HTTP handler in the web.config for every application hosted by IIS 7.0? Thanks for your help!

• 09-21-2006, 6:50 PM

  In reply to

  thomad Joined on 08-20-2002, 3:28 PM Redmond Posts 387

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact You are right. The ASP.NET mappings are not installed. I don't know why to be honest. Was there something with Atlas and IIS7? I thought I read something somewhere. Did you install Atlas afterwards and what version of Atlas? Can you have a look into the %windir%\IIS7.log file if there is something that could help us?   Thomas Deml Senior Program Manager Internet Information Services Microsoft Corp.

• 09-24-2006, 12:32 AM

  In reply to

  jbristowe Joined on 09-21-2006, 3:32 PM Calgary, Alberta, Canada Posts 6	Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact ASP.NET "Atlas" was installed before I enabled ASP.NET in IIS 7.0. Is there an issue with ASP.NET "Atlas" and IIS 7.0? I looked in the IIS 7.0 logfile and found nothing of note.

• 09-24-2006, 6:01 AM

  In reply to

  synyan Joined on 09-24-2006, 9:57 AM Melbourne, Victoria, Australia Posts 1

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact Hey buddy, did you enable all services on RC1? See this: http://www.netomatix.com/Development/IIS7_404Error.aspx I met the same problem like you and after 2 hrs Googling and testing I found out that the problem is because when you click on the IIS7 checkboxes in Vista RC1, it is actually that you didn't select all sub-items like Asp.net all so. Hence you need to expand all of them, or you need to click again.

  Tags: rc1vistaiisaspx

• 09-24-2006, 8:55 AM

  In reply to

  jbristowe Joined on 09-21-2006, 3:32 PM Calgary, Alberta, Canada Posts 6	Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact Yes, the necessary services are enabled.

• 09-25-2006, 12:16 PM

  In reply to

  bills Joined on 02-03-2006, 5:33 PM Redmond, WA Posts 430	Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact does your web.config for Default Web Site clear the system.webServer/handlers section?  Is there a location tag in applicationHost.config for Default Web Site which clears it? bill ~~~~~~~~~~~~~~~~~~~~~~~~ Bill Staples Product Unit Manager, IIS blog: http://blogs.iis.net/bills

• 09-26-2006, 12:12 PM

  In reply to

  jbristowe Joined on 09-21-2006, 3:32 PM Calgary, Alberta, Canada Posts 6

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact The web.config file for the Default Web Site does not clear the system.webServer/handlers section. However, there is a location tag in applicationHost.config for the Default Web Site which does: <configuration>  <!-- ... -->  <location path="Default Web Site">   <system.webServer>    <handlers>     <clear />     <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="" />    </handlers>    <!-- ... -->   </system.webServer>  </location>  <location path="" overrideMode="Allow">   <system.webServer>    <handlers accessPolicy="Script, Read">     <clear />     <!-- ... -->     <add name="PageHandlerFactory-ISAPI-2.0" path="*.aspx" verb="GET,HEAD,POST,DEBUG" type="" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness32" />     <add name="PageHandlerFactory-ISAPI-1.1" path="*.aspx" verb="GET,HEAD,POST,DEBUG" type="" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv1.1,bitness32" />     <!-- ... -->    </handlers>    <!-- ... -->   </system.webServer>  </location> </configuration> Please note that certain sections were replaced with comments (<!-- ... -->) for readability.

• 09-26-2006, 4:17 PM

  In reply to

  bills Joined on 02-03-2006, 5:33 PM Redmond, WA Posts 430

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact interesting - that explains why you are not seeing an .aspx script map for Default Web Site.  It is possible that some tool or installer (maybe atlas) somehow cleared the handlers list at some point.  this looks like something ABOMapper may have written out.   Do you know what may have caused this to show up?  when did you first notice it? ~~~~~~~~~~~~~~~~~~~~~~~~ Bill Staples Product Unit Manager, IIS blog: http://blogs.iis.net/bills

• 09-27-2006, 6:59 PM

  In reply to

  jbristowe Joined on 09-21-2006, 3:32 PM Calgary, Alberta, Canada Posts 6	Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact This behaviour appeared as soon as I installed and enabled IIS 7.0. ASP.NET "Atlas" was installed before IIS 7.0.

• 10-12-2006, 5:07 PM

  In reply to

  manukahn Joined on 09-19-2005, 8:35 AM Posts 13

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact 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? manu@sela.co.il

  Tags: manu

• 10-16-2006, 1:12 PM

  In reply to

  danhop Joined on 10-16-2006, 5:08 PM Posts 1

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact I had a similar problem and ran across an blog here: http://www.west-wind.com/wconnect/weblog/ShowEntry.blog?id=493  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. - Dan

• 10-17-2006, 9:00 AM

  In reply to

  wongkyn Joined on 01-12-2003, 12:13 AM Posts 1

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact 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!  Nick Wong

• 10-23-2006, 1:51 AM

  In reply to

  mvolo Joined on 09-17-2003, 1:48 PM Philadelphia, PA Posts 583

  Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found) Reply Contact It sounds like several different problems.  Let me try to separate them: jbristowe - 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. manukahn - 1427193: You are having a similar issue.  I posted a (likely) solution on your other thread - .1437278 danhop - 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. wongkyn - 1431322: Are you any of the above? :)  If not, what is it? Thanks, Mike Volodarsky Program Manager IIS Core Server Visit mvolo.com for more inside information on IIS7, IIS and ASP.NET This posting is provided "AS IS" with no warranties, and confers no rights.