Status Codes 5.0 and 6.0 of Microsoft Internet Information Server (IIS)

HTTP

1xx-Information prompt

These status codes indicate temporary responses. Before receiving a regular response, the client should be prepared to receive one or more 1xx responses.

• 100-continue.
• 101-switch protocol.

2XX-success

This type of Status Code indicates that the server successfully accepts client requests.

• 200-OK. The client request is successful.
• 201-created.
• 202-accepted.
• 203-non-authoritative information.
• 204-NO content.
• 205-Reset content.
• 206-part of content.
• 207-Multi-status (webDAV ).

3xx-redirection

The client browser must perform more operations to implement the request. For example, the browser may have to request different pages on the server or repeat the request through the proxy server.

• 301-permanently moved
• 302-the object has been moved.
• 304-not modified.
• 307-temporary redirection.

4xx-client Error

The client seems to be faulty when an error occurs. For example, the client does not provide valid authentication information for a page that does not exist in a request.

• 400-Incorrect request.
• 401-Access denied. IIS defines several different 401 errors to indicate more specific error causes. These specific error codes are displayed in the browser but not in the IIS log:
  • 401.1-Logon Failed.
  • 401.2-login failed due to server configuration.
  • 401.3-the ACL is not authorized due to resource restrictions.
  • 401.4-filter authorization failed.
  • 401.5-An error occurred while authorizing the ISAPI/cgi application.
  • 401.7-access is denied by the URL Authentication Policy on the Web server. This error code is dedicated to IIS 6.0.
• 403-Access prohibited: IIS defines several different 403 errors to indicate more specific error causes:
  • 403.1-the execution access is forbidden.
  • 403.2-Read access is forbidden.
  • 403.3-write access is forbidden.
  • 403.4-require SSL.
  • 403.5-require SSL 128.
  • 403.6-the IP address is rejected.
  • 403.7-client certificate required.
  • 403.8-site access is denied.
  • 403.9-too many users.
  • 403.10-the configuration is invalid.
  • 403.11-change the password.
  • 403.12-access to the ing table is denied.
  • 403.13-the client certificate is revoked.
  • 403.14-reject the directory list.
  • 403.15-the access permission of the client is exceeded.
  • 403.16-the client certificate is untrusted or invalid.
  • 403.17-the client certificate has expired or has not yet taken effect.
  • 403.18-the requested URL cannot be executed in the current application pool. This error code is dedicated to IIS 6.0.
  • 403.19-CGI cannot be executed for clients in this application pool. This error code is dedicated to IIS 6.0.
  • 403.20-logon to passport failed. This error code is dedicated to IIS 6.0.
• 404-not found.
  • 404.0-(none)-No file or directory found.
  • 404.1-the website cannot be accessed through the requested port.
  • 404.2-the Web service extended locking policy blocks this request.
  • 404.3-the mime ing 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 is required.
• 412-precondition failed.
• 413-The Request Entity is too large.
• 414-the request URI is too long.
• 415-unsupported media type.
• 416-unable to meet the request range.
• 417-execution failed.
• 423-locking error.

5xx-Server Error

The server cannot complete the request because of 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 Request to global. ASA is not allowed.
  • The 500.16-unc authorization credential is incorrect. This error code is dedicated to IIS 6.0.
  • 500.18-unable to open the URL Authorization repository. This error code is dedicated to IIS 6.0.
  • 500.19-the data in this file is incorrectly configured in the metabase.
  • 500.100-Internal ASP error.
• 501-the header value specifies the unimplemented configuration.
• 502-the Web server received an invalid response when used as a gateway or proxy server.
  • 502.1-CGI application timeout.
  • 502.2-CGI application error.
• 503-the service is unavailable. This error code is dedicated to IIS 6.0.
• 504-gateway timeout.
• 505-the HTTP version is not supported.

Iis http status code and Its Causes

