What should I do if I cannot run the ASP program in the IIS environment?

How to install IIS

Step one: Installation of IIS

A. Select "Add/Remove Programs" in the Control Panel and select "Add/Remove Windows Components" in the dialog box that appears.

B. Select to install Internet Information Services (IIS) in the check box that appears. This component requires about 19MB of space.

C. Click "Next" and put the Win2000 installation CD into the CD-ROM drive. The installation program will copy the program files to the hard disk. Click "End" to complete.

Step 2: Basic configuration of the Web server in IIS

The basic configuration of the Web server in IIS mainly includes the following parts:

A. Open the configuration window of the IIS server, select "Start" → "Programs" → "Administrative Tools" → "Internet Service Manager", or "Select" → "Control Panel" → "Administrative Tools" → "Internet Service Manager" "Also, the opened window is as shown in Figure 3.

B. Right-click "Default Web Site" in the window that opens and select the "Properties" menu.

C. In the "Default Web Site Properties" window that appears, select the "Home Directory" tab to set the location of the Web content on the hard disk. The default directory is "C:InetpubWwwroot". You can set it yourself according to your needs. (Figure 4).

D. Select the "Document" tab in the properties window, set your default home page name, such as "Myfirstweb.htm", add it and move it to the top of the list (Figure 5).

E. Confirm whether the default Web site has been started. If not, right-click "Default Web site", select "Start", and type the IP address of the machine in the opened IE address bar to see the home page you specified. It has started to be published on the Internet.

Here we only introduce the most basic setting options of IIS. You can also set the "Default Web Site Properties" mentioned above specifically according to your needs, and use it to configure the security and other parameters of IIS.

Although IIS is easy to use, it also has many security vulnerabilities when installed by default, including the famous Unicode vulnerabilities and CGI vulnerabilities. Therefore, after the IIS installation is completed, it is recommended to continue to download and install the security vulnerabilities they provide on the Microsoft homepage. Patches SP1 and SP2. In addition, it is recommended to convert the disk's file system to NTFS format. The partition where the system is installed can be converted during system installation, or it can be converted using tools such as PQMagic after the system is installed.

What is the number of IIS connections?

The number of IIS connections refers to the number of visits to port 80 by the accessed IP, which is the number of times the website file is called, and is not equivalent to the number of people online at the same time.

IIS connection number, I can introduce it like this: If a door is 4 meters and the average width of each person is 0.5 meters, then 8 people can be allowed to pass through the door at the same time. That is to say, the IIS of this door is 8. Within 10 minutes, maybe There are 100 people passing through this door, so the number of people online in this forum may be 100, and then IIS is 8. Does it mean that 8 people are allowed to request data in real time at the same time? No, because the programs are different, and each program occupies The number of IIS is also different. Maybe it is a 2-meter-wide fat man, so only 2 people can be allowed to pass at the same time. That is to say:

(1), IIS is the number of units requested at the same instant, which is not equal to IP.

(2) An IP may occupy multiple IISs at one time. For example, a fat man occupies 4 people's IISs.

(3) IIS refers to the number of simultaneous connections, while online statistics refers to the throughput. One refers to the number of people allowed to pass through the door at the same time, and the other refers to the number of people who entered the door during this time period. people.

IIS cannot run ASP program?

Before analyzing the problem, first try to access a purely static web page (page with htm or html as suffix) in the website. If it cannot be displayed normally, it means that the problem itself is not in ASP.

Check the settings of IIS to see if "Application Settings-Execution Permissions-Pure Script" is set and there is an asp extension in "Configuration-Mapping". After the IIS settings are checked and correct, proceed to the next steps.

1. If the website itself has Global.asa, first rename it to Global.old and restart the website. Use Notepad to write down the code and save it as a test.asp file and access it in the browser. If it can be displayed normally, the problem lies in the Global.asa file.

<%Response.Write "This is a test ASP page."%>

2. Set the application protection to "Low" and restart the IISadmin thread. If the ASP page can be read in the browser at this time, it means there is a problem with the IWAM account. If you still can't access the ASP page, check "Component Services" in "Administrative Tools" to make sure you can see the IIS package.

Attachment: If you encounter a component service that cannot be opened (may be due to the application occupying the CPU), go to Add and Remove in the control panel, re-add and delete the component service, and then restart the computer.

3. Return the application protection to "Medium" or "High" and add the IWAM account to the Administrator group. If the ASP page can be browsed at this time, it means that there is a permission issue with IWAM. If ASP still cannot be displayed normally, enter the DOS window and run the Synciwam.vbs tool from the command line.

C:Inetpubadminscripts>cscript synciwam.vbs

4. Solve the permission problem of IWAM account. Well, this is a long story. I will publish a separate article in the future.

5. Method to re-create IIS packages:

Remove the following packages in Component Services

IIS In-Process Applications

IIS Out-of-Process Pooled Applications

IIS Utilities

Use the DOS window to type the following command to re-create the package

%windir%system32inetsrv rundll32 wamreg.dll, CreateIISPackage

Close the component manager and reopen it. After seeing the three newly created packages, restart IIS (IISRESET) to check whether the ASP web page can be browsed normally.