Computer skills in IIS

1. Unable to start IIS [Unexpected error 0x8ffe2740] the error 0x8ffe2740 occurs when IIS is started because other programs occupy port 80 and change the default port of IIS to over 80, after the startup is successful, change it back to 80. If the restart is successful, there will be no error. If the 500 error occurs again, reinstall IIS to solve the problem. Cause: if the system stores

1. Unable to start IIS [Unexpected error 0x8ffe2740] the error 0x8ffe2740 occurs when IIS is started because other programs occupy port 80 and change the default port of IIS to over 80, after the startup is successful, change it back to 80. If the restart is successful, there will be no error. If the 500 error occurs again, reinstall IIS to solve the problem. Cause: if the system stores

1. IIS cannot be started. [Unexpected error 0x8ffe2740]
When IIS is started, the error 0x8ffe2740 occurs because other programs occupy port 80. You can change the default port of IIS to over 80. After IIS is started successfully, change it back to port 80, if the Error 500 occurs again, you can reinstall IIS to solve the problem.

Cause
This situation may occur if a port conflict exists in the system. by default, IIS uses port 80 for HTTP Communication. if the application except IIS is running and port 80 is being used on the same IP address, you may also receive this error message when trying to start the website using IIS manager.
Solution
To solve this problem, you can perform any of the following operations:
"In IIS manager, change the website binding port to a port other than port 80.
"Stop the application that is using port 80, and then start the website from IIS manager.
More information
You can use third-party tools such as TCPView or FPort to determine other applications that are using port 80.

If you do not know what program occupies port 80, use TCPView or fport to check what program. Turns out to be a Trojan!
If not, change the port.

Unexpected error 0x8ffe2740 in-depth analysis
After that, although the previous practice was successful, the iis stop still occurred every time after the computer was restarted.

To find out whether the administrator tools> service item was read this time
Use fport to find out the program svchost.exe that occupies port 80 and the pid of the program.
Pid Process Port Proto Path
1396 svchost-> 80 tcp c: \ WINDOWS \ System32 \ svchost.exe

Although the task manager can directly Delete the svchost.exe file of the pid.exe file, the same situation will occur after the next restart. That is to say, a program will call svchost.exe every time windows is restarted. What is it? Check the service and finally lock the target on mysee2_runtime. If [C: \ WINDOWS \ System32 \ svchost.exe-k mysee2] stops the service, iis can be restarted. To avoid this iis problem, you can also use mysee. You can only change this service to manual. It's really troublesome to watch the streaming media of mysee.

The problem persists after the restart.

2. Error code 400

Error 400 is caused by incorrect requests. It indicates that the webpage being searched may have been deleted, renamed, or temporarily unavailable.

Error code: 401.1

401.1 error is caused by logon failure. It indicates that you do not have the permission to view the directory or webpage.

Error code: 401.2

401.2 error is caused by server configuration problems, because the server script fails to correctly send the WWW authentication header file field. To complete this task using the Active Server Pages script, you can use the "AddHeader" method of the "Response" object to require the client to access resources using a specific authentication method.

Error code: 401.3

401.3 the error is caused by the ACL on the resource that is not authorized to access the webpage or directory.

Error code: 401.4

401.4 error is caused by filter Authorization failure. If the Web server has a filter program installed to check the users connected to the server. This filter program can prohibit access to resources through authentication connected to the server.

Error code: 401.5

401.5 error: Authorization failed due to ISAPI/CGI application. If an ISAPI or CGI program is installed on the Web server address to be accessed, it is used to verify the user certificate before the execution continues. This program can prohibit access to resources by connecting to the server's authentication certificate.

Error code: 403.1

403.1 error is caused by "execution" access being disabled. If you attempt to execute CGI, ISAPI, or other executable programs from the directory, however, this error occurs when the program cannot be executed in this directory.

Error code: 403.2

403.2 error is caused by the "read" access being disabled. This error occurs because no default webpage is available and directory browsing is not enabled for the directory, or the HTML webpage to be displayed resides in only the "executable" or "script" permission.

Error code: 403.3

403.3 error is caused by the "write" access being disabled. when attempting to upload a file to a directory or modify the file in a directory, however, this error occurs when the directory does not allow "write" access.

Error code: 403.4

403.4 error occurs because SSL is required. You must use "https" in the address of the webpage you want to view ".

Error code: 403.5

403.5 error is caused by a Web browser that uses the 128-bit encryption algorithm. If your browser does not support the 128-bit encryption algorithm, this error occurs, you can connect to the Microsoft website to upgrade your browser.

Error code: 403.6

403.6 error is caused by the rejection of the IP address. If the server contains a list of IP addresses that cannot access the site, and the IP address you are using is in this list, you will return this error message.

Error code: 403.7

403.7 error: the client certificate is required. This error is returned when the browser is required to have a Secure Socket Layer (SSL) client certificate recognized by the server.

Error code: 403.8

