HTTP 400, 404, 500, 502 error causes and workarounds for server

Basically covers all the issues
Invalid HTTP 400– request
HTTP 401.1– not authorized: Logon failed
HTTP 401.2– not authorized: Login failed due to server configuration problem
HTTP 401.3–acl prohibit access to resources
HTTP 401.4– not authorized: Authorization denied by filter
HTTP 401.5– not authorized: ISAPI or CGI authorization failed

http 403– Forbidden Access to the
HTTP 403– access to Internet Service Manager is limited to Localhost
HTTP 403.1 Forbidden: Disable Access
HTTP 403.2– Forbidden: Disable Read access
HTTP 403.3– Forbidden: Prohibit write access
HTTP 403.4– Forbidden: Require SSL
HTTP 403.5– Forbidden: Requires SSL +
HTTP 403.6– Forbidden: IP address denied
HTTP 403.7– Forbidden: Require client certificate
HTTP 403.8– Forbidden: Prohibit site access
HTTP 403.9– Forbidden: Too many users connected
http 403.10– Forbidden: Invalid configuration
HTTP 403.11– Forbidden Stop access: Password change
http 403.12– Forbidden: Mapper denied access
HTTP 403.13– Forbidden: Client certificate revoked
HTTP 403.15– Forbidden: Too many client access Licenses
HTTP 403.16– Forbidden : Client certificate is untrusted or invalid
http 403.17– Forbidden: The client certificate has expired or has not yet been in effect HTTP 404.1-

cannot find Web site
HTTP 404-Cannot find file
HTTP 405– Resource Forbidden
http 406– unacceptable
HTTP 407– require proxy authentication
HTTP 410– never available
http 412– Prerequisite Failure
HTTP 414– request –uri too long

http 500– Internal Server error
HTTP 500.100– Internal Server error –asp error
http 500-11 server shutdown
HTTP 500-12 application Restart
HTTP 500-13– Server Too busy
HTTP 500-14– application is invalid
http 500-15– does not allow request Global.asa
Error 501– not implemented
HTTP 502– Gateway error

When a user tries 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 status of the request. This status code is logged 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 succeeded, and can reveal the exact cause of the request failure.
Location of log files
by default, IIS places its log files in the%windirsystem32logfiles folder. Each World Wide Web (WWW) site and an FTP site have a separate directory in that directory. By default, log files are created every day in these directories, and the log file is named with the date (for example, ExYYMMDD.log).
HTTP
1xx– information prompt

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– continues.
? 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– has been created.
? 202– has accepted.
? 203– non-authoritative information.
? 204– no content.
? 205– Reset the content.
? 206– part of the content.
3xx– redirection

The client browser must take more action to implement the request. For example, the browser might have to request a different page on the server, or repeat the request through a proxy server. The 302– object has been moved.
? 304– is not modified.
? 307– temporary redirection.
4xx– Client Error

The client appears to have a problem with the error. 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, which 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. The
? 401.2– server configuration causes logon failures.
? 401.3– is not authorized 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 specific to IIS 6.0.

? 403– Forbidden: IIS defines a number of different 403 errors that indicate a more specific cause of the error:

? 403.1– execution access is forbidden.
? 403.2– Read access is forbidden.
? 403.3– Write access is forbidden.
? 403.4– requires SSL. The
? 403.5– requires SSL 128. The
? 403.6–ip address is rejected. The
? 403.7– requires a client certificate.
? 403.8– site access is denied. The
? 403.9– has too many users. The
? 403.10– configuration is invalid.
? 403.11– password changes.
? 403.12– denies access to the mapping table. The
? 403.13– client certificate is revoked.
? 403.14– rejects the directory list. The
? 403.15– exceeds the Client Access License. The
? 403.16– client certificate is not trusted or invalid. The
? 403.17– client certificate has expired or is not yet valid.
? 403.18– cannot execute the requested URL in the current application pool. This error code is specific to IIS 6.0.
? 403.19– cannot execute CGI 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 files or directories found.
? 404.1– cannot access the WEB site 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– the HTTP verb used to access this page is not allowed (method not allowed)
? 406– the client browser does not accept the MIME type of the requested page. The
? 407– requires proxy authentication.
? 412– precondition failed. The
? 413– request entity is too large. The
? 414– request URI is too long. The
? 415– does not support media types. The range requested by the
? 416– cannot be satisfied.
? 417– execution failed.
? 423– locked error.
5xx– Server Error

