IIS status code
Article ID: 318380 Last Update Date: June 25, 2004 Version: 6.2
The release number of this article has been CHS318380
This page
Summary More Information Reference
summary
When the user tries to access the content on the server running Internet Information Service (IIS) via HTTP or File Transfer Protocol (FTP), IIS returns a digital code indicating the state of the request. This status code is recorded in the IIS log, and it is also possible to display in a web browser or FTP client. Status code can indicate whether the specific request has been successful, and it can also reveal the exact cause of request failure.
More information
The location of the log file is in the default state, IIS places its log file in the% WINDIR / System32 / LogFiles folder. Each World Wide Web (WWW) site and FTP site have a separate directory in this directory. In the default, you will create a log file in these directory every day and name it to the log file (for example, exymmdd.log) with the date.
HTTP
1xx - Information Tips
These status code indicate a temporary response. The client should be prepared to receive one or more 1xx responses before receiving a regular response.
• 100 - Continue. • 101 - Switching protocol.
2xx - success
Such state code indicates that the server has successfully accepted the client request.
• 200 - OK. The client request has been successful. • 201 - has been created. • 202 - Accepted. • 203 - Non-authorified information. • 204 - No content. • 205 - Reset content. • 206 - Some content.
3xx - redirection
The client browser must take more operations to implement the request. For example, a browser may have to request a different page on the server or repeat the request via a proxy server.
• 302 - The object has been moved. • 304 - Unmodified. • 307 - Temporary redirection.
4xx - client error
An error occurs, the client seems to have problems. For example, the client requests a page that does not exist, and the client does not provide valid authentication information.
• 400 - Error request. • 401 - Access is rejected. IIS defines many different 401 errors, which indicate more specific error reasons. These specific error codes are displayed in the browser, but not in the IIS log:
• 401.1 - Login failed. • 401.2 - Server configuration causes login to fail. • 401.3 - Due to the restriction of ACLs, no authorization is obtained. • 401.4 - Filter authorization failed. • 401.5 - ISAPI / CGI application authorization failed. • 401.7 - Access is rejected by the URL authorization policy on the web server. This error code is dedicated to IIS 6.0. • 403 - Prohibition Access: IIS defines many different 403 errors, which indicate more specific error:
• 403.1 - Perform access is disabled. • 403.2 - Read Access is disabled. • 403.3 - Write access is disabled. • 403.4 - Require SSL. • 403.5 - Require SSL 128. • 403.6 - IP address is rejected. • 403.7 - Require client certificate. • 403.8 - Site Access is rejected. • 403.9 - too much user number. • 403.10 - Configuration is invalid. • 403.11 - Password changes. • 403.12 - Reject the access mapping table. • 403.13 - Client Certificate is revoked. • 403.14 - Reject the directory list. • 403.15 - Beyond the client access license. • 403.16 - The 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 performed in the current application pool. This error code is dedicated to IIS 6.0. • 403.19 - CGI cannot be performed for clients in this application pool. This error code is dedicated to IIS 6.0. • 403.20 - Passport login failed. This error code is dedicated to IIS 6.0. • 404 - Not found.
• 404.0 - (None) - No file or directory found. • 404.1 - Unable to access the Web site on the requested port. • 404.2 - Web Service Extension Lock Policy prevents this request. • 404.3 - MIME mapping policy prevents this request. • 405 - HTTP predicates used to access this page are not allowed (Method Not Allow) • 406 - The client browser does not accept the MIME type of the requested page. • 407 - Require proxy authentication. • 412 - Prerequisites fail. • 413 - The request entity is too large. • 414 - Request URI too long. • 415 - Media types that are not supported. • 416 - The range requested cannot be satisfied. • 417 - Execution failed. • 423 - Locked error. 5xx - server error
The server cannot complete the request due to an error.
• 500 - Internal server error.
• 500.12 - Application is busy restarting on a web server. • 500.13 - Web server is too busy. • 500.15 - Do not allow you to request Global.asa directly. • 500.16 - UNC authorization credentials are incorrect. This error code is dedicated to IIS 6.0. • 500.18 - URL authorization storage cannot be opened. This error code is dedicated to IIS 6.0. • 500.100 - Internal ASP error. • 501 - The page eyebrow value specifies the unrealized configuration. • 502 - Web server received an invalid response when used as a gateway or a proxy server.
• 502.1 - CGI application timeout. • 502.2 - CGI application error. Application. • 503 - Service is not available. This error code is dedicated to IIS 6.0. • 504 - Gateway timeout. • 505 - HTTP version is not supported.
Common HTTP status code and reason
• 200 - success. This status code indicates that IIS has successfully processed the request. • 304 - Unmodified. The document requested by the client has not been modified since its cache. The client uses a cache copy of the document without downloading documents from the server. • 401.1 - Login failed. The login trial is unsuccessful, it may be invalid because the username or password is. • 401.3 - Due to the restriction of ACLs, no authorization is obtained. This indicates that there is an NTFS permission issue. This error may occur even if you have the corresponding permissions attempting to access. For example, if the IUSR account does not have to access 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:
187506 INFO: IIS 4.0 Basics NTFS Permissions
• 403.1 - Perform access is disabled. Below is two common causes that lead to this error message:
• You don't have enough execution licenses. For example, if the directory permissions where the ASP page attempts to access is set to "None", or that the directory permissions attempt to execute are "only allowed scripts", this error message will appear. To modify execution permissions, right-click on the directory in the Microsoft Management Console (MMC), then click Properties and Directory tabs to ensure that appropriate execution permissions are set to attempt to access. • You do not set the script map of the file type attempt to execute to identify the predicate used (for example, Get or POST). To verify this, right click on the directory in the MMC, click Properties, Directory tabs, and configuration, and then verify that the script mapping of the corresponding file type is set to allow the predicates used. • 403.2 - Read Access is disabled. 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:
247677 Error message: 403.2 Forbidden: Read Access Forbidden (403.2 Forbidden Access: Read Access is prohibited) • 403.3 - Write access is disabled. Verify that IIS permissions and NTFS permissions have been set to grant write access to this directory. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base:
248072 Error message: 403.3 Forbidden: Write Access Forbidden (403.3 Prohibited Access: Write access is disabled)
• 403.4 - Require SSL. Disable the requirements for secure channel options, or use HTTPS instead of HTTP to access the page. If this error occurs if there is no Web site where the certificate is installed, click the following article number to see the article in the Microsoft Knowledge Base:
224389 Error message: http error 403, 403.4, 403.5 Forbidden access: Request SSL
• 403.5 - Require SSL 128. Disable requirements 128-bit encryption options or use a 128-bit encrypted browser to view the page. If this error occurs if there is no Web site where the certificate is installed, click the following article number to see the article in the Microsoft Knowledge Base:
224389 Error message: http error 403, 403.4, 403.5 Forbidden access: Request SSL
• 403.6 - IP address is rejected. You have configured your server to refuse to access 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:
248043 Error message: 403.6 - Forbidden: ip address rejected (403.6 - Unavailable: IP address is rejected)
• 403.7 - Require client certificate. You have configured your server to require client authentication certificates, but you don't have a valid client certificate. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
190004 Error 403.7 or "Connection TO Server Could Not Be Established" (connection to the server)
186812 PRB: Error message: 403.7 Forbidden: Client Certificate Required (403.7 Forbidden Access: Require client certificate)
• 403.8 - Site Access is rejected. You have set a domain name limit for you to access the server's domain. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base:
248032 Error message: Forbidden: Site Access Denied 403.8 (Forbidden Access: Site Access is denied 403.8)
• 403.9 - too much user number. The number of users connected to the server exceeds the connection restrictions you set. For additional information about how to change this limit, click the article number below to see the article in the Microsoft Knowledge Base:
248074 Error message: Access forbidden: Too Many Users Are Connected 403.9 (Disable Access: Too many users connected to 403.9)
Note: Microsoft Windows 2000 Professional and Microsoft Windows XP Professional automatically sets up to 10 connections on IIS. You cannot change this limit. • 403.12 - Reject the access mapping table. The page you want to access requires a client certificate, but the user ID that is mapped to your client certificate has been denied the file. For additional information, click the article number below to see the article in the Microsoft Knowledge Base: 248075 Error Message: HTTP 403.12 - Access Forbidden: Mapper Denied Access (HTTP 403.12 - Disable Access: Map Table Reject Access)
• 404 - Not found. This error occurs because the file you try to access has been removed or deleted. This error occurs after you try to access a file with a limited extension after installing the URLSCAN tool. In this case, the words "Rejected by Urlscan" will appear in the log file item of the request. • 500 - Internal server error. Many server-side errors can cause this error message. The event viewer log contains a more detailed reason. In addition, you can disable friendly HTTP error messages to receive a detailed error description. For additional information about how to disable friendly HTTP error messages, click the article number below to see the article in the Microsoft Knowledge Base:
294807 How to disable the "Show Friendly HTTP Error Message" feature on the server ternet Explorer 5
• 500.12 - The application is restarting. This means that you try to load the ASP page during the IIS restarting the application. After refreshing the page, this information will disappear. If the page is refreshed, this information appears again, it may be that the anti-virus software is scanning the Global.asa file. For additional information, click the article number below to see the article in the Microsoft Knowledge Base:
248013 Error message: http error 500-12 Application Restarting (HTTP error 500-12 application is restarting)
• 500-100.asp - ASP error. This error message will appear if you try to load the ASP page containing an error code. To get more exact error messages, disable friendly HTTP error messages. By default, this error message will only be enabled on the default Web site. For additional information about this error message on a non-default Web site, click the article number below to view the article in the Microsoft Knowledge Base:
261200 Displays the HTTP 500 error message without displaying the 500-100.asp ASP error message
• 502 - Gateway error. This error message will appear if the CGI script attempts to run does not return a valid HTTP header set.
FTP
1xx - affirmative initial reply
These status code indicates that an operation has started successfully, but the client wants to get another reply before continuing the new command.
• 110 Restart the tag reply. • 120 service is ready, start after NNN minutes. • 125 Data connection is turned on and is starting to transfer. • 150 file status is normal, ready to open data connections.
2xx - affirmative completion reply
A operation has been successfully completed. The client can perform a new command.
• 200 Command OK. • 202 The command is not executed, excessive 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 Service Ready, you can perform new users' requests. • 221 Service Close Control Connection. If appropriate, please log out. • 225 Data connection opens, no transmission in progress. • 226 Turn off the data connection. The requested file operation has been successful (for example, transfer file or abandon file). • 227 enters passive mode (H1, H2, H3, H4, P1, P2). • 230 users have logged in and proceed. • 250 The file operation is correct and has been completed. • 257 has created "pathname". 3xx - affirmative intermediate reply
This command has been successful, but the server needs more information from the client to complete the process of request.
• The 331 username is correct and needs a password. • 332 You need to log in to your account. • 350 requested file operations are waiting for further information.
4XX - Transient negation completion reply
This command is unsuccessful, but the error is temporary. If the client retry command, it may be successful.
• 421 Service is not available and is closing the control connection. If the service determines that it must be turned off, this answer will be sent to any command. • 425 Unable to open data connections. • 426 Connection Closed; Transfer Aborted. • 450 No request file operation. The file is not available (for example, the file is busy). • 451 The operation of the requested operation is terminated: the local error is being processed. • 452 Operation of the request is not executed. System storage space is not enough.
5xx - permanent negative completion reply
This command is unsuccessful, and the error is permanent. If the client returns the command, the same error will occur again.
• 500 syntax errors, commands cannot be identified. This may include errors such as the command line too long. • 501 There is a syntax error in the parameter. • 502 Operation commands. • 503 Errors command sequence. • 504 The command does not perform this parameter. • 530 is not logged in. • 532 Storage file requires an account. • 550 Operation of the requested request. Files are unavailable (for example, no files found, no access rights). • 551 The operating exception is terminated: unknown page types. • 552 Request file operation exception termination: beyond the storage assignment (for the current directory or dataset). • 553 Operation of the requested request. The file name that is not allowed.
Common FTP status code and reason
• 150 - FTP uses two ports: 21 for sending a command, 20 is used to send data. Status code 150 indicates that the server is ready to open a new connection on the port 20, send some data. • 226 - Command Opens the data connection on port 20 to perform operations, such as transferring files. This operation is successfully completed, and the data connection is closed. • 230 - After the client sends the correct password, display the status code. It indicates that the user has successfully logged in. • 331 - After the client sends the user name, the status code is displayed. The status code will be displayed regardless of whether the username provided is a valid account in the system. • 426 - Command Opens the data connection to perform the operation, but the operation has been canceled, the data connection is closed. • 530 - This status code indicates that the user cannot log in because the username and password combination are invalid. If you log in with a user account, you may type an erroneous username or password, or you may choose to allow anonymous access. If you log in with an anonymous account, IIS configuration may refuse anonymous access. • 550 - The command is not executed because the specified file is not available. For example, the file to be Get does not exist, or attempt to use the file PUT to you without a write permission.
reference
To get more information about HTTP status code, please visit the following Web Federation (W3C) Web Site: Status Code Definition
http://www.w3.org/protocols/rfc2616/rfc2616-sec10.html#sec10
To get more information about the FTP status code, check the 4.2 section of the following W3C Web site ("FTP Answer"):
File transfer function
http://www.w3.org/protocols/rfc959/4_filetransfer.html
The information in this article applies to:
• Microsoft Internet Information Server 4.0 • Microsoft Internet Information Services 5.0 • Microsoft Internet Information Services 6.0 • Microsoft Internet Information Services 5.1
