IIS Status Code

IIS returns a numeric code that represents the state of the request when a user attempts to access content on a server that is running Internet information Services (IIS) through HTTP or File Transfer Protocol (FTP). 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%windir\system32\logfiles 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). 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. 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. 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. 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. 403.6-ip The 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. 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. 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. An invalid response was received when the 502-web server was used as a gateway or proxy server. The 502.1-cgi application timed out. Error 502.2-cgi application. application.503-Service is not available. This error code is private to IIS 6.0. 504-Gateway Timeout. 505-http version is not supported. 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:\Winnt\System32\Inetsrv directory, you will see this error. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base: 403.1-execution access is prohibited. 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 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, 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 resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base: 403.3-Write access is prohibited. Verify that the IIS permissions and NTFS permissions are set to grant write access to the directory. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base: 403.4-require SSL. option, or use HTTPS instead of HTTP to access the page. If this error occurs on a Web site that does not have a certificate installed, click the article number below to view the article in the Microsoft Knowledge Base: 403.5-Requires SSL 128. option, or use a browser that supports 128-bit encryption to view the page. If this error occurs on a Web site that does not have a certificate installed, click the article number below to view the article in the Microsoft Knowledge Base: The 403.6-IP address was rejected. You have configured your server to deny access to your current IP address. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base: 403.7-Requires a client certificate. You have configured your server to require a client authentication certificate, but you do not have a valid client certificate installed. For additional information, click the article number below to view the article in the Microsoft Knowledge Base: 403.8-site access denied. You have set a domain name limit for the domain that you use to access the server. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base: 403.9-Too many users. The number of users connected to this server exceeds the connection limit you have set. For additional information about how to change this limit, click the following article number to view the article in the Microsoft Knowledge Base:: Microsoft Windows Professional and Microsoft Windows XP Professional automatically sets the limit of up to 10 connections on IIS. You cannot change this limit. 403.12-access to the mapping table is denied. The page you are trying to access requires a client certificate, but the user ID that is mapped to your client certificate has been denied access to the file. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 404-not found. This error occurs because the file you are trying to access has been moved or deleted. This error can also occur if you attempt to access a file with a limited extension after you install the URLScan tool. In this case, the word "Rejected by URLScan" appears in the log file entry for the request. 500-Internal server error. Many server-side errors can cause this error message. The Event Viewer log contains more detailed reason for the error. In addition, you can disable friendly HTTP error messages to receive detailed error descriptions. For additional information about how to disable friendly HTTP error messages, click the following article number to view the article in the Microsoft Knowledge Base: 500.12-The application is rebooting. This means that you are attempting to load an ASP page while IIS restarts the application. This information disappears when the page is refreshed. If the page is refreshed, this information appears again, possibly because antivirus software is scanning the Global.asa file. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 500-100. Asp-asp error. If an ASP page that you are trying to load contains an error code, you will receiveThis error message. To get a more accurate error message, disable the friendly HTTP error message. By default, this error message is enabled only on the default Web site. For additional information about how to see this error message on a Non-default Web site, click the following article number to view the article in the Microsoft Knowledge Base: Displays an HTTP 500 error message without displaying the 500-100.asp ASP error message 502-Gateway error. This error message appears if the CGI script you are trying to run does not return a valid set of HTTP headers. These status codes indicate that an operation has started successfully, but the client expects another reply before continuing with the new command. 110 reboot the tag reply. 120 The service is ready and starts after nnn minutes. 125 The data connection is turned on and the transfer is starting. 150 file status is normal, ready to open data connection. An operation has completed successfully. The client can execute the new command. 200 the command determines. 202 command is not executed, too many commands on the site. 211 System State, 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 execute the new user's request. 221 The service closes the control connection. If appropriate, please log off. 225 The data connection is open and no transmission is in progress. 226 Close the data connection. The requested file operation was successful (for example, transferring a file or discarding a file). 227 into the passive mode (H1,H2,H3,H4,P1,P2). 230 The user is logged in and continues. 250 The requested file operation is correct and completed. 257 has created "PATHNAME". The command was successful, but the server needed more information from the client to complete processing of the request. 331 username is correct and requires a password. 332 login account required. 350 The requested file operation is waiting for further information. The command did not succeed, but the error is temporary. If the client retries the command, it may execute successfully. The 421 service is not available and is shutting down the control connection. If the service determines that it must be closed, this response is sent to any command. 425 The data connection could not be opened. 450 The requested file operation was not executed. File is not available (for example, the file is busy). 451 the requested operation terminated abnormally: A local error is being processed. 452 the requested operation was not performed. The system does not have enough storage space. The command is not successful and the error is permanent. If the client retries the command, the same error occurs again. 500 syntax error, command not recognized. This may include errors such as the command line being too long. 501 There is a syntax error in the parameter. 502 Not implementedCommand. 503 wrong sequence of commands. 504 The command that did not execute the parameter. 530 not logged in. 532 requires an account for storing files. 550 the requested operation was not performed. File is not available (for example, file not found, no access rights). 551 The requested operation terminated abnormally: Unknown page type. 552 requested file operation terminated abnormally: Excess storage allocation (for current directory or dataset). 553 The requested operation was not performed. The file name that is not allowed. -FTP uses two ports: 21 for sending commands, 20 for sending data. Status code 150 indicates that the server is ready to open a new connection on port 20 and send some data. -The command opens a data connection on port 20 to perform operations, such as transferring files. The operation completed successfully and the data connection was closed. -The status code is displayed after the client sends the correct password. It indicates that the user has successfully logged in. -The status code is displayed after the client sends the user name. The status code is displayed regardless of whether the user name provided is a valid account on the system. -The command opens a data connection to perform the operation, but the operation has been canceled and the data connection has been closed. -The status code indicates that the user cannot log on because the user name and password combination are invalid. If you are logged on with a user account, you may type an incorrect user name or password, or you may choose to allow only anonymous access. If you log on with an anonymous account, the configuration of IIS may deny anonymous access. -the command was not executed because the specified file is not available. For example, the file you want to get does not exist, or you are trying to put the file to a directory where you do not have write permission.