The server could not complete the request because it encountered an error. 500– internal server error.? The 500.12– application is busy restarting on the WEB server.
? The 500.13–web server is too busy.
? 500.15– does not allow direct request for Global.asa.
? 500.16–unc authorization credentials are incorrect. This error code is specific to IIS 6.0.
? The 500.18–url authorization store cannot be opened. This error code is specific to IIS 6.0.
? 500.100– Internal ASP error.

? The 501– header value specifies the 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.
? 502.2–CGI Application error. Application.

? The 503– service is not available. This error code is specific to IIS 6.0.
? The 504– gateway timed out.
? 505–http version is not supported.

Common HTTP status codes and their causes
? 200– success. This status code indicates that the request was successfully processed by IIS.
? 304– not modified. The document requested by the client 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 instead of downloading the file from the server.
? 401.1– Login failed. The logon attempt was unsuccessful, possibly because the user name or password is invalid.
? 401.3– is not authorized due to ACL restrictions on resources. This indicates that there is an NTFS permission issue. 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 permission to access the C:winntsystem32inetsrv 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 base NTFS permissions for Info:iis 4.0
? 403.1– execution access is forbidden. The following are the two common causes of this error message:? You do not have sufficient permission to execute. For example, this error message occurs if you try to access an ASP page that has the directory permission set to None, or if you try to execute a CGI script that has the directory permission of "script only". To modify the execution permissions, right-click the directory in the Microsoft Management Console (MMC), then clicking the Properties and Directories tab, and then make sure that the appropriate execution permissions are set for the content you are trying to access.
? You have not set the script mapping of the file type you are trying to execute to recognize the verb (for example, GET or POST) that you are using. To verify this, right-click the directory in the MMC, clicking Properties, Directories tab, and configuration, and then verify that the script map for the appropriate file type is set to allow the verb to be 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:
247677 error message: 403.2 forbidden:read access Forbidden (403.2 Forbidden: Read access Forbidden)
? 403.3– Write access is forbidden. Verify that 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:
248072 error message: 403.3 forbidden:write access Forbidden (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 this error occurs on a Web site that does not have a certificate installed, click the following article number to view the article in the Microsoft Knowledge Base:
224389 error message: HTTP error 403, 403.4, 403.5 Forbidden: SSL Required
? 403.5– requires SSL 128. Disable the Require 128-bit encryption 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 following article number to view the article in the Microsoft Knowledge Base:
224389 error message: HTTP error 403, 403.4, 403.5 Forbidden: SSL Required
? The 403.6–IP address is 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:
248043 error message: 403.6–FORBIDDEN:IP address rejected (403.6– not available: IP address denied)
? 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:
190004 error 403.7 or "Connection to server Could not being established" (unable to establish a connection to the server)
186812 PRB: Error message: 403.7 forbidden:client Certificate Required (403.7 Forbidden: Require client certificate)
? 403.8– site access is 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:
248032 error message: Forbidden:site access Denied 403.8 (Forbidden: Site access denied 403.8)
? 403.9– too many users. The number of users connected to the server exceeds the connection limit that you set. For additional information about how to change this limit, click the following article number to view the article in the Microsoft Knowledge Base:
248074 error message: Access Forbidden:too Many users are Connected 403.9 (forbidden: Too many users connected 403.9)
Note Microsoft Windows Professional and Microsoft Windows XP Professional automatically set a limit of up to 10 connections on IIS. You cannot change this limit.
? 403.12– denied access to the 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 access to the file. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
248075 error message: HTTP 403.12–access forbidden:mapper Denied access (HTTP 403.12– Forbidden: Mapping table denied access)
? 404– not found. This error occurs because the file that you are trying to access has been moved or deleted. This error can also occur if you try 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 a more detailed cause of the error. Additionally, you can disable friendly HTTP error messages in order 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:
294807 How to disable the "show friendly HTTP error Messages" feature on the server side of Internet Explorer 5
? 500.12– the application is restarting. This indicates that you attempted to load an ASP page during IIS restart of the application. When the page is refreshed, this information disappears. If this information appears again after the page is refreshed, the antivirus software may be scanning the Global.asa file. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
248013 Error message: HTTP error 500-12 Application restarting (HTTP 500-12 application is restarting)
? 500-100.asp–asp error. This error message appears if you try to load an ASP page that contains an error code. To obtain a more accurate error message, disable the friendly HTTP error message. By default, this error message is only enabled 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:
261200 displays an HTTP 500 error message without displaying the ASP error message for 500-100.asp
? 502– Gateway error. This error message occurs if the CGI script that you are trying to run does not return a valid set of HTTP headers.

Ftp
1xx– a definite initial reply

These status codes indicate that an operation has started successfully, but the client wants to get another reply before continuing with the new command. 110 Restart Tag reply.
? 120 service is ready, starting in nnn minutes.
? 125 The data connection is open and the transfer is starting.
? 150 file status OK, ready to open data connection.
2xx– sure to complete the reply

An operation has been successfully completed. The client can execute the new command. 200 command OK.
? 202 The command is not executed and there are too many commands on the site.
? 211 system Status, or system help reply.
? 212 Directory status.
? 213 file status.
? 214 Help message. The
? 215 Name System type, where name is the formal system name listed in the Assigned Numbers document.
? 220 service is ready to execute requests from new users. The
? 221 Service closes the control connection. If appropriate, please log out.
? 225 data connection open, no in-progress transfer.
? 226 closes the data connection. The requested file operation was successful (for example, transferring a file or discarding a file).
? 227 enters 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 created "PATHNAME".
3xx– a positive intermediate reply

The command was successful, but the server needs more information from the client to complete the processing of the request. 331 user name is correct, password required.
? 332 You need to log in to your account.
? 350 The requested file operation is waiting for further information.
4xx– Transient negation Completion reply

The command is unsuccessful, but the error is temporary. If the client retries the command, it may execute successfully. 421 service is not available and the control connection is shutting down. If the service determines that it must be closed, this response is sent to any command.
? 425 The data connection cannot be opened.
? 426 Connection closed; Transfer aborted.
? 450 The requested file operation was not performed. The file is not available (for example, the file is busy).
? 451 requested operation aborted: Local error is being processed.
? 452 the requested operation was not performed. The system does not have enough storage space.
5xx– permanent negation of complete reply

The command is unsuccessful and the error is permanent. If the client retries the command again, the same error will occur again. 500 syntax error, command not recognized. This may include errors such as the command line being too long.
? 501 has a syntax error in the argument.
? 502 The command was not executed.
? 503 error sequence of commands.
? 504 does not execute the command for this parameter.
? 530 is not logged in.
? 532 The storage file requires an account.
? 550 The requested operation was not performed. The file is not available (for example, the file was not found and no access was granted).
? 551 requested operation aborted: unknown page type.
? 552 requested file operation terminated abnormally: storage allocation exceeded (for current directory or dataset).
? 553 The requested operation was not performed. The file name is not allowed.

Common FTP status codes and their causes
? The 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 and send some data.
? The 226– command opens a data connection on port 20 to perform operations, such as transferring files. The operation completed successfully and the data connection is closed.
? After the 230– client sends the correct password, the status code is displayed. It indicates that the user has successfully logged on.
? The status code is displayed after the 331– client sends the user name. The status code is displayed regardless of whether the provided user name is a valid account in the system.
? The 426– command opens the data connection to perform the operation, but the operation has been canceled and the data connection is closed.
? 530– The status code indicates that the user cannot log on because the user name and password combination is not valid. If you are logged on with a user account, you might 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 550– command was not executed because the specified file is not available. For example, the file you want to get does not exist, or you try to put the file into a directory where you do not have write permission.

HTTP 400, 404, 500, 502 error causes and workarounds for server