http://dev.9cbs.net/Article/36/36203.shtm
9CBS - Document Center - Website Production Technology
9CBS - Document Center - Website Production Technology
Title IIS Suddenly do not parse the processing steps of the ASP file Select from the BLOG keyword IIS from Ajou Suddenly do not resolve the process of the ASP file, the original source: http://www.iisfaq.com/default.aspx? Tabid = 3094 finishing translation: Ajou1. If there is a global.asa file in the Web site directory, change this file file named global.old. Restart the web service, write the following code in Notepad (there is no code in the original text, the actual simplest ASP source code, Translator Note). Save Surfarters in Test.asp in the web root directory. If the ASP file can be executed normally, the problem is in Global.asa, if you still don't work, please go to the second step. See the following Microsoft Knowledge Base More information of the global.asa file error.
Q288245 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" to restart the Iisadmin service. If the ASP file can be implemented normally, the problem is displayed on the IWAM user, please skip to the third step. Continue. If there is no normal execution, please Check component service in the management tool to ensure that IIS Packages can be seen, make sure that the component service does not fail, confirm that the local user group has the following users:
NT Authority / Authenticated Uses NT Authority / Interactive For more information, please refer to Enrollment Article: Q301919 PRB: Cannot Expand 'My Computer' In Component Services MMC Snap-in 3. If you pass the second step ASP file Can perform normal execution, set the site's application protection level back "in" "or" high ", add the IWAM user to the local administrator user group, if this step, the ASP file can be executed normally, indicating that IWAM users' access license There is a problem with the permission, jump to the fourth step, if the ASP file is not executed properly, execute the SynciWam.vbs tool in the command prompt. Method: Open the command prompt window to knock into the following command: c: / inetpub / adminsscripts > CScript synciwam.vbs. About IWAM users (setting incorrectly) caused the ASP file to be executed normally, please refer to the encenration library .q308622 how to: Perform Administration Tasks in Iis from a commms 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 problems IWAM user permissions, use of windows 2000 Third Party Products: REGMON and FILEMON. Please download these tools in http://www.sysinternals.com. When you perform the ASP page request, run these tools, DllHost.exe process Find "Accdenied" in Regmon (in Filemonia) Find "failure"). Note: Don't be nervous when the "Operation Failed" appears in the IE process, this is just a normal phenomenon. For the minimum conditions required for IIS functionality, see Knowledge Base: Q271071 Minimum NTFS Permissions Required for II After seeing the error message of the DllHost.exe Process "Failure", use the regedit32 tool to modify any of the necessary NTFS permissions in the registration table (it seems to be a sick, sweat ...) 5. After loading IIS5 After .0, browse the ASP or HTML file from the WEB server console or other network, the web service may return to the following error message: HTTP 500 internal server error. The default web service may be in the running status, if you run netstat -an you It may be noted that the web server is listening to the TCP80 port, HTTP's default port. Note: If you use IE5.0 (or above, the translator's note), you may block the display friendly HTTP error message option in the IE advanced option, More information: Please refer to Microsoft Knowledge Base: Q218155 Description of Hypertext Transport Protocol Error Messages The following may appear in event logs with IIS5.0 machines: Application log: Com Error With Event ID 4099 System Log: W3SVC Error WITH EVENT ID 59 System Log: W3SVC WARNING WIVENT ID 36.IIS5.log file (Winnt Directory) Marsh Marshing Information: 0x8004e00F = COM WAS Unable to Talk To The Microsoft Distributed Transaction Coordinator You are trying to open COM
The component service used by the manager, the MMC stops respond. Reason IIS5.0 Dependent with COM , COM Depending on the DISTRIBUTED Transaction Coordinator (DTC) service, the DTC Check version mechanism (including SQL Server before Windows 2000) Cannot recognize Windows2000 The version attribute used, the result of SQL Server's DTC installer moves the DTC service installed by Windows 2000, more please check the Microsoft Knowledge Base: Q249310 BUG: Installing SQL Server On Windows 2000 Uninstalls DTC Service Addresses the following steps to solve this problem: a Verify DTCSetup.exe (default in C: / WinNT / System32) is 1999.9.9.3422.24 or later version number b. Run DTCSetup.exe Install DTC Service C. Start DTC Services D. Control Panel, Double-click Add Delete Program "e. Select" Add Remove Windows Components "to remove IIS5.0 and reinstall. Status Microsoft has confirmed that this will be a problem in SQL Server Versions 6.5 and 7.0 and MSDE 1.0. See article: http: // support. Microsoft.com/default.aspx?scid=kb;n-us;q257267 6. Last trick: According to the following steps you can create IIS Packagesa. Browse component service Delete the following packages A.IIS in-process Applications B.Iis Out-of -Process Pooled Applications C.IIS UtilitiesB. Open a command prompt, go to folder% windir% / system32 / inetsrv, execute command: rundll32 wamreg.dll, CreateiisPackage Note: CreateiisPackage is sensitive to case sensitive, confirmation, correct. . Re-opening the component service, you will see that IIS COM app has been recreated .d. No ASP files not executed before running Iisrestart before the command prompt.
http://blog.9cbs.net/ajou/
