The IIS server cannot run ASP program.

IIS server is a basic Internet service provided by Microsoft based on Microsoft Windows. It was originally an Optional package for the Windows NT version and was subsequently released together with Windows 2000, Windows XP Professional, and Windows Server 2003. However, IIS is not available in the commonly used Windows XP Home version.

Before analyzing the problem, first try to access the pure static webpage in the website (pages suffixed with htm or html). If it cannot be displayed normally, it means that the problem is not on ASP itself.

Check the settings of the IIS server to see if "application settings-execute permissions-script only" is set, and "configuration- ing" contains the asp extension. After the IIS server is correctly set, perform the following steps.

1. If the website itself has Global. asa, change it to Global. old and restart the website. Use NotePad to write down the code and save it as a test. asp file, which can be accessed in a browser. If the display is normal, 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 IIS server admin thread. If the ASP page can be read in the browser, the IWAM account is faulty. If you still cannot access the ASP page, check "component service" of "Administrative Tools" to ensure that you can see the IIS server package.

Note: If the component service cannot be opened (probably because the application is full of CPU), add or delete the component service on the control panel, add or delete the component service again, and restart the computer.

3. Return application protection to "medium" or "high" and add the IWAM account to the Administrator group. If the ASP page can be viewed at this time, IWAM has a permission problem. If ASP still cannot be displayed normally, run Synciwam. vbs in the DOS window using command lines.

C: \ Inetpub \ adminscripts> cscript synciwam. vbs

4. Solve the Problem of IWAM account permissions. Well, this is a long talk and I will post an article separately later.

5. Re-establish the IIS server packages method:

Delete the following packages in the component service
IIS server In-Process Applications
IIS server Out-of-Process Pooled Applications
IIS server Utilities

Enter the following command in the DOS window to recreate the package
% Windir % \ system32 \ inetsrv rundll32 wamreg. dll, Create IIS Package

Turn off the component manager and open it again. After seeing the three new packages, restart the IIS Server (iis reset) to check whether ASP Web pages can be viewed normally.