Home > Forums › IIS 7 › IIS 7 - FastCGI Module › Thread MODULE_SET_RESPONSE_ERROR_STATUS Warning

Thread: Thread MODULE_SET_RESPONSE_ERROR_STATUS Warning

Last post 11-14-2008 2:22 PM by Manijuneja. 4 replies.

Average Rating Rate It (5)Thank you for the rating!

RSS

Page 1 of 1 (5 items)

Sort Posts:

Shortcuts

Search | Active Posts | Unanswered Posts | View all users

11-13-2008, 3:40 PM

Manijuneja
Joined on 11-13-2008, 3:34 PM
Posts 6

Thread MODULE_SET_RESPONSE_ERROR_STATUS Warning

Reply Contact

I am getting this error in windows server 2008

ModuleName="StaticFileModule",

Notification="EXECUTE_REQUEST_HANDLER", HttpStatus="404",

 HttpReason="Not Found", HttpSubStatus="3", ErrorCode="The request is not supported.
 (0x80070032)", ConfigExceptionInfo=""

Plz help me in that

Thanx

11-13-2008, 8:06 PM In reply to

ksingla
Joined on 06-14-2006, 3:02 AM
Redmond, WA
Posts 863

Re: Thread MODULE_SET_RESPONSE_ERROR_STATUS Warning

Reply Contact

What is the URL you are requesting? 404.3 happens when static file handler handles the request but the extension is not there in mimemap list. Either set the handler or add the extension to mimemap list if static file handler should be serving it.

Thanks,
Kanwal

Follow me on twitter at http://twitter.com/kjsingla

11-13-2008, 10:47 PM In reply to

Manijuneja
Joined on 11-13-2008, 3:34 PM
Posts 6

Re: Thread MODULE_SET_RESPONSE_ERROR_STATUS Warning

Reply Contact

http://localhost/login.php

and how to set ectension for php

I am getting this on --http://localhost/login.php

HTTP Error 404.3 - Not Found

The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

Detailed Error Information

Module	StaticFileModule
Notification	ExecuteRequestHandler
Handler	StaticFile
Error Code	0x80070032

Requested URL	http://localhost:80/login.php
Physical Path	C:\inetpub\wwwroot\login.php
Logon Method	Anonymous
Logon User	Anonymous
Failed Request Tracing Log Directory	C:\inetpub\logs\FailedReqLogFiles

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.)
If ASP.NET is not installed.

Things you can try:

In system.webServer/handlers:
- Ensure that the expected handler for the current page is mapped.
- Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
- Pay extra attention to typographical errors in the expected handler line.
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.
1. To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']
2. The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
3. For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']
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.
Install ASP.NET.
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.

Links and 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 files.

View more information »