G
Guest
I have installed Vista B2, and IIS7, to include the subcategories under it.
I am trying to run a program that requires IIS. When I run the program, I
get the following 404.3 error:
___________________________________________________________________
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.
____________________________________________________________________
Reading the newsgroups, a possible fix is to run "aspnet_regiis -i". I did
this from Start-->Accessories-->Run, and found it by browsing in the
appropriate Microsoft.NET subfolder. However, the command failed, and the
command line window closed too fast for me to see the error. I have read
that commands from the Run box are not run with adminstrator privileges, and
this may be the problem. How do I do anything from the command line with
admin priviliges?
Alan
I am trying to run a program that requires IIS. When I run the program, I
get the following 404.3 error:
___________________________________________________________________
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.
____________________________________________________________________
Reading the newsgroups, a possible fix is to run "aspnet_regiis -i". I did
this from Start-->Accessories-->Run, and found it by browsing in the
appropriate Microsoft.NET subfolder. However, the command failed, and the
command line window closed too fast for me to see the error. I have read
that commands from the Run box are not run with adminstrator privileges, and
this may be the problem. How do I do anything from the command line with
admin priviliges?
Alan