403.8 error is caused by disabling site access. If the server contains a list of DNS names that cannot access the site, this information is returned when the DNS name you use is in the list. Note the difference between error 403.6 and error 403.8.

Error code: 403.9

403.9 error is caused by too many connected users. Because the Web server is very busy, this error will be returned if the request cannot be processed due to too much communication.

Error code: 403.10

403.10 error is caused by invalid configuration. When you try to execute CGI, ISAPI, or other executable programs from the directory, however, this error is returned when the program cannot be executed in this directory.

Error code: 403.11

403.11 error is caused by a password change and you are not authorized to view the page.

Error code: 403.12

403.12 error is caused by the er's Access denied. If a valid client certificate is required for the Web page to be viewed, and your client certificate ing does not have the permission to access the Web site, an error that the denies access will be returned.

Error code: 403.13

403.13 error: the client certificate used because the webpage to be viewed requires a valid client certificate has been revoked, or the certificate cannot be determined whether it has been revoked.

Error code: 403.15

403.15 error is caused by a customer's excessive access permissions. This error is returned when the server exceeds the access permission limit of the customer.

Error code: 403.16

403.16 error is caused by the untrusted or invalid client certificate.

Error code: 403.17

403.17 error occurs because the customer certificate has expired or has not yet taken effect.

Error code: 404.1

404.1 error indicates that the IP address of the website to be accessed does not accept the port (source port of the request) request. Generally, a 404.1 error occurs only on a computer with multiple IP addresses. If a customer request is received on a specific IP Address/Port Combination and the IP address is not set to listen on a specific port, IIS returns the 404.1 HTTP Error. For example, if a computer has two IP addresses and only one of them is configured to listen on port 80, any requests received from other IP addresses from port 80 will cause IIS to return the 404.1 error. This error should be set only at the service level, because it is returned to the customer only when multiple IP addresses are used on the server.

Error code: 404b

The 404b error occurs because the file cannot be found. It is usually because the webpage being searched may have been deleted, renamed, or temporarily unavailable.

Error code: 405

405 error: the webpage address is incorrect because the resource is forbidden. Therefore, the webpage to be searched cannot be displayed.

Error code: 406

406 error is caused by the failure of the browser to open the resources being searched.

Error code: 407

407 error occurs because the proxy server must verify the identity before processing the request.

Error code: 410

410 error: the webpage to be searched has been permanently deleted, which means that the resource will never be used.

Error code: 412

412 error: the request cannot be completed because the webpage to be viewed has a prerequisite. Generally, one or more request header fields in a webpage have prerequisites. These fields are considered "FALSE" after being tested by the server ". The client sets a prerequisite for the meta information (header file field data) of the current resource to prevent the request method from being used to specify other resources other than the resource.

Error code: 414

414 error is caused by the request URI being too long and the server rejects the request. General possibilities include:

1) The client mistakenly converts a POST request to a GET request with long query information.

2) or the client encounters a redirection problem (for example, the prefix of the Redirection URL points to its own suffix ).

3) The server is attacked by a client, which attempts to exploit the security vulnerabilities on servers that use a fixed-length buffer to read or control the request URI.

Error code: 500

500 error is caused by an internal server error.

Error code: 500.11

500.11 error occurs because the server is shut down and the resources cannot be accessed. The Web site cannot process the requests when it is closed.

Error code: 500.12

500.12 error indicates that resources cannot be accessed due to application restart, and requests cannot be processed during Web site restart.

Error code: 500.13

500.13 error occurs because the server is too busy to process the request. The communication volume exceeds the capability of the Web site.

Error code: 500.14

500.14 errors are caused by Invalid applications and some Web sites are unavailable. The Web site application configuration is faulty and cannot process the request.

Error code: 500.15

500.15 error is caused by a request for global. asa that is not allowed to be requested. You can edit the URL in the "Address" column, delete global. asa, and press Enter. To solve this problem.

Error code: 502

The 502 error is caused by a Gateway error. When the server serving as the gateway or proxy contacts the upper-layer content server, the 502 error occurs when an invalid response is received.

Error code: 500-100.asp

-100.asp errors refer to ASP errors. By default, the "Default Web site" and all its applications send ASP error processes to the 500-100.asp file. However, any new Web site or application created by the user sends the 500.100 error process to the default (not custom) error file. If you want to develop additional error processes for the. asp file, you can map the 500-100 error to the. asp file, or create your own error process. asp file.

Any errors that occur during compilation and running of the. asp file. When an ASP error occurs, IIS returns the 500-100.asp file with detailed error information, such as the row number and description of the error.

If the file 500-100.asp contains an ASP error, ASP will not return another 500-100.asp file. In this way, when an error is reported, it seems that there is no custom error file corresponding to the 500-100 error.

If the error processing file (default: 500-100.asp) contains a runtime error, only this error is displayed, regardless of the Error Type in the. asp file requested. If the error processing file contains preprocessing and editing errors, the two errors are displayed in the browser (that is, errors in the 500-100.asp file and errors in the requested. asp file ).