• 200-successful.This status code indicates that IIS has successfully processed the request.
• 206-part of content.This indicates that a part of the file has been downloaded. You can resume corrupted downloads or split the downloads into multiple concurrent streams.
• 207-Multi-status (webDAV ).There should be an XML message before this message, which may contain several separate response codes, depending on how many subrequests are sent.
• 301-permanently moved.This request and all subsequent requests should be forwarded to the specified Uri.
• 302-found.For form-based authentication, this message usually indicates that the object has been moved ". The requested resources temporarily reside in different Uris. As redirection may change sometimes, the client should continue to use request-URI for future requests. This response can be cached only when it is indicated in the cache-control or Expires header field.
• 304-not modified.The document requested by the client is already in its cache and has not been modified since the cache. The client uses cached copies of documents instead of downloading documents from the server.
• 401.1 and 401.2-Logon Failed.The logon attempt failed because the user name or password is invalid or the system configuration is incorrect. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 907273 (http://support.microsoft.com/kb/907273/) troubleshooting HTTP 401 errors in IIS
• 401.3-the ACL is not authorized due to resource restrictions.This indicates that NTFS permission issues exist. This error may occur even if you have the relevant permissions on the file you are trying to access. For example, if the IUSR account does not have access to the C: \ winnt \ system32 \ inetsrv directory, you will see this error. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 271071 (http://support.microsoft.com/kb/271071/) how to set the required NTFs and user permissions for IIS 5.0 web servers
  812614 (http://support.microsoft.com/kb/812614/) default permissions and user permissions for IIS 6.0
• 403-Access prohibited:If the website does not set the default document and is not set to allow directory browsing, the 403 status code is received. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 320051 (http://support.microsoft.com/kb/320051/) how to configure the default document in Internet Information Services
• 403.1-the execution access is forbidden.The following are two common causes of this error message:
  • You do not have sufficient execution permits. For example, if the directory permission of the ASP page to be accessed is set to "NONE", or the directory permission of the CGI script to be executed is "only allow scripts ", the error message is displayed. To modify the execution permission, right-click the directory on the Microsoft Management Console (MMC) and click Properties"And "directory"Tab, make sure that the appropriate execution permissions are set for the content to be accessed.
  • You have not set the script ing of the file type you are trying to execute to identify the predicates used (for example, get or post ). To verify this, right-click the directory in the Microsoft console and choose Properties", "Directory"Tab and "configuration"Verify whether the script ing of the corresponding file type is set to allow the predicates used.
• 403.2-Read access is forbidden.Verify that IIS has been set to allow read access to the directory. In addition, if you are using a default file, verify that the file exists. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 247677 (http://support.microsoft.com/kb/247677/) error message: 403.2 forbidden: Read Access forbidden (403.2 forbidden access: Read Access forbidden)
• 403.3-write access is forbidden.Verify that the IIS and NTFS permissions are set to grant write access to the directory. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 248072 (http://support.microsoft.com/kb/248072/) error message: 403.3 forbidden: Write Access forbidden (403.3 forbidden access: forbidden write access)
• 403.4-require SSL.DisableSecure channel requiredOr use HTTPS instead of HTTP to access the page. If this error occurs on a website that does not have a certificate installed, click the following article number to view the article in the Microsoft Knowledge Base: 224389 (http://support.microsoft.com/kb/224389/) error message in Internet Information Server 4.0: "HTTP Error 403,403.4, 403.5 forbidden: SSL required" (HTTP Error 403, 403.4, 403.5 disabled: SSL required)
• 403.5-require SSL 128.DisableRequires 128-bit encryptionOr use a browser that supports 128-bit encryption to view the page.
• 403.6-the IP address is rejected.You have configured the server to deny access to your current IP address. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 248043 (http://support.microsoft.com/kb/248043/) error message: 403.6-Forbidden: IP address rejected (403.6-unavailable: IP address denied)
• 403.7-client certificate required.You have configured the server to require a certificate for client authentication, but you have not installed a valid client certificate. 186812 (http://support.microsoft.com/kb/186812/) PRB: error message: 403.7 forbidden: client certificate required (403.7 forbidden access: client certificate required)
• 403.8-site access is denied.You have set domain name restrictions for the domain used to access the server. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 248032 (http://support.microsoft.com/kb/248032/) error message: forbidden: site access denied 403.8 (forbidden access: site access denied 403.8)
• 403.9-too many users.The number of users connected to the server exceeds the connection limit you set. For more information about how to change this restriction, click the following article number to view the article in the Microsoft Knowledge Base: 248074 (http://support.microsoft.com/kb/248074/) error message: Access forbidden: too connected users are connected 403.9 (Access forbidden: too many connected users 403.9)

  Note:: Microsoft Windows 2000 Professional and Windows XP Professional automatically set a maximum of 10 connections on IIS. You cannot change this restriction.

• 403.12-access to the ing table is denied.The page you want to access requires a client certificate. However, the user ID mapped to the client certificate has denied access to the file. For other information, click the following article number to view the article in the Microsoft Knowledge Base: 248075 (http://support.microsoft.com/kb/248075/) error: HTTP 403.12-Access forbidden: mapper denied access (HTTP 403.12-forbidden access: er 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 attempt to access a file with a limited extension after installing the URLScan tool. If you have installed uriscan, you will see "rejected by URLScan" in the w3svc log file ". In this case, "rejected by URLScan" appears in the log file of the request. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 248033 (http://support.microsoft.com/kb/248033/) common cause of the "HTTP 404-file not found" (HTTP 404-file not found) Error returned by the IIS server
  • 404.1-the website cannot be accessed through the requested port.This error message indicates that the IP address of the website to be accessed does not accept requests from the port used by this request. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    248034 (http://support.microsoft.com/kb/248034/) Iis error: 404.1 web site not found (404.1 website not found)
  • 404.2-The lock policy blocks this request.In IIS 6.0, this indicates that the request has been blocked in the Web Service Extension list. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 328419 (http://support.microsoft.com/kb/328419/) how to add and delete Web Service Extension files in IIS 6.0
    328505 (http://support.microsoft.com/kb/328505/) How to list web service extensions and extensions in IIS 6.0
    328360 (http://support.microsoft.com/kb/328360/) How to enable and disable ISAPI extensions and CGI applications in IIS 6.0
  • 404.3-the mime ing policy blocks this request.This problem occurs if:
    1. Handler ing for the requested file extension is not configured.
    2. No MIME type is configured for the website or application.
• 405-the method is not allowed.This error occurs when the client sends an HTTP request to the server running IIS that contains an HTTP verb that the server cannot recognize. To solve this problem, make sure that the client request uses an HTTP verb compatible with the http rfc. For more information about http rfc, see the "Reference" section.
• 500-internal server error.Many server errors may cause this error message. The Event Viewer log contains more detailed error causes. In addition, you can disable friendly HTTP Error messages to receive detailed error descriptions. For more information about how to display friendly HTTP Error messages, click the following article number to view the article in the Microsoft Knowledge Base: 294807 (http://support.microsoft.com/kb/294807/) How to: Disable Internet Explorer 5 'show friendly HTTP Error message' feature on the server side
• 500.12-the application is restarting.This indicates that you attempt to load ASP pages When IIS restarts the application. After the page is refreshed, the message disappears. If the message appears again after the page is refreshed, it may be that the anti-virus software is scanning the global. Asa file. For other information, click the following article number to view the article in the Microsoft Knowledge Base: 248013 (http://support.microsoft.com/kb/248013/) error message: HTTP Error 500-12 Application restarting (HTTP Error 500-12 Application restarting)
• 500-100.asp-Asp error.If the ASP page to be loaded contains the error code, this error message is displayed. To get a more accurate error message, disable the friendly HTTP error message. By default, this error message is only enabled on the default website. For more information about how to view this error message on a non-default website, click the following article number to view the article in the Microsoft Knowledge Base: 261200 (http://support.microsoft.com/kb/261200/) displays HTTP 500 error messages without ASP error messages of 500-100.asp
• 502-Gateway error.If the CGI script you are trying to run does not return a valid HTTP header set, this error message is displayed. To solve this problem, you must debug the CGI application to determine why it passes invalid HTTP information to IIS.
• 503-the service is unavailable.Starting from IIS 6, the kernel mode HTTP. sys component generates the HTTP 503 status. For more information about how to determine and exclude HTTP 503 errors, click the following article number to view the article in the Microsoft Knowledge Base: 820729 (http://support.microsoft.com/kb/820729/) error logging in HTTP API
• 500.19.If the XML metabase contains invalid configuration information in the content type you are trying to access, you will receive this error. To solve this problem, delete or correct the invalid configuration. This problem usually indicates a problem in the scriptmap metadatabase key.

FTP

1xx-Affirmative preliminary reply

These status codes indicate that an operation has started successfully, but the client wants to receive another response before continuing to operate the new command.

• 110 restart mark the reply.
• 120 the service is ready.NnnMinutes later.
• 125 the data connection is enabled and transmission is starting.
• 150 the file is in normal state and you are ready to open the data connection.

2XX-a positive response

An operation has been completed successfully. The client can execute new commands.

• 200 command OK.
• 202 if no command is executed, there are too many commands on the site.
• 211 system status or system help reply.
• 212 directory status.
• 213 File status.
• 214 help message.
• 215 name system type, where name is the formal system name listed in the assigned numbers document.
• 220 the service is ready to execute new user requests.
• 221 close the control connection. If appropriate, log out.
• 225 the data connection is opened and there is no transmission in progress.
• 226 close the data connection. The requested file operation has been successful (for example, transferring a file or dropping a file ).
• 227 enter the passive mode (H1, H2, H3, H4, P1, P2 ).
• 230 The user has logged on and continues.
• 250 the requested file operation is correct and has been completed.
• 257 "pathname" has been created ".

3xx-Affirmative intermediate reply

The command is successful, but the server needs more information from the client to process the request.

• 331 the user name is correct and the password is required.
• 332 You need to log on to the account.
• 350 the requested file operation is waiting for further information.

4xx-completion of transient Negation

The command fails, but the error is temporary. If the client retries the command, it may be executed successfully.

• 421 the service is unavailable and the control connection is being closed. If the Service determines that it must be disabled, this response will be sent to any command.
• 425 data connection cannot be enabled.
• 426 Connection closed; Transfer aborted.
• 450 file operations not requested. The file is unavailable (for example, the file is busy ).
• 451 request operation exception termination: processing local error.
• 452 the requested operation is not performed. Insufficient system storage space.

5xx-permanent completion reply

The command fails. The error is permanent. If the client retries the command, the same error will occur again.

• 500 syntax error. The command cannot be identified. This may include errors such as too long command lines.
• 501 syntax error in the parameter.
• 502 the command is not executed.
• 503 error command sequence.
• 504 the command for this parameter is not executed.
• 530 not logged on.
• 532 accounts are required to store files.
• 550 the requested operation is not performed. File is unavailable (for example, the file is not found and no access permission is available ).
• 551 exceptional request termination: Unknown page type.
• 552 the requested file operation ended abnormally: exceeds Storage Allocation (for the current directory or dataset ).
• 553 the requested operation is not performed. The file name is not allowed.

Common FTP status code and Its Causes

• 150-FTP uses two ports: 21 for sending commands and 20 for sending data. Status Code 150 indicates that the server is preparing to open a new connection on Port 20 and send some data.
• 226-Open a data connection on Port 20 to perform operations, such as transferring files. This operation is successfully completed and the data connection is closed.
• 230-The status code is displayed after the client sends the correct password. It indicates that the user has successfully logged on.
• 331-The status code is displayed after the client sends the user name. This status code is displayed no matter whether the user name is a valid account in the system.
• 426-The command opens the data connection to execute the operation, but the operation has been canceled and the data connection has been closed.
• 530-The Status Code indicates that the user cannot log on because the combination of the user name and password is invalid. If you log on with a user account, you may enter the wrong user name or password, or you may choose to allow anonymous access only. If you log on with an anonymous account, the IIS configuration may reject anonymous access.
• 550-The command is not executed because the specified file is unavailable. For example, the file to get does not exist, or you try to put the file to a directory without the write permission.

Turn: http://www.netcet.cn/content.aspx? Id = 514106911922