IIS 7 & IIS 8
error 0x80070032 on iis 7.0 for .NET 2.0 project
Last post Oct 28, 2011 02:05 PM by sridhar2844
Jun 15, 2007 02:16 AM|LINK
Hi I am a complete noob with IIS 7.0, actually IIS in general but my project does work in Win XP SP2 IIS 5.1 with no probs.
However when I install Vista Business and setup IIS 7.0 it automatically referred to .NET 2.0 without installation, (not sure if it comes as a default).
When I try and run the site using
http://localhost/test/default.aspx I get the following 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
Requested URL: http://localhost:80/ets/bob.asp
Physical Path: C:\inetpub\wwwroot\ets\bob.asp
Logon User: Anonymous
Logon Method: Anonymous
Most likely causes:
It is possible that a handler mapping is missing. By default, the
static file handler processes all content.
The feature you are trying to use may not be installed.
The appropriate MIME map is not enabled for the Web site or
application. (Warning: Do not create a MIME map for content that users
should not download, such as .ASPX pages or .config files.)
What you can try:
Ensure that the expected handler for the current page is mapped.
Pay careful attention to preconditions (e.g. runtimeVersion,
pipelineMode, bitness) and compare them to the settings for your
Pay careful attention to typographical errors in the expected handler
Please verify that the feature you are trying to use is installed.
Verify that the MIME map is enabled or add the MIME map for the Web
site using the command-line tool appcmd.exe.
Open a command prompt and change directory to %windir%
To set a MIME type, use the following syntax: appcmd set config /
The variable fileExtension string is the file name extension and the
variable mimeType string is the file type description.
For example, to add a MIME map for a file which has the extension
".xyz", type the following at the command prompt, and then press
appcmd set config /section:staticContent /+
Warning: Ensure that this MIME mapping is needed for your Web server
before adding it to the list. Configuration files such as .CONFIG or
dynamic scripting pages such as .ASP or .ASPX, should not be
downloaded directly and should always be processed through a handler.
Other files such as database files or those used to store
configuration, like .XML or .MDF, are sometimes used to store
configuration information. Determine if clients can download these
file types before enabling them.
Create a tracing rule to track failed requests for this HTTP status
code. For more information about creating a tracing rule for failed
requests, click here.
More Information... This error occurs when the file extension of the
requested URL is for a MIME type that is not configured on the server.
You can add a MIME type for the file extension for files that are not
dynamic scripting pages, database, or configuration files. Process
those file types using a handler. You should not allows direct
downloads of dynamic scripting pages, database or configuration
I am not quite sure what the issue is as it wasn't that hard in IIS 5. I added default.aspx in the default parameters to look for if you don't type in the filename of the root folder.
Can anyone help with how I can overcome this issue, as I have absolutely no clue here.
thanks for any tips in advance
Ringo (aka blind venison)
Jun 15, 2007 09:19 AM|LINK
Make sure ASP is installed. By default, ASP is not installed with IIS.
Windows Server MVP - IIS
Log archival solution
Install, Configure, Forget
Jun 18, 2007 11:04 PM|LINK
I encounter the same exact error.
I have all components of IIS 7 installed. I'm running Windows Vista Home Premium with all applicable updates.
There are several posts floating around out there for people who have encountered this and other errors while using IIS 7 in Vista Home Premium.
Any ideas based on that info?? Thanks! :0
Jun 19, 2007 12:29 AM|LINK
You say you requested default.aspx but the error indicates that you requested bob.asp. Are you getting 404.3 for default.aspx and bob.asp? Static file module is handling the asp, aspx requests on your machine. That means either you don't have asp and asp.net
installed on your machine or your system.webServer/handlers configuration is not correct. Can you make sure you have the components installed on the machine first?
Jun 21, 2007 08:18 AM|LINK
Sorry for the misleading info.
A post that I found was exactly the same error as I was getting but it related to default.aspx not bob.asp.
I wasn't at home where my computer was and I needed to get the post online to get info so that I could resolve it asap.
does this shed some light on the issue so that I could possibly get someones help ?
thanks in advance
Jun 21, 2007 03:44 PM|LINK
Ok have had a chance to look at the issue further and I had to do the following:
First of all I had to put it back to the Pipeline mode as I believe I had it in Classic mode when setting up the virtual application. (sorry if all the terminology is wrong as it is on another machine that is now shut down and I need some sleep)
I then tried it and I ended up with a 500 server error and it suggested that I add <identity impersonate="false" /> in the first choice to fix the error (from 3 options) as it sounded like it suggested impersonatioon was only avail in .NET 3.0?
Anywayz, it has got the problem sorted. It isn't or wasn't as hard as I had thought even for a noob like me.
The error handling messages are fantastic and give some very good suggestions; my hat goes off to the developers just on this alone.
thanks, problem now sorted.
Mar 20, 2008 01:27 PM|LINK
One more additional comment. I'd done everything everyone suggested to no avail. Finally, changed one thing in IIS Manager, and fixed the problem.
I added the .aspx extension in MIME Types, with text/html as the MIME Type. Even though I'd installed asp services, it didn't put this type in IIS, so it was unrecognized.
After a day of pulling my hair out, finally figured this one out.
Mar 20, 2008 03:08 PM|LINK
This is the wrong thing to do, you are opening a security hole on the server and will cause the source code for your aspx pages to be downloaded rather than the result of the script execution.
Mar 20, 2008 03:26 PM|LINK
Then what would the right thing to do be? I couldn't get this to work any other way.
One note - my development machine is Vista, whereas our webserver is Server 2003. Don't know if we'll see the same issues on iis 6.0.
Mar 20, 2008 04:39 PM|LINK
You need to install ASP.Net from control panel -> programs and features -> turn windows features on or off under IIS - this will add the correct handler mapping for asp.net content including .aspx extension