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:
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.
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
Group Program Manager
Internet Information Services
Microsoft Corp.
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 apps APP "Default Web Site/" (applicationPool:DefaultAppPool)
APP "Default Web Site/Hello" (applicationPool:DefaultAppPool)
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:
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?
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
Group Program Manager
Internet Information Services
Microsoft Corp.
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.
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?
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:
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?
jbristowe
6 Posts
ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 21, 2006 04:41 PM|LINK
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:
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:
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.
"ASP.NET" Configuration "IIS 7.0"
thomad
552 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 21, 2006 08:02 PM|LINK
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.
Group Program Manager
Internet Information Services
Microsoft Corp.
jbristowe
6 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 21, 2006 10:16 PM|LINK
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:
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:
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!
thomad
552 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 21, 2006 10:50 PM|LINK
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?
Group Program Manager
Internet Information Services
Microsoft Corp.
jbristowe
6 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 24, 2006 04:32 AM|LINK
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.
synyan
1 Post
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 24, 2006 10:01 AM|LINK
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.
rc1 vista iis aspx
jbristowe
6 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 24, 2006 12:55 PM|LINK
Yes, the necessary services are enabled.
bills
433 Posts
Microsoft
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 25, 2006 04:16 PM|LINK
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
jbristowe
6 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 26, 2006 04:12 PM|LINK
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:
Please note that certain sections were replaced with comments (<!-- ... -->) for readability.
bills
433 Posts
Microsoft
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Sep 26, 2006 08:17 PM|LINK
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