1. The request filtering module is configured to reject requests that contain double escape sequences. HTTP Error 404.11 - Not Found
1. Click Start. In the Start Search box, type Notepad. Right-click Notepad and click Run as administrator.
Note If prompted for an administrator password or for confirmation, type the password, or click Continue.
2. On the File menu, click Open. In the File name box, type %windir%\system32\inetsrv\config\applicationhost.config and click Open.
3. In the ApplicationHost.config file, locate the configuration/system.webServer/security/requestFiltering/ file under configuration/system.webServer/security/requestFiltering/
<requestFiltering> nodes. About 360 lines
<requestFiltering>will
Change
<requestFiltering allowDoubleEscaping="true">
That's it
2. Solution to IIS 7.0 Error in Uploading Large Files (Description: The request filtering module is configured to reject requests that exceed the length of the request content)
When uploading large files using IIS7.0 asp, the following error occurs:
HTTP Error 404.13 - Not Found
Description: The Request Filtering module is configured to reject requests that exceed the length of the request content.
Error code: 0x00000000
Notification: BeginRequest
Module: RequestFilteringModule
Requested URL: http://localhost:80/u2/upfile.asp
Physical path: G:\web\u2\upfile.asp
Logged in users: Not yet determined
Login method: Not yet determined
Processor: ASPClassic
Most likely causes:
Request filtering on the web server is configured to deny the request because the content length exceeds the configured value.
What to try:
Confirm the configuration/system.webServer/security/requestFiltering/requestLimits@maxAllowedContentLength setting in the applicationhost.config or web.config file.
Access is running an Internet Information Services 7.0 server hosting a web site with an error message: "HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE"
The solution is as follows
To resolve this issue, follow these steps:
1. Click Start. In the Start Search box, type Notepad. Right-click Notepad and click Run as administrator.
Note If prompted for an administrator password or for confirmation, type the password, or click Continue.
2. On the File menu, click Open. In the File name box, type %windir%\system32\inetsrv\config\applicationhost.config and click Open.
3. In the ApplicationHost.config file, locate the < requestLimits > node.
4. Delete the maxAllowedContentLength property. Alternatively, add a value that matches the Content-Length header and the client sends the request as the size. By default, the value of the maxAllowedContentLength property is 30000000.
For example, modify the following code.
<requestLimits maxAllowedContentLength ="<length>" />
5. Save the ApplicationHost.config file.
In fact, the default error in II7.0 has already told us how to do it, hehe, this is much more user-friendly than IIS6.0.
After modification, type iisreset on the cmd command line to restart IIS (or directly use IIS Manager to restart), and the error still occurs when re-uploading the file.
But this is the traditional mistake.
In IIS6.0, you need to do the following operations (see: Breaking through IIS6 upload and download file size***)
Workaround:
Start by stopping the IIS service, then open metabase.XML in C:\Windows\System32\Inetsrv and modify AspMaxRequestEntityAllowed to the value you need (e.g. 1073741824, 1GB).
Start the IIS service.
In IIS 7.0, the built-in ASP module already has this property, which can be directly modified
The steps are as follows:
Click the name of the required site - double-click on the ASP module in the "Function View", open the "*** Properties", and change the last item "Maximum Request Entity Body ***[maxRequestEntityAllowed]" to the value you need (e.g. 1073741824, 1GB).
Also, please note that if you upload a large file, please consider whether the "scriptTimeOut" needs to be changed.
The default is 00:01:30, yaosansi has changed it to 00:05:30, of course you can also change the timeout time in the ASP program.
3. Server Error HTTP Error 404.3 - Not Found in the Application Description: The requested page cannot be processed due to the Multipurpose Internet Mail Extensions (MIME) mapping policy configured on the web server. The page you requested has an unrecognized file extension and is therefore not allowed.
Error code: 0x80070032
Most likely causes:
It could be that the handler mapping is missing. By default, static file handlers will handle everything.
The feature you want to use may not already be installed.
The corresponding MIME mapping is not enabled for websites or applications. (Warning: Please do not download . ASPX pages or .config files create MIME maps. )
Possible actions: System disk: \windows\ServiceProfiles\NetworkService\AppData\Local\Temp Add a read/write license of "Autheticated Users" to this directory.
Modifications:
C:\Windows\System32\inetsrv\config\applicationHost.config
Original text of line 108 of the document:
<processModel identityType="NetworkService" />
Modified to:
<processModel identityType="NetworkService" loadUserProfile="false" />
4. IIS7.0 ASP cannot connect to the Access database normally
Before solving this problem, let's talk about the configuration of Vista IIS7.0 ASP environment, if IIS is installed by default, then the ASP program cannot run, when opening a file with an extension of .ASP in IE, IIS will be displayed as an ordinary web file. Looking at the source code of the file in IE, you can see all the original code of the ASP file, just like double-clicking to open the file. We need to install some functions to support the resolution of ASP applications, open: Control Panel - Programs - Programs and Functions - Turn Windows functions on or off, follow the diagram below, and select the corresponding ASP.
Set up IIS (turn on "Enable parent directory path", or you can use it: /path), do a good job of setting the relevant site, but it will prompt when running:
Citing [Microsoft][ODBC Microsoft Access Driver] disk or network errors. or (depending on how you connect to Access)
Reference Microsoft JET Database Engine Error '80004005'
Unspecified error
/inc/conn.asp，行 10
Solution
Add everyone's read and write permissions to the Temp directory under C:\Windows\ServiceProfiles\NetworkService\AppData\Local. Another visit is OK, so the problem is solved (everyone plus reading and writing is added by myself to save trouble, in fact, you can also add more "precise" points, see below for details)
Quote There is also a saying on the Internet to add an "Authenticated Users" user to the "System Disk:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp" directory, where the AppData directory is hidden, you can directly enter the path in the address bar when entering, or display the hidden file in the folder options
http://www.chinaz.com/Server/Web/061130X62008.html
IIS Status Codes: IIS detailed error codes and explanations
When a user attempts to access content on a server running Internet Information Services (IIS) over HTTP or File Transfer Protocol (FTP), IIS returns a numerical code that indicates the status of the request. This status code is recorded in the IIS logs and may also be displayed in a web browser or FTP client. Status codes can indicate whether a specific request was successful or not, and can also reveal the exact reason why the request failed.
Back to the top
More information
The location of the log file
By default, IIS places its log files in the %WINDIR\System32\Logfiles folder. Each World Wide Web (WWW) site and FTP site has a separate directory under that directory. By default, log files are created in these directories every day and named by date (for example, exYYMMDD.log).
HTTP
1xx - Informational tips
These status codes indicate temporary responses. The client should be prepared to receive one or more 1xx responses before receiving a regular response. 100 - Continue.
? 101 - Switch protocols.
2xx - Success
These status codes indicate that the server has successfully accepted the client request. 200 - OK. The client request was successful.
? 201 - Created.
? 202 - Accepted.
? 203 - Non-authoritative information.
? 204 - No content.
? 205 - Reset contents.
? 206 - Partial content.
3xx - Redirect
The client browser must take more action to fulfill the request. For example, the browser may have to request a different page on the server, or repeat the request through a proxy server. 302 - The object has been moved.
? 304 - Unmodified.
? 307 - Temporary redirect.
4xx - Client error
An error occurred and there seems to be a problem with the client. For example, the client requests a page that does not exist, and the client does not provide valid authentication information. 400 - Wrong request.
? 401 - Access denied. IIS defines a number of different 401 errors that indicate more specific reasons for the error. These specific error codes are displayed in the browser, but not in the IIS logs:? 401.1 - Login failed.
? 401.2 - Server configuration causes login to fail.
? 401.3 - Not authorized due to resource constraints by ACLs.
? 401.4 - Filter authorization failed.
? 401.5 - ISAPI/CGI application authorization failed.
? 401.7 – Access is denied by URL authorization policy on the web server. This error code is specific to IIS 6.0.
? 403 - Disabled Access: IIS defines a number of different 403 errors that indicate a more specific cause of the error: ? 403.1 - Executive Access Prohibited.
? 403.2 - Read Access Prohibited.
? 403.3 - Write access is prohibited.
? 403.4 - Requires SSL.
? 403.5 - Requires SSL 128.
? 403.6 - IP address rejected.
? 403.7 - Client certificate required.
? 403.8 - Site access denied.
? 403.9 - Too many users.
? 403.10 - Invalid configuration.
? 403.11 - Password Change.
? 403.12 - Denial of access to the mapping table.
? 403.13 - Client certificate revoked.
? 403.14 - Deny directory list.
? 403.15 - Client access permission exceeded.
? 403.16 - Client certificate is not trusted or invalid.
? 403.17 - The client certificate has expired or is not yet valid.
? 403.18 - The requested URL cannot be executed in the current application pool. This error code is specific to IIS 6.0.
? 403.19 - CGI cannot be performed for clients in this application pool. This error code is specific to IIS 6.0.
? 403.20 - Passport login failed. This error code is specific to IIS 6.0.
? 404 - Not found. 404.0 - (None) – No file or directory found.
? 404.1 - Website cannot be accessed on the requested port.
? 404.2 - Web Services Extension Lockout Policy Blocks This Request.
? 404.3 - MIME mapping policy blocks this request.
? 405 - HTTP predicates used to access this page are not allowed (methods are not allowed)
? 406 - The client browser does not accept the MIME type of the requested page.
? 407 - Proxy authentication required.
? 412 - Prerequisite failed.
? 413 – The request entity is too large.
? 414 - The request URI is too long.
? 415 – Unsupported media types.
? 416 – The requested scope cannot be met.
? 417 – Execution failed.
? 423 – Locked error.
5xx - Server error
The server is unable to complete the request because it encountered an error. 500 - Internal server error.? 500.12 - The application is busy restarting on the web server.
? 500.13 - The web server is too busy.
? 500.15 - Direct requests to Global.asa are not allowed.
? 500.16 – Incorrect UNC authorization credentials. This error code is specific to IIS 6.0.
? 500.18 – URL authorization store cannot be opened. This error code is specific to IIS 6.0.
? 500.100 - Internal ASP error.
? 501 - The header value specifies the unimplemented configuration.
? 502 - Received an invalid response when the web server was used as a gateway or proxy server.? 502.1 - CGI application timeout.
? 502.2 - CGI application error. application.
? 503 - Service unavailable. This error code is specific to IIS 6.0.
? 504 - Gateway timeout.
? 505 - HTTP version is not supported.
Common HTTP status codes and their causes
? 200 - Success. This status code indicates that IIS has successfully processed the request.
? 304 - Unmodified. The document requested by the client is already in its cache, and the document has not been modified since the cache. The client uses a cached copy of the document and does not download the document from the server.
? 401.1 - Login failed. The login attempt is unsuccessful, possibly because the username or password is invalid.
? 401.3 - Not authorized due to resource constraints by ACLs. This indicates an NTFS permissions issue. This error can occur even if you have the appropriate permissions for the file you are trying to access. For example, you will see this error if the IUSR account does not have access to the C:\Winnt\System32\Inetsrv directory. For additional information on how to resolve this issue, click the article number below to view the appropriate article in the Microsoft Knowledge Base:
187506 (http://support.microsoft.com/kb/187506/) INFO: Basic NTFS permissions for IIS 4.0
? 403.1 - Executive Access Prohibited. Here are two common causes of this error message: ? You don't have enough permission to execute. For example, this error message occurs if the directory permission on the ASP page you are trying to access is set to None, or if the directory permission on which the CGI script you are trying to execute is Allow scripts only. To modify the execution permissions, right-click the directory in the Microsoft Management Console (MMC), and then click the Properties and then the Catalog tab, making sure that the appropriate execution permissions are set for the content you are trying to access.
? You don't have a script mapping set to recognize the predicate used (for example, GET or POST) for the file type you're trying to execute. To verify this, right-click the directory in MMC, click Properties, click the Catalog tab, click Configuration, and then verify that the script mapping for the appropriate file type is set to allow the predicates used.
? 403.2 - Read Access Prohibited. Verify that IIS is set to allow read access to the directory. Also, if you are using a default file, verify that it exists. For additional information on how to resolve this issue, click the article number below to view the appropriate article in the Microsoft Knowledge Base:
247677 (http://support.microsoft.com/kb/247677/) Error message: 403.2 Forbidden: Read Access Forbidden
? 403.3 - Write access is prohibited. Verify that IIS and NTFS permissions are set to grant write access to the directory. For additional information on how to resolve this issue, click the article number below to view the appropriate article in the Microsoft Knowledge Base:
248072 (http://support.microsoft.com/kb/248072/) Error message: 403.3 Forbidden: Write Access Forbidden
? 403.4 - Requires SSL. Disable the Require secure channel option, or use HTTPS instead of HTTP to access the page. If you receive this error from a website that does not have a certificate installed, click the article number below to view the appropriate article in the Microsoft Knowledge Base:
224389 (http://support.microsoft.com/kb/224389/) Error message: HTTP error 403, 403.4, 403.5 Access prohibited: SSL required
? 403.5 - Requires SSL 128. Disable the option to require 128-bit encryption, or use a browser that supports 128-bit encryption to view the page. If you receive this error from a website that does not have a certificate installed, click the article number below to view the appropriate article in the Microsoft Knowledge Base:
224389 (http://support.microsoft.com/kb/224389/) Error message: HTTP error 403, 403.4, 403.5 Access prohibited: SSL required
? 403.6 - IP address rejected. You have configured your server to deny access to your current IP address. For additional information on how to resolve this issue, click the article number below to view the appropriate article in the Microsoft Knowledge Base:
248043 (http://support.microsoft.com/kb/248043/) Error message: 403.6 - Forbidden: IP Address Rejected
? 403.7 - Client certificate required. You have configured your server to require client authentication certificates, but you have not installed a valid client certificate. For additional information, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
190004 (http://support.microsoft.com/kb/190004/) Error 403.7 or "Connection to Server Could Not Be Established"
186812 (http://support.microsoft.com/kb/186812/) PRB: Error message: 403.7 Forbidden: Client Certificate Required
? 403.8 - Site access denied. You've set domain restrictions for the domain you use to access your server. For additional information on how to resolve this issue, click the article number below to view the appropriate article in the Microsoft Knowledge Base:
248032 (http://support.microsoft.com/kb/248032/) Error message: Forbidden: Site Access Denied 403.8
? 403.9 - Too many users. The number of users connecting to that server exceeds the connection limit you set. For additional information on how to change this limit, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
248074 (http://support.microsoft.com/kb/248074/) Error message: Access Forbidden: Too Many Users Are Connected 403.9
Note: Microsoft Windows 2000 Professional and Microsoft Windows XP Professional automatically set a limit of up to 10 connections on IIS. You cannot change this limit.
? 403.12 - Denial of access to the mapping table. The page you want to visit asks for a client certificate, but the user ID mapped to your client certificate has been denied access to the file. For additional information, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
248075 (http://support.microsoft.com/kb/248075/) Error message: HTTP 403.12 - Access Forbidden: Mapper Denied Access
? 404 - Not found. This error occurs because the file you are trying to access has been removed or deleted. This error also occurs if you try to access a file with a limited extension after installing the URLScan tool. In this case, the log file entry of the request will appear as "Rejected by URLScan".
? 500 - Internal server error. A lot of server-side errors can cause this error message. The Event Viewer log contains more detailed error reasons. In addition, you can disable friendly HTTP error messages to receive detailed error descriptions. For additional information on how to disable friendly HTTP error messages, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
294807 (http://support.microsoft.com/kb/294807/) How to disable Internet Explorer 5's "Show Friendly HTTP Error Messages" feature on the server side
? 500.12 - The application is restarting. This means that you are trying to load the ASP page during the IIS restart of the application. This information disappears when the page is refreshed. If this message reappears after refreshing the page, it may be that your antivirus software is scanning the Global.asa file. For additional information, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
248013 (http://support.microsoft.com/kb/248013/) Error Message: HTTP Error 500-12 Application Restarting
? 500-100.ASP - ASP error. This error message appears if the ASP page you are trying to load contains an error code. To get more precise error messages, disable friendly HTTP error messages. By default, this error message is only enabled on the default website. For additional information on how to see this error message on a non-default Web site, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
261200 (http://support.microsoft.com/kb/261200/) shows an HTTP 500 error message instead of an ASP error message for 500-100.asp
? 502 - Gateway error. This error message occurs if the CGI script that is trying to run does not return a valid HTTP header set.
FTP
1xx - Initial response in the affirmative
These status codes indicate that an operation has started successfully, but the client expects another answer before proceeding with a new command. 110 Restart the mark response.
? 120 service is ready and starts in nnn minutes.
? 125 The data connection is open and the transfer is starting.
? 150 The file is in good condition and ready to open the data connection.
2xx - Affirmative completion response
An operation has been successfully completed. The client can execute the new command. 200 command OK.
? 202 Commands not executed, too many commands on the site.
? 211 system status, or system help reply.
? 212 Directory status.
? 213 File Status.
? 214 Help Messages.
? 215 NAME system type, where NAME is the official system name listed in the Assigned Numbers document.
? 220 The service is ready to perform requests from new users.
? 221 Service Shutdown Control Connection. If appropriate, log out.
? 225 Data connection open, no transmission in progress.
? 226 Close the data connection. The requested file operation was successful (for example, transferring a file or abandoning a file).
? 227 Enter passive mode (H1, H2, H3, H4, P1, P2).
? 230 Users are logged in, proceed.
? 250 The requested file operation is correct and complete.
? 257 "PATHNAME" has been created.
3xx - Affirmative intermediate response
The command succeeded, but the server needed more information from the client to finish processing the request. 331 Correct username and password required.
? 332 Account login required.
? 350 Requested file operations are awaiting further information.
4xx - Complete response for transient negation
The command was unsuccessful, but the error was temporary. If the client retries the command, it may be executed successfully. 421 Service is unavailable and the control connection is being closed. If the service determines that it must be shut down, this response is sent to any command.
? 425 Unable to open data connection.
? 426 Connection closed; transfer aborted.
? 450 The requested file operation was not executed. The file is not available (for example, the file is busy).
? 451 Request Operation Terminated: A local error is being processed.
? 452 Requested action not executed. Insufficient system storage.
5xx - Permanent negative completion response
The command was unsuccessful and the error was permanent. If the client retries the command, the same error will occur again. 500 syntax errors and commands not recognized. This can include errors such as the command line being too long.
? 501 There is a syntax error in the parameter.
? 502 Orders not executed.
? 503 Wrong command sequence.
? 504 The command for this parameter is not executed.
? 530 Not logged in.
? 532 Account required to store files.
? 550 The requested action was not executed. The file is not available (e.g., file not found, no access).
? 551 Abnormal termination of the requested operation: Unknown page type.
? 552 Requested file operation terminates abnormally: Storage allocation exceeded (for current directory or dataset).
? 553 The requested action was not executed. File names that are not allowed.
Common FTP status codes and their causes
? 150 - FTP uses two ports: 21 for sending commands and 20 for sending data. Status code 150 indicates that the server is ready to open a new connection on port 20 to send some data.
? 226 - Command to open a data connection on port 20 to perform an action, such as transferring a file. The operation completes successfully and the data connection is closed.
? 230 - This status code is displayed when the client sends the correct password. It indicates that the user has successfully logged in.
? 331 - The status code is displayed after the client sends the username. The status code will be displayed regardless of whether the username provided is a valid account in the system.
? 426 - The command opens the data connection to perform an action, but the action has been canceled and the data connection is closed.
? 530 - This status code indicates that the user is unable to log in because the username and password combination is invalid. If you sign in with a user account, you may have typed the wrong username or password, or you may choose to allow anonymous access only. If you log in with an anonymous account, the configuration of IIS may deny anonymous access.
? 550 - The command is not executed because the specified file is not available. For example, the file you want to GET doesn't exist, or trying to PUT the file into a directory that you don't have write access to. |
Posted on 2/3/2015 4:06:17 PM
|
|
|
