IIS常见错误代码

IIS常见错误代码
IIS introduction
When a user attempts to file transfer protocol (FTP) access via HTTP or a running Internet information services (IIS) of the content on the server, IIS the request returns a said the state of the digital code. The status code is logged in the IIS log and may also be displayed on the Web browser or FTP client. The status code can indicate whether the specific request has been successful and can also reveal the exact cause of the request failure.
By default, IIS puts its log files in the Windows \ \ System32 \ \ Logfiles folder. Each WWW site and FTP site has a separate directory under that directory. By default, log files are created in these directories each day, and the log files are named (for example, exYYMMDD. Log).
HTTP code
1x-information tip: these state codes represent temporary responses. The client should be ready to receive one or more 1xx responses before receiving the regular response.
100 -
101-switching protocol
2xx - success: this status code indicates that the server successfully accepts the client request.
200 - determines the status code that indicates that IIS has successfully processed the request
201 - has been created
202 - accepted
203-non-authoritative information
204 - nothing
205 - reset content
206 - part of it
3xx - redirect: the client browser must do more to implement the request. For example, the browser might have to request a different page on the server or repeat the request through the proxy server.
300 - multiple options
301 - has been removed forever
302 - the object has been found and moved
303 - see other terms
304 - the document that does not modify the client request is in the client cache, and the document has not been modified since the cache. The client USES the cached copy of the document
without downloading the document from the server.
305 - use the agent
306 - this code has been retained but not used
307 - temporary redirects
4xx - client error: error occurred, client problem. For example, the client request does not exist and the guest does not provide valid authentication information.
400-error request
401 - access is rejected
IIS defines a number of different 401 errors that specify more specific error reasons. These specific error codes are displayed in the browser, but not in the IIS log:
401.1-login failed login attempts, possibly because the user name or password is invalid.
The 401.2-server configuration failed to login
3, 401.3 - there is an NTFS permission problem because of the limitation of the ACL to the resource. This error may occur even if you have the appropriate permissions for the file you are trying to access. To solve this problem, see the corresponding article in the Microsoft knowledge base: 187506 List of NTFS Permissions Required for IIS Site to Work (the List of NTFS
Permissions Required for the IIS Site Work)
401.4 - filter authorization failed
The 401.5-isapi/CGI application authorization failed
401.7 - access is rejected by the URL authorization policy on the Web server
403 - no access
IIS defines a number of different 403 errors, which specify more specific error reasons, see 403.x code
404 - not found
The reason for this error is that the file you are trying to access has been removed or removed. This error occurs when the URLScan tool is installed to try to access files with a limited extension. In this case, the name "Rejected by URLScan" appears in the log file item of the request.
404.0 - no files or directories are found
404.1 - you can't access the Web site on the requested port
The 404.2-web service extension locking policy prevents this request
4, 404.
The 3-mime mapping policy prevents this request
405 - the HTTP predicate that is used for accessing this page is not allowed (the method is not allowed)
406 - the client browser does not accept the MIME type of the requested page
407 - requires agent authentication
412-premise failure
413 - the request entity is too large
414 - the request URI is too long
415-unsupported media types
416 - the scope of the request cannot be satisfied
417 - execution failure
423 - lock error
5xx - server error: the server cannot complete the request because of error
500-internal server error
Many server-side errors can lead to this error message. The event viewer log contains more detailed errors. In addition,
you can disable the friendly HTTP error message to receive detailed error instructions. Other information about how to disable the HTTP friendly error message, check in the Microsoft knowledge base article: 294807 how to disable Internet Explorer 5 at the server end "show friendly HTTP error message" function
500.12 - the application is busy restarting on the Web server
This means that you are trying to load the ASP page while IIS restarts the application. Once the page is refreshed, this information disappears. Once the page is refreshed, the message appears again, possibly with anti-virus software scanning global.asa. For additional information, see the corresponding article in the Microsoft knowledge base: 248013 HTTP Error 500-12 Application Restarting (HTTP Error 500-12 applications are being restarted)
The 500.13-web server is too busy
500.15 - no direct request for Global. Asa
The 500.16-unc authorization credentials are incorrect (IIS6.0 proprietary)
500.18-url authorization storage cannot be opened (IIS6.0 proprietary)
500.100 - internal ASP error
This error message will occur if you try to load the ASP page with error code. For more accurate error information, disable
the friendly HTTP error message. By default, this error message is only enabled on the default Web site. How about in the default Web site to see the error information of the other information please check phase should be in the Microsoft knowledge base article: 261200 shows the HTTP 500 error message and not the 500-500. The asp asp error information.
The author thinks that there is a problem of directory permissions or no parent path.
The 501-header value specifies the unimplemented configuration
502 - the Web server received an invalid response (gateway error) as a gateway or proxy server
This error message will occur if the CGI script that is trying to run does not return a valid HTTP header set.
502.1 - CGI application timeout
502.2-cgi application error
503 - service unavailable (IIS6.0)
504-gateway timeout
The 505-http version is not supported
FTP code
1 xx - certainly the preliminary answer: these status code
indicates an operation has been successful, but the client hope to continue to operate a new command before receive another answer.
110 restart the tag reply
The service is ready to start after NNN minutes
125 data connection is open and transmission is starting
150 file status is normal, ready to open the data connection
FTP USES two ports: 21 to send commands and 20 to send data. The status code 150 indicates that the server is ready to open a new connection on port 20 and send some data.
2xx - positive reply: an operation has been successfully completed. The client can execute the new command.
200 command set
No command is executed. There are too many orders on the site
211 system status, or system help reply
212 directory
213 file status
214 help message
The 215 NAME system type, in which NAME is the official system NAME listed in the Assigned Numbers document
220 service ready,
New user requests can be executed
221 service closes the control connection. If appropriate, please log out
225 data connection open, no transmission in progress
Close the data connection. The requested file operation has been successful (for example, transferring files or dropping files)
The command opens the data connection on port 20 to perform the operation, such as the transfer file. The operation completes successfully and the data connection is closed.
227 enter the passive mode (h1, h2, h3, h4, p1, p2)
230 users are logged in and continue
After the client sends the correct password, the status code is displayed. It indicates that the user has logged in successfully.
The requested file operation is correct and completed
The "PATHNAME" has been created.
3xx - positive reply: the command has been successful, but the server needs more information from the client to complete the processing of the request.
331 user name is correct, need password
After the client sends the user name, the status code is displayed. The status code will be displayed regardless of whether the supplied user name is a valid account in the system.
332 requires a login account
The file operation of the 350 request is waiting for further information
4xx - transient negative reply: this command is not successful, but the error is temporary. If the client retries the order, it may execute successfully.
421 service unavailable, closing control connection
425 cannot open data connection
426 the Connection closed; Transfer aborted
The command opens the data connection to perform the operation, but the operation has been canceled and the data connection is closed.
File operation of 450 unexecuted requests. File unavailable
(for example, busy file)
451 requested operation exception termination: local error is being processed
The operation of the request is not performed. The system storage space is not enough
5xx - the complete answer to the negative: the order is not successful and the error is permanent. The same error will occur again if the client retries the command.
500 syntax error, command is not recognized. This may include errors such as the command line too long
501 has syntax errors in the parameters
502 did not execute the command
503 wrong sequence of commands
504 no command to execute the parameter
530 not logged in
The status code indicates that the user cannot log in because the user name and password combination are invalid. If you log in with a user account, you may enter the wrong user name or password, or you may choose to only allow anonymous access. If an anonymous account is used, the IIS configuration may reject anonymous access.
532 storage files need accounts
The operation of 550 does not perform the request. File unavailable (for example, no file, no access)
The command is not executed because the specified file is not available. For example, the file that you want to GET doesn't exist, or you try to PUT the file into a directory where you don't have access to it.
The operation of the request is aborted: the unknown page type
File operation exception termination for 552 requests: beyond the storage allocation (for the current directory or data set)
The operation of 553 not performing the request. File names that are not allowed。