I've been trying to follow the instructions in this post, but I'm having
trouble. I'm not familiar with server operations, and I have one program
requiring it, giving me the dreaded 404.3 error.

I have installed Vista b2, and IIS from the add/remove programs, to include
all the subcategories. When I try to start my program, I get the following
error page:

__________________________________________________________________

Server Error in 'Default Web Site' Application.

--------------------------------------------------------------------------------

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 therefore is not allowed.

Error Code: 0x80070032

Notification: ExecuteRequestHandler

Module: StaticFileModule

Requested URL: http://localhost:80/Web-Link/default.asp

Physical Path: C:\inetpub\wwwroot\Web-Link\default.asp

Logon User: Anonymous

Logon Method: Anonymous

Handler: StaticFile

Causes:

The appropriate MIME map is not enabled for the web site or application
Solution:

Verify that the MIME map is enabled or add the MIME map for the site.
From the Web Management tool, open a connection to the website.
Double click the MIME Types Management feature.
Verify that the MIME type is in the list and is not set to Removed.
If the MIME type is in the list and set to Removed, highlight the MIME Type
in the list, and in the MIME Types Tasks, click Restore.
If the MIME Type is not in the list, complete the MIME Type information in
the Tasks pane under New MIME Type, and then click Add.
NOTE: Make sure that this MIME mapping is needed for your Web server before
adding it to the list.
Set up a new Failed Request Trace rule for this HTTP status code.
Use the IIS Web Management tool to open a connection to the Web server where
the problem is occurring.
In the tree view, navigate to the Web site, and then click to select it.
In the Tasks pane, click Failed Request Tracing.
Check Enable Logging for this Site, specify a logging folder or use the
default log folder, and then click OK
Open the Failed Request Tracing Rules feature and click New Rule in the
Tasks pane.
Specify the content type to monitor and then click Next.
Check the Status Codes checkbox, type 404.3 in the Edit box, and then click
Next.
In the Providers area, make sure that the WWW Server is checked and
highlighted, and that in Provider Properties, the Verbosity level is set to
Verbose.
Click FinishRequest the page that generated the 404.3 error and then look at
the tracing file that was created for the request. This file is located in
the logging folder you specified in Step 4.
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.

Microsoft Knowledge Base Articles:


--------------------------------------------------------------------------------
Server Version Information: Internet Information Services 7.0.
_____________________________________________________________________

After reading the post, I tried to run the "aspnet_regiis -i" command from
the Accessories-->Run prompt. It fails, and the command line window is gone
so quickly that I can't read the error message. Can anyone get me past this?
I have heard that the Run command does not allow administrator priviliges,
and this may be part of the problem. Is there a way to use this command with
admin priviliges?

Alan




"Cal Learner" wrote:

