Iis7 error HTTP Error 404.4-not found

First paste the error details

Error details

Error Summary
HTTP 404.4-not found
The resource you want to search for does not have a handler associated with it.

Detailed error message
Module IIS Web Core
Notification maprequesthandler
The handler has not been determined
Error code 0x80070002

Request URL http: // localhost: 80/
Physical path D:/project/iisroot/website
Logon method Anonymous
Anonymous login user

The most likely cause is:
No handler is configured for the file extension of the requested URL to process requests on the Web server.

Possible operations:
If the file extension does not have a handler associated with it, add a handler ing for the extension.
Make sure that the handler associated with the file extension name is correctly installed and configured.
Create a trail rule to track failed requests for this HTTP status code. For more information about creating tracing rules for failed requests, click here.

Link and more information

 

Access the test program default. aspx under this website directory through this address http: // localhost/default. aspx can be accessed normally, I want to view the virtual directory now

When an error occurs during access through http: // localhost, the above error occurs. I have enabled the directory browsing function in IIS.

 

Possible HTTP error causes and solutions .... I have seen a solution for all iis7 errors on the Microsoft page. I cannot find it now. I will try again later.

First, describe the basic information. The system is Vista Ultimate. (iis7 has been installed properly, ASP, Asp.net. This option is selected during installation, if you do not know the function, select ..) In the IIS system directory c:/Windows/system32/intersrv/, you can find static. DLL file. In the operating system version, if the system is Vista Home Basic, this HTTP Error 404 will also occur when iis7 is configured. This problem cannot be solved. You must change the system version, because Vista Home Basic features are rarely restricted and iis7.ultimate cannot be used, this is not the case.

Next, I mentioned that Microsoft has an HTTP Error solution. I will refer to the HTTP Error 404.4 solution as follows:

 

To solve this problem, add the file extension as the requested URL Handler ing. Follow the steps below to addStaticfileHandler ing operation:

1. Start IIS manager. To do this, clickStart, ClickRun, Type inetmgr.exe, and then clickOK.
2. In the IIS manager, expandServer NameExpandWeb Site, Click the website you want to modify.
3. InFunction View, Double-clickHandler ing.
4. InHandler ingRight-click in the paneStaticfileAnd then clickEdit.
5. InEdit module ingIn the dialog box, enter * inRequest PathBox, and then clickOK.

Note:After performing these steps, you can successfully access static files. For example, you can successfully access a file with the following file extensions:

• . Htm
• . Html
• . Jpg
• . Gif
• . PNG

Back to TopIf maprequesthandler is notified to search for ing or filter, adding such filter by online search will not work. In fact, this is not my case. The staticfile module does not exist in the root module when I open my handler. Now there is a direction for the problem. If my iis7 lacks staticfile, start with the staticfile module. After searching the Internet, there is a post in the forums.foiis.net website that mentions manually adding the staticfile module. OK. now, manually add this module by referring to other people's configurations. 1. In the handler ing, refer to the following

Request Path:

*

 

Module:

Staticfilemodule, defadocumentdocumentmodule, directorylistingmodule

 

Name

Staticfile

 

Request restrictions:

File or folder

After this addition, I found that my staticfile module was not recognized at all, but this solution was aborted.

2. modify the configuration file C:/Windows/system32/intersrv/config/applicationhost. config. Normally, the configuration file contains two staticfile nodes.

I don't have either of them. Here I also refer to the cultivation and modification of others. I will add the <staticfile> module and save it.

Now let's look at http: // localhost and give me an HTTP Error 500.21. This is fine. Just like the above method, the system prompts an error: Unrecognized module staticfile... Now, you can browse http: // localhost/default. aspx, and the scheme is aborted.

I have tried other methods that are too messy. In the end, I had to uninstall vs2008, sql2008, and iis7. Then I can install iis7 first and use it after installation. This is the problem with his mother, angry! It is true that Microsoft is not compatible with your own products. If it is not compatible, an irrelevant error message is returned, it's annoying to pull the problem direction to the wrong direction!

In short, the root cause is that the installation sequence of iis7 and. NET is incorrect. This problem occurs when you install Vs and IIS first. Install iis7 first and then. Blood lessons

In addition, the installation sequence of sql2008 and vs2008 may also cause inexplicable errors...