. If the web site directory contains the global. Asa file, change the file name to global. Old. Restart the web service and write the following code in Notepad (no code in the original article, The simplest ASP source code can be used. The file is saved as test. asp in the Web root directory. If the ASP file can be executed normally, the problem lies in global. Asa, If not, go to step 2. Refer to the following Microsoft Knowledge Base for more information about errors in the global. Asa file. Q282135 PRB: Global. Asa does not fire from personal Web server on Windows 98 Q265275 fp2000: Global. Asa does not run in FrontPage Web Q173742 fix: Global. ASA is not executed if restricting Web Access 2. Set the application protection level of the web site to "low" and restart the IISADMIN service. If the ASP file can be executed normally, the problem lies in the IWAM user, Please proceed to step 3. If not, check the component service in the management tool to ensure that IIS packages is displayed, Make sure that the component service does not fail. Check that the following users exist in the local user group: Nt authority/Authenticated Users Nt authority/interactive For more information about component service errors, refer to the following articles: Q301919 PRB: cannot expand 'My Computer 'in component services MMC snap-in 3. if the ASP file can be normally executed in step 2, set the application protection level of the site to "medium" or "high", and add the IWAM user to the local administrator user group, the ASP file can be normally executed, indicating that the access permission of IWAM users is incorrect. Please go to Step 4. If the ASP file is not properly executed, execute synciwam in the command prompt. vbs tool. Method: Open the Command Prompt window and type the following command: C:/inetpub/adminscripts> cscript synciwam. vbs. If the ASP file cannot be executed properly due to an incorrect IWAM user (configuration), refer to the following knowledge base. Q308622 how to: perform administration tasks in IIS from a command prompt Q297989 PRB: configured identity is incorrect for IWAM account Q255770 PRB: logon Failure: Unknown user name or bad password when you run out-of-process Webs Q236007 Domain Controller demotion causes out-of-process applications to fail 4. Solve IWAM user permission issues, please use Windows 2000 third-party products: regmon and Filemon. Please download these tools in http://www.sysinternals.com. These tools are run when you execute ASP page requests. The dllhost.exe process searches for "accdenied" in regmon ("failure" in Filemon "). Note: Do not be nervous when the IE process Encounters "Operation Failure". This is just a common phenomenon .~~ For the minimum conditions required for the normal operation of IIS functions, refer to the knowledge base: Q271071 minimum NTFS permissions required for IIS 5.0 to work After reading the error message of the dllhost.exe process "operation failed", use regedit32 to modify any required NTFS permission in the registry (as if it was an exception, Khan ...) 5. After iis5.0 is installed, view ASP or HTML files from the Web server console or workstation on other networks. The web service may return the following error message: HTTP 500 internal server error. The default web service may be running. If you run netstat-An, you may notice that the Web server is listening to port tcp80, that is, the default http port. Note: If you are using ie5.0 (or a later version, the Translator's note), you may have blocked the show friendly HTTP Error Message option in IE advanced options. For more information, see Microsoft Knowledge Base: Q218155 description of Hypertext Transport Protocol Error messages The following several logs may appear in the event log containing the iis5.0 machine: Application log: COM + error with event ID 4099 System log: W3SVC error with event ID 59 System log: W3SVC warning with event ID 36. The iis5.log file (under the WINNT directory) may contain the following error message: 0x8004e00f = COM + was unable to talk to the Microsoft Distributed Transaction Coordinator You are trying to open the component service used by the COM + manager and the MMC stops responding. Cause Iis5.0 depends on COM +, COM + depends on Distributed Transaction Coordinator (DTC) Service running, and DTC checks the version mechanism (including SQL Server versions earlier than Windows 2000) the version attribute used by Windows 2000 cannot be identified. As a result, the SQL Server DTC installer removes the DTC service installed in windows. For more information, see the Microsoft Knowledge Base: Q249310 BUG: Installing SQL Server on Windows 2000 uninstalldtc Service Solution To solve this problem, follow these steps: A.verify whether dtcsetup.exe (in C:/winnt/system32 by default) is of the later version or later version. B .run dtcsetup.exe to install the DTC service C. Start the DTC service (MSDTC-resetlog) and then start the service. ) D. on the control panel, double-click "add delete program" E. Select "add and delete Windows components", remove iis5.0, and reinstall. Status quo Microsoft has confirmed that this is a problem in SQL Server versions 6.5 and 7.0 and MSDE 1.0. For details, see the article: Http://support.microsoft.com/default.aspx? SCID = KB; en-US; q252137 6. Last Resort: follow the steps below to create your own IIS packages A. Browse component services to delete the following packages A. IIS In-process applications B. IIS Out-of-process pooled applications C. IIS utilities B. Open the command prompt, go to the folder % WINDIR %/system32/inetsrv, and execute the command: Rundll32 wamreg. dll, createiispackage Note: createiispackage is case-sensitive and is correct. C. Re-open the component service. You will see that the iis com + application has been re-created. D. Run iisrestart from the command prompt and test any ASP files that were not correctly executed before. |