> Success at last. Thanks for your suggestions and comments. In the course of 1
> week futzing around with this problem, many suggestions were tried, and
> probably helped contribute to the solution. Eventually, the correction came
> by following KB 309051 ("Troubleshooting ASP in IIS 5.0"), and in particular,
> deleting the IIS packages in Component Services of MMC. In my case, only 1 of
> the required 3 packages was present to begin with (IIS Utilities). I was
> missing the out-of-process and in-process packages. Once deleted, I
> re-created the packages and did the other steps in paragraph #6 of that KB
> article, then reset IIS and voila! Hope this helps others who have this issue.
>
>
> "Cal Learner" wrote:
>
> > Recently got a new box running Win MCE (2002). Installed IIS components
> > without any trouble, and it appears that all of the required directories
> > (inetpub, wwwroot, etc) are in place, as are iisstart.asp and localstart.asp.
> > The network is functioning; I pinged localhost and computer_name and
> > everything ran as it should. Any html file serves just fine through
> > http://localhost/. The problem is that it will not serve any .asp files,
> > including localstart.asp. I keep getting the error 500 white screen. Even
> > unchecking the friendly error messages doesn't give me anything useful. I've
> > been all through the MMC a dozen times looking for anything unusual. The
> > default web is there. I don't know exactly what the permissions should be set
> > to, but this is a development system for me only, and I'm logged on as an
> > administrator, so that should not be the problem. Some versions of IIS
> > apparently allow you to designate which file extensions to allow and which to
> > block. (V6.0 apparently comes locked down, so the ASP extension has to be
> > selected, but I can't find anything similar in v5.1.)
> >
> > I give up. What's left to consider? I've done this on previous machines (XP
> > Pro) and don't remember having these sorts of mysteries on my hands. Please
> > offer the most likely steps I should take to resolve this. It just can't be
> > as hard as I've made it!

Open a command prompt window first, then run the command. The window will stay open and you can see any resulting error messages. You may also want to post your question to the Windows Vista newsgroups, as the product is still in beta, and that is where support is offered.

Additionally a Google search returned this result

http://www.netomatix.com/Development/IIS7_404Error.aspx

--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display\Security
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"DocInTheBox" <DocInTheBox@discussions.microsoft.com> wrote in message news:99DDAE65-CBCF-4722-B861-83EC01541095@microsoft.com...
> I've been trying to follow the instructions in this post, but I'm having
> trouble. I'm not familiar with server operations, and I have one program
> requiring it, giving me the dreaded 404.3 error.
>
> I have installed Vista b2, and IIS from the add/remove programs, to include
> all the subcategories. When I try to start my program, I get the following
> error page:
>
> __________________________________________________________________
>
> Server Error in 'Default Web Site' Application.
>
> --------------------------------------------------------------------------------
>
> 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 therefore is not allowed.
>
> Error Code: 0x80070032
>
> Notification: ExecuteRequestHandler
>
> Module: StaticFileModule
>
> Requested URL: http://localhost:80/Web-Link/default.asp
>
> Physical Path: C:\inetpub\wwwroot\Web-Link\default.asp
>
> Logon User: Anonymous
>
> Logon Method: Anonymous
>
> Handler: StaticFile
>
> Causes:
>
> The appropriate MIME map is not enabled for the web site or application
> Solution:
>
> Verify that the MIME map is enabled or add the MIME map for the site.
> From the Web Management tool, open a connection to the website.
> Double click the MIME Types Management feature.
> Verify that the MIME type is in the list and is not set to Removed.
> If the MIME type is in the list and set to Removed, highlight the MIME Type
> in the list, and in the MIME Types Tasks, click Restore.
> If the MIME Type is not in the list, complete the MIME Type information in
> the Tasks pane under New MIME Type, and then click Add.
> NOTE: Make sure that this MIME mapping is needed for your Web server before
> adding it to the list.
> Set up a new Failed Request Trace rule for this HTTP status code.
> Use the IIS Web Management tool to open a connection to the Web server where
> the problem is occurring.
> In the tree view, navigate to the Web site, and then click to select it.
> In the Tasks pane, click Failed Request Tracing.
> Check Enable Logging for this Site, specify a logging folder or use the
> default log folder, and then click OK
> Open the Failed Request Tracing Rules feature and click New Rule in the
> Tasks pane.
> Specify the content type to monitor and then click Next.
> Check the Status Codes checkbox, type 404.3 in the Edit box, and then click
> Next.
> In the Providers area, make sure that the WWW Server is checked and
> highlighted, and that in Provider Properties, the Verbosity level is set to
> Verbose.
> Click FinishRequest the page that generated the 404.3 error and then look at
> the tracing file that was created for the request. This file is located in
> the logging folder you specified in Step 4.
> 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.
>
> Microsoft Knowledge Base Articles:
>
>
> --------------------------------------------------------------------------------
> Server Version Information: Internet Information Services 7.0.
> _____________________________________________________________________
>
> After reading the post, I tried to run the "aspnet_regiis -i" command from
> the Accessories-->Run prompt. It fails, and the command line window is gone
> so quickly that I can't read the error message. Can anyone get me past this?
> I have heard that the Run command does not allow administrator priviliges,
> and this may be part of the problem. Is there a way to use this command with
> admin priviliges?
>
> Alan
>
>
> "Cal Learner" wrote:
>
>> Success at last. Thanks for your suggestions and comments. In the course of 1
>> week futzing around with this problem, many suggestions were tried, and
>> probably helped contribute to the solution. Eventually, the correction came
>> by following KB 309051 ("Troubleshooting ASP in IIS 5.0"), and in particular,
>> deleting the IIS packages in Component Services of MMC. In my case, only 1 of
>> the required 3 packages was present to begin with (IIS Utilities). I was
>> missing the out-of-process and in-process packages. Once deleted, I
>> re-created the packages and did the other steps in paragraph #6 of that KB
>> article, then reset IIS and voila! Hope this helps others who have this issue.
>>
>>
>> "Cal Learner" wrote:
>>
>> > Recently got a new box running Win MCE (2002). Installed IIS components
>> > without any trouble, and it appears that all of the required directories
>> > (inetpub, wwwroot, etc) are in place, as are iisstart.asp and localstart.asp.
>> > The network is functioning; I pinged localhost and computer_name and
>> > everything ran as it should. Any html file serves just fine through
>> > http://localhost/. The problem is that it will not serve any .asp files,
>> > including localstart.asp. I keep getting the error 500 white screen. Even
>> > unchecking the friendly error messages doesn't give me anything useful. I've
>> > been all through the MMC a dozen times looking for anything unusual. The
>> > default web is there. I don't know exactly what the permissions should be set
>> > to, but this is a development system for me only, and I'm logged on as an
>> > administrator, so that should not be the problem. Some versions of IIS
>> > apparently allow you to designate which file extensions to allow and which to
>> > block. (V6.0 apparently comes locked down, so the ASP extension has to be
>> > selected, but I can't find anything similar in v5.1.)
>> >
>> > I give up. What's left to consider? I've done this on previous machines (XP
>> > Pro) and don't remember having these sorts of mysteries on my hands. Please
>> > offer the most likely steps I should take to resolve this. It just can't be
>> > as hard as I've made it!