IIS installation and configuration problems

Solution for zclientm.exe not found during iis5.1installation

Default category: 11:26:33 read 302 comments 0 font size:Medium and largeSmall

Solution for zclientm.exe not found during iis5.1installation

Solution for zclientm.exe not found during iis5.1installation

 

I tried to install IIS 5.1xpversion on my home this day. I tried multiple times to find the file zclientm.exe, I have repeatedly uninstalled and uninstalled the installation, that is, it cannot be installed. Next we will teach you how to correctly install IIS. For website development, it is best not to take a look. First, open the control panel: Click Add and delete programs. Click add and delete WINDOWS components on the left.   In fact, the check box of the internet information service was not checked at the beginning. We just need to check it and click Next. In the next step, if a file is missing, you only need to click browse and select your IIS installation path. If it is an xp version, a prompt is displayed: If you cannot find the dialog box for zclientm.exe, you don't have to worry about it. In this case, we will return to the windows build wizard. Double-click the attachment and tool, The attachment and tool dialog box is displayed, and double-click the game option. In this case, the INTERNET Game check box is removed.   Click OK all the way. Haha, the installation is successful and the problem is solved! Final result: To complete debugging of an ASP program, you must configure the local Server IIS (Internet Information Server). However, after installing the IIS component, assign the local IP address, local path, and enable the default document, open the browser and enter 127.0.0.1. The expected webpage is not opened and an error occurs during access. Open Control Panel> Administrative Tools> Internet Information Service and find that the default website is stopped. Right-click the website and select start from the expanded menu ", however, the following error occurs: "Unexpected error 0x8ffe 2740", IIS cannot be started! Go to the Event Viewer and find the w3svc service error in the system. view the details as follows: The service cannot bind instance 1. The returned data is an error code. For more information about this message, visit the Microsoft online support site: http://www.microsoft.com/contentredirect.asp. Go to Start> Run, Enter cmd, enter the dos window, and enter the following command to view port usage: C: \ Documents ents and settings \ test> netstat-ano Find the port 80 used by IIS: Proto Local Address Foreign Address state PID TCP 0.0.0.0: 80 0.0.0.0: 0 LISTENING 2306 The PID is 2306. Open the task manager, select the "process" tab item, click "View"> "Select column" in the menu, and tick the "PID (process identifier)" item, in the "process" list, the PID column is displayed. Click here, sort by PID from small to large, and find the "image name" corresponding to PID = 2306, it turned out to be WebThunder )! That is to say, port 80, which should have been used by IIS, is now occupied by WebThunder. No wonder IIS errors. Click the Web Thunder icon in the system taskbar in the lower-right corner to open the Web Thunder local page, and click "Settings-> BT/Port Settings ", we can see that its TCP port setting is exactly 80 (this is obviously a mistake in Web Thunder's design. Port 80 is the default IIS port. For web application developers, the local IIS is often used to debug the program, and the default port 80 is usually used. Therefore, no software, including web Thunder, should use 80 by default, but should select an uncommon port, such as 5999. In short, the general default settings that do not affect existing programs should be the basic design principle ). I didn't care, so I re-installed the IIS component according to the old method. The problem still exists. It turns out that the "Thunder" Network download software installed on my computer occupies the default TCP port 80, the configuration conflict with IIS causes IIS to fail to be enabled. The solution is available immediately. There are two simple solutions: (1) uninstall the "Thunder" software, restart the computer, open the browser, enter 127.0.0.1, OK! Problem solving; (2) Change the TCP port of IIS to 100. Open the browser and enter 127.0.0.1: 100. The problem is also solved! Bytes ----------------------------------------------------------------------------------------------------- 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. It's thunder. it's useful to shut down Thunder! ^_^... This problem also occurs to me. I can open it normally after I saw the thunder off just now. (I personally did not install thunder. This also happens)