I experienced a similiar issue, however I cannot confirm that the .NET Extensibility, ASP, ASP.NET, ISAPI Extensions, ISAPI Filters were installed before installing Atlas RTM.
Here is my order for (possibly) repro'ing this problem, should it exist:
I had the same problem with a <clear /> tag being in my handlers section (I upgraded to Vista from XP SP2). When I removed the <clear /> tag and tried to access my default web site I got a configuration error complaining about a duplicate entry. I put
back in the <clear /> tag and added a script map ASPNET-ISAPI-2.0-PageHandlerFactory for *.aspx to point to C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll and now my default site works. I do have a some questions.
I notice that there are ASPNET-ISAPI-1.1 maps for *.axd, *.rem, *.soap, *.ashx, and *.asmx.
1. Should I put in 2.0 maps for those?
2. Are there any other 2.0 specific maps I should add?
3. Is there a list somewhere of what the IIS 7.0 default web site mappings should be with a clean install?
There should be a copy of the clean-install applicationhost.config in the inetsrv\config directory.
Thanks. If that applicationhost.config.clean.install file is what is reall used, then that means that even deleting the <clean /> tags would not have helped as it has no Framework 2.0 handlers defined in the file. How do these get into IIS 7.0? I can't
believe that everyone has to put them in manually.
By the way, now that I have the 2.0 stuff working, my 1.1 applications now just give me "Bad Request" for the first attempt and "Server Application Unavailable" when I hit the reload button. It also puts an entry in the application log "Failed to execute
request because the App-Domain could not be created. Error: 0x80131522". There seem to be a lot of hits on that error for a search but I haven't found one that works for me yet.
By the way, now that I have the 2.0 stuff working, my 1.1 applications now just give me "Bad Request" for the first attempt and "Server Application Unavailable" when I hit the reload button. It also puts an entry in the application log "Failed to execute request
because the App-Domain could not be created. Error: 0x80131522". There seem to be a lot of hits on that error for a search but I haven't found one that works for me yet.
This is getting to be like Whack-A-Mole!
OK, I found a way to fix the problem. I had this in the ASP.NET 1.1 Application Pool which seemed reasonable to me because it was the only 1.1 Pool. I moved it into AppPool_Medium which has "No Managed Code" for the .NET Framework Version and the "Bad
Request" etc. errors went away. It also seems to run OK regardless if the Managed Pipeline is set to either Classic or integrated.
I must say that on the surface it appears very counter-intuitive that 1.1 code wouldn't run in an application pool with the framework version set to 1.1. Anybody got an explanation or a reference that explains why this is the case?
How IIS7 upgrade works is that, it does an install of IIS and then brings over all the downlevel settings - the reason asp.net mappings are not there in the clean-install file is that asp.net is not included in the install that upgrade does before bringing
over the down-level settings.
Also, on IIS6 (and earlier versions), the way to use different versions of asp.net on the server was to change the ScriptMaps on each of the site to point to the right version, which soon leads to a lot of scriptmaps and management problems, the new better
IIS7 way has ScriptMaps (handlers) of all asp.net versions in the global defaults with preconditions and then which asp.net version gets run gets chosen by setting on the app-pool that the app resides in.
An upgrade (to maintain most compatibility, and because there is only so much time we want to spend on writing upgrade code) leaves things in the state IIS6 was in, so you get each app with its own ScriptMap (with no preconditions), so the settings on the
app-pool really have no affect. Also, this means that any changes you do to the global handlers list have no effect.
I think you will be more happy long-term if you save the current applicationhost.config - completely uninstall IIS (including Windows Process Activation Service) and do a clean-install - then create the apps and app-pools you want and set the app-pool settings
to the right asp.net version/pipeline mode etc. The resulting config file will be much more managable in the future in terms of moving apps from one version to another or adding new apps for various versions.
Anil Ruia
Software Design Engineer
IIS Core Server
I'm having a the same error on vista home premium however my laptop with vista business is working fine. I do not have "atlas" installed, unless it is done by default as I'm not even sure what "atlas" is.
Both machines have asp enabled but the home premium machine will not serve up the required .aspx page. In my case it does seem related to the application since I have other .aspx pages which do work, they are in different application pools and from different
vendors.
My main and underlying question and concern is why does it work on the vista business machine and not on the vista home machine?
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
Notification: ExecuteRequestHandler
Module: StaticFileModule
Requested URL: http://localhost:80/default.aspx
Physical Path: E:\inetpub\wwwroot\default.aspx
Logon User: Anonymous
Logon Method: Anonymous
Handler: StaticFile
-----
now what can i do to fix this problem putting into consideration that i have enabled everything in the Application Development features in the World Wide Web Services in the IIS from Turn on Windows features.
Can any one give me simple answer or guide on how to solve this,
ok i think i found out what was my problem but still i need some professional opinion, it was the handlers, I opened my default website from the iis manager and opened the handler mappings, clicked add managed handler, Request path : " *.aspx ", Type : " System.Web.DefaultHttpHandler
", and for name i typed " ASPX ", then i ran my localhost/default.aspx, et voila, it's workin.
Kindly correct me if i am wrong
my problem now is that before i do that i uninstalled and reinstalled the iis 7 , and deleted the web.config and other files from the wwroot directory, Is there a default web.config to start with or where can i find the basic web.config that is created for
the first time
damart
1 Post
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Feb 13, 2007 04:35 PM|LINK
I experienced a similiar issue, however I cannot confirm that the .NET Extensibility, ASP, ASP.NET, ISAPI Extensions, ISAPI Filters were installed before installing Atlas RTM.
Here is my order for (possibly) repro'ing this problem, should it exist:
1. Install VS2005
2. Install Atlas RTM
3. Install IIS
Hope this helps
wbhyde
5 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Apr 20, 2007 06:01 PM|LINK
I had the same problem with a <clear /> tag being in my handlers section (I upgraded to Vista from XP SP2). When I removed the <clear /> tag and tried to access my default web site I got a configuration error complaining about a duplicate entry. I put back in the <clear /> tag and added a script map ASPNET-ISAPI-2.0-PageHandlerFactory for *.aspx to point to C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll and now my default site works. I do have a some questions.
I notice that there are ASPNET-ISAPI-1.1 maps for *.axd, *.rem, *.soap, *.ashx, and *.asmx.
1. Should I put in 2.0 maps for those?
2. Are there any other 2.0 specific maps I should add?
3. Is there a list somewhere of what the IIS 7.0 default web site mappings should be with a clean install?
Thanks,
Bill
vista aspx aspnet iis7 handlers
anilr
2343 Posts
Microsoft
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Apr 20, 2007 06:45 PM|LINK
Software Design Engineer
IIS Core Server
wbhyde
5 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Apr 21, 2007 02:50 PM|LINK
Thanks. If that applicationhost.config.clean.install file is what is reall used, then that means that even deleting the <clean /> tags would not have helped as it has no Framework 2.0 handlers defined in the file. How do these get into IIS 7.0? I can't believe that everyone has to put them in manually.
By the way, now that I have the 2.0 stuff working, my 1.1 applications now just give me "Bad Request" for the first attempt and "Server Application Unavailable" when I hit the reload button. It also puts an entry in the application log "Failed to execute request because the App-Domain could not be created. Error: 0x80131522". There seem to be a lot of hits on that error for a search but I haven't found one that works for me yet.
This is getting to be like Whack-A-Mole!
wbhyde
5 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Apr 21, 2007 04:53 PM|LINK
OK, I found a way to fix the problem. I had this in the ASP.NET 1.1 Application Pool which seemed reasonable to me because it was the only 1.1 Pool. I moved it into AppPool_Medium which has "No Managed Code" for the .NET Framework Version and the "Bad Request" etc. errors went away. It also seems to run OK regardless if the Managed Pipeline is set to either Classic or integrated.
I must say that on the surface it appears very counter-intuitive that 1.1 code wouldn't run in an application pool with the framework version set to 1.1. Anybody got an explanation or a reference that explains why this is the case?
"ASP.NET" Configuration "IIS 7.0" aspx "Application Pools"
anilr
2343 Posts
Microsoft
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Apr 21, 2007 10:19 PM|LINK
How IIS7 upgrade works is that, it does an install of IIS and then brings over all the downlevel settings - the reason asp.net mappings are not there in the clean-install file is that asp.net is not included in the install that upgrade does before bringing over the down-level settings.
Also, on IIS6 (and earlier versions), the way to use different versions of asp.net on the server was to change the ScriptMaps on each of the site to point to the right version, which soon leads to a lot of scriptmaps and management problems, the new better IIS7 way has ScriptMaps (handlers) of all asp.net versions in the global defaults with preconditions and then which asp.net version gets run gets chosen by setting on the app-pool that the app resides in.
An upgrade (to maintain most compatibility, and because there is only so much time we want to spend on writing upgrade code) leaves things in the state IIS6 was in, so you get each app with its own ScriptMap (with no preconditions), so the settings on the app-pool really have no affect. Also, this means that any changes you do to the global handlers list have no effect.
I think you will be more happy long-term if you save the current applicationhost.config - completely uninstall IIS (including Windows Process Activation Service) and do a clean-install - then create the apps and app-pools you want and set the app-pool settings to the right asp.net version/pipeline mode etc. The resulting config file will be much more managable in the future in terms of moving apps from one version to another or adding new apps for various versions.
Software Design Engineer
IIS Core Server
rdumont
1 Post
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Oct 20, 2007 02:55 PM|LINK
I'm having a the same error on vista home premium however my laptop with vista business is working fine. I do not have "atlas" installed, unless it is done by default as I'm not even sure what "atlas" is.
Both machines have asp enabled but the home premium machine will not serve up the required .aspx page. In my case it does seem related to the application since I have other .aspx pages which do work, they are in different application pools and from different vendors.
My main and underlying question and concern is why does it work on the vista business machine and not on the vista home machine?
Any help would be much appreciated.
Rob
Bosbos
10 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Nov 15, 2008 12:05 AM|LINK
Hi everyone, thx for the the effort, but i just dont get it, whats causing this problem?
i have IIS7 installed on a Vista Ultimate and I use VWD2008 Express.
Whenever i try to goto " http://localhost/default.aspx " , i get this error:
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
Notification: ExecuteRequestHandler
Module: StaticFileModule
Requested URL: http://localhost:80/default.aspx
Physical Path: E:\inetpub\wwwroot\default.aspx
Logon User: Anonymous
Logon Method: Anonymous
Handler: StaticFile
-----
now what can i do to fix this problem putting into consideration that i have enabled everything in the Application Development features in the World Wide Web Services in the IIS from Turn on Windows features.
Can any one give me simple answer or guide on how to solve this,
THX
Bosbos
10 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Nov 15, 2008 10:11 PM|LINK
ok i think i found out what was my problem but still i need some professional opinion, it was the handlers, I opened my default website from the iis manager and opened the handler mappings, clicked add managed handler, Request path : " *.aspx ", Type : " System.Web.DefaultHttpHandler ", and for name i typed " ASPX ", then i ran my localhost/default.aspx, et voila, it's workin.
Kindly correct me if i am wrong
my problem now is that before i do that i uninstalled and reinstalled the iis 7 , and deleted the web.config and other files from the wwroot directory, Is there a default web.config to start with or where can i find the basic web.config that is created for the first time
thx
shijo4567
7 Posts
Re: ASP.NET Configuration (HTTP Error 404.3 - Not Found)
Jan 20, 2011 07:54 AM|LINK