IIS verbose error codes and explanations

When a user attempts to access content on a server that is running Internet information Services (IIS) through HTTP or File Transfer Protocol (FTP), IIS returns a numeric code that represents the state of the request. The status code is recorded in the IIS log and may also be displayed in a Web browser or FTP client. The status code can indicate whether a specific request has been successful, and can also reveal the exact cause of the request failure.

In the default state, IIS places its log files in the%windirsystem32logfiles folder. Each World Wide Web (WWW) site and FTP site have a separate directory under that directory. By default, log files are created in these directories on a daily basis, and the log files are named with dates (for example, ExYYMMDD.log).

HTTP

1XX-Information Tips

These status codes represent a temporary response. The client should be prepared to receive one or more 1xx responses before receiving a regular response. · 100-Continue.

· 101-Switch protocol.

2XX-Success

This type of status code indicates that the server 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 the content.

· 206-part content.

3xx-redirect

The client browser must take more action to implement the request. For example, a browser might have to request a different page on the server, or repeat the request through a proxy server. · 302-Object has been moved.

· 304-not modified.

· 307-Temporary redirection.

4xx-Client Error

An error occurred and the client appears to have a problem. For example, a client requests a page that does not exist, and the client does not provide valid authentication information. · 400-the wrong request.

· 401-access is denied. IIS defines a number of different 401 errors that indicate a more specific cause of the error. These specific error codes are displayed in the browser but are not displayed in the IIS log: · 401.1-Login failed.

· 401.2-The server configuration caused the login to fail.

· 401.3-Authorization is not granted due to ACL restrictions on resources.

· 401.4-Filter Authorization failed.

· 401.5-ISAPI/CGI application authorization failed.

· 401.7– access is denied by the URL authorization policy on the WEB server. This error code is private to IIS 6.0.

· 403-Prohibit access: IIS defines a number of different 403 errors that indicate a more specific cause of the error: · 403.1-execution access is prohibited.

· 403.2-Read access is forbidden.

· 403.3-Write access is forbidden.

· 403.4-Require SSL.

· 403.5-Requires SSL 128.

· The 403.6-IP address was rejected.

· 403.7-Client certificate required.

· 403.8-site access is denied.

· 403.9-Excessive number of users.

· 403.10-Configuration is not valid.

· 403.11-Password change.

· 403.12-access to the mapping table is denied.

· 403.13-The client certificate was 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 has not yet taken effect.

· 403.18-The requested URL cannot be executed in the current application pool. This error code is private to IIS 6.0.

· 403.19-CGI cannot be performed for clients in this application pool. This error code is private to IIS 6.0.

· 403.20-passport Login failed. This error code is private to IIS 6.0.

· 404-not Found. · 404.0-(None) – No files or directories found.

· 404.1-The Web site cannot be accessed on the requested port.

· The 404.2-web service extension lockout policy blocks this request.

· The 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 is required.

· 412-Prerequisite failed.

· The 413– request entity is too large.

· 414-The request URI is too long.

· 415– media type that is not supported.

· 416– the requested range is not satisfied.

· 417– execution failed.

· 423– the locked error.

5XX-Server Error

The server was unable to complete the request due to an error encountered. · 500-Internal server error. · 500.12-The application is busy restarting on the WEB server.

· The 500.13-web server is too busy.

· 500.15-Direct Request Global.asa is not allowed.

· The 500.16–unc authorization credentials are incorrect. This error code is private to IIS 6.0.

· The 500.18–url authorization store cannot be opened. This error code is private to IIS 6.0.

· 500.100-Internal ASP error.

· 501-The header value specifies a configuration that is not implemented.

· The 502-web server received an invalid response when it was used as a gateway or proxy server. · The 502.1-cgi application timed out.

· Error 502.2-cgi application. Application.

· 503-The service is not available. This error code is private to IIS 6.0.

· 504-Gateway Timeout.

· 505-http version is not supported.

Common HTTP status Codes and why

· 200-success. This status code indicates that IIS has successfully processed the request.

· 304-not modified. The client-requested document is already in its cache and the document has not been modified since it was cached. The client uses a cached copy of the document, rather than downloading the document from the server.

· 401.1-Login failed. The logon attempt was unsuccessful, possibly because the user name or password is invalid.

· 401.3-Authorization is not granted due to ACL restrictions on resources. This indicates that there is an NTFS permission problem. This error can occur even if you have the appropriate permissions for the file you are trying to access. For example, if the IUSR account does not have access to the C:winntsystem32inetsrv directory, you will see this error. For additional information about how to troubleshoot this issue, click the article number below to view the article in the Microsoft Knowledge Base:

Base NTFS permissions for 187506 (HTTP://support.microsoft.com/kb/187506/) Info:iis 4.0

· 403.1-execution access is prohibited. The following are two common causes of this error message: · You do not have sufficient permission to execute. For example, this error message appears if the directory where the ASP page you are attempting to access is set to none, or if you are trying to execute a CGI script that has permission to allow script only. To modify execution permissions, right-click the directory in Microsoft Management Console (MMC), and then click the Properties and Directories tab to ensure that the appropriate execution permissions are set for the content you are trying to access.

· You did not set the script mapping of the file type you are trying to perform to identify the predicate you are using (for example, get or POST). To verify this, right-click the table of contents in MMC, click Properties, right-click the table of Contents tab, and configure, and then verify that the script mappings for the appropriate file type are set to allow the verbs that are used.

· 403.2-Read access is forbidden. Verify that IIS is set to allow read access to the directory. Also, if you are using the default file, verify that the file exists. For additional information about how to troubleshoot this issue, click the article number below 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 No access: Read access prohibited)

· 403.3-Write access is forbidden. Verify that the IIS permissions and NTFS permissions are set to grant write access to the directory. For additional information about how to troubleshoot this issue, click the article number below 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 No access: Write access prohibited)