Unable to run ASP program under IIS

  
                  

Before analyzing the problem, try to access the pure static webpage in the website (the suffix with htm or html). If it is not displayed properly, the problem itself is not on the ASP.

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

1. If the website itself has Global.asa, rename it to Global.old and restart the website. Write the code in Notepad and save it as a test.asp file, which is accessed in the browser. If it can be displayed normally, the problem is in the Global.asa file.

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

2, set the application protection to "low", restart the IISadmin thread, if you can browse at this time The ASP page is read out, indicating that there is a problem with the IWAM account. If you still can't access the ASP page, check the "Component Services" of the "Administrative Tools" and make sure you can see the IIS package.

Attachment: If you encounter component service can not open (may be caused by the application full CPU), add and delete in the control panel, re-add the remove 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, IWAM has a permission problem. If ASP still does not display properly, run the Synsiwam.vbs tool in the DOS window using the command line.

C:\\Inetpubadminscripts>cscript synciwam.vbs

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

5, re-establish the IIS packages method:

Delete the following packages in the component service

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%\\system32\\inetsrv rundll32 wamreg.dll, CreateIISPackage

Turn off the component manager and re-open it. After seeing the three newly created packages, restart IIS (IISRESET) to check if the ASP page can be browsed normally.

Copyright © Windows knowledge All Rights Reserved