IIS problem, HTTP 500 Error Solution

IIS problem, HTTP 500 Error solution! I searched the internet and found that there is another directory for the user IUSR_QIUYISTUDIO to have the write permission, namely % SystemRoot % \ Temp (C: \ Windows \ Temp when the system is installed by default) directory, my days, ASP. NET permission is also required to grant this temporary directory permission, and now ASP is also. Solve the problem !!   Recently, I wanted to build my own website. When I installed IIS on my machine, I found that I could not browse ASP pages. The static pages of HTM and HTML are okay. Baidu has more than N, fenyun is also widely spoken on the Internet. Maybe they have different problems and different solutions. Now I want to list some common IIS errors and brainstorm. I hope that my friends who have encountered similar problems can take less detours, IIS http 500 errors can be seen in the following situations (of course, the premise is to remove the check box before "internet Options-> advanced-> show friendly HTTP Error information, otherwise, the system prompts an HTTP500 error and does not see any other details ):   First case: Active Server Pages error "ASP 0201" Invalid default scripting language The default scripting language specified for this application is invalid. Case 2: -2147467259 (0x80004005) Case 3: Server Application Error The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for maintenance.   HTTP500 internal server error solution (this is my personal solution, the system is winxp sp2 ): 1. Delete "internet Information Service (IIS )", 2. Restart the host and press F8 to enter "safe mode ", 3. In safe mode, delete "C: \ Inetpub", "c: \ windows \ iis6.log", and "c: \ windows \ system32 \ inetsrv. 4. Restart the host and install "internet Information Service (IIS)" in normal mode )". 5. check whether there are msdtc errors in the Event Viewer. If yes, run msdtc-uninstall to uninstall, run msdtc-install to install, and run net start msdtc to run the msdtc Service, in the event viewer, we can see that the msdtc Service has started properly. 6. Enable "internet Information Service (IIS)" and "restart IIS ". 7. After the installation, you may see that the application LM/W3SVC/1/ROOT cannot be loaded on similar servers. The error is "no registered category", which is often seen in the event viewer. Cd % windir % \ system32 \ inetsrv Rundll32 wamreg. dll, CreateIISPackage Regsvr32 asptxn. dll After restarting the machine, my problem can be solved perfectly in this step! In this case, I have been using GHOST for more than N times, and baidu has more than N materials to solve the problem.         If the problem persists, continue: Run cmd, and then Regsvr32/u scrrun. dll Regsvr32 scrrun. dll Regsvr32 vbscript. dll (Note: This command fixes Dynamic Link Libraries related to java scripts) Regsvr32 jscript. dll (Note: This command fixes the dynamic link library related to the vb script) Regsvr32 % windir % \ system32 \ inetsvr \ asp. dll Go to iis -- default website -- home directory -- Application protection -- select low (iis Process) to view dynamic web pages. Restart IIS and solve the error.         Another possibility is to install  security guard. Recently, it has been tested that some rogue software will maliciously damage the system after installing security guard on the machine. Now, releases the Repair Tool. Please use the fixer Repair Tool to fix it. Post on Safe (download fixer from the following website) Http://bbs.safe.com/viewthread.php? Tid = 31134 Http://bbs.safe.com/viewthread.php? Tid = 39252 There are many other types of data circulating on the Internet, many of which have not been met yet. Unconfirmed ones are listed below. If you are interested, you can try them: Click Start, point to program, point to administrative tools, and then click Internet Information Service. In the console tree, click the default Web site. In the display pane, right-click the default Web site and click Properties. In the anonymous access and authentication control on the Directory Security tab, click Edit. On the authentication method attributes page, click Remove anonymous access. An error occurs on the internal server of HTTP500. if the error is caused by COM +, a solution is provided. The com + problem should be displayed in the event viewer. The following describes how to reinstall COM +: This is the original text (English ): How do I clean up a damaged COM + catalog in Windows 2000? To clean up a damaged COM + catalog: 01. Rename % SystemRoot % \ System32 \ Clbcatq. dll to % SystemRoot % \ System32 \~ Clbcatq. dll, making sure that you include the tilde (~). 02. Shutdown and restart your computer. 03. Delete the COM3 sub-key from the registry at HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft. 04. Open a CMD. EXE prompt. 05. Type pushd % SystemRoot % and press Enter. 06. Type rd/s/q Registration and press Enter. 07. Type popd and press Enter. 08. Type exit and press Enter. 09. Use Notepad to remove Hide from the COM = line in % SystemRoot % \ Inf \ Sysoc. inf. 10. For Windows XP: A. Open a CMD. EXE window B. Type the following commands, pressing ENTER after each line: Regsvr32/s ole32.dll Regsvr32/s oleaut32.dll 11. Start/Settings/Control Panel/Add/Remove Programs/Add/Remove Windows Components. 12. Press Next and reinstall COM +. NOTE: If Windows File Protection blocks any of the above renaming and/or Deletions, perform those steps in Safe Mode. Chinese technical documents: Repair damaged COM + directory The COM + directory contains all the COM + applications, classes, and attributes in the specified system. The purpose of keeping this directory in the Windows operating system is to ensure the link between different COM + attributes and display it in different programming interfaces. If the directory is corrupted, the program running on COM + will not run normally (or cannot run at all !). One example of a Service that relies on COM + is the Volume Shadow Copy Service used in Microsoft's NTBACKUP application ), of course, this service is also used in other programs. With shadow replication, NTBACKUP can replicate system files or other locked files. However, if NTBACKUP fails due to an error in the COM + service of shadow replication, it is very likely that the directory is damaged and needs to be repaired. (Another feature of COM + directory corruption is that many programs are suspended for several minutes consecutively, but this is only a small part and is not well described .) To repair the damaged COM + directory, follow these steps: 1. Find the "\ % WinDir % \ System32 \ Clbcatq. dll" file and rename it as "~ Clbcatq. dll (note the symbol "~"). "% Windir %" is an environment variable, which can be translated into "C: \ Windows ". 2. restart the computer in safe mode. 3. Open the registry and delete the following key value: HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ COM3 4. In the \ % WinDir % directory, find the subdirectory "Registration. Delete this directory, including all the files contained in it. 5. restart the computer normally. 6. In command line mode, type "regsvr32 \ % windir % \ system32 \ ole32.dll", and click "OK" on the receiving prompt ". 7. Open "Control Panel", select "add or delete programs", and then select "Add/delete Windows Components. 8. Click "Next" to reinstall COM +. In fact, you do not need to choose to add or delete any components. COM + will be automatically reinstalled as usual. After this step, you do not need to restart the computer; the re-registered COM + service will take effect immediately       There are also two ways to solve IIS errors (these two solutions are complicated, and I have tried many times but fail): Control Scripts ------------------------------------------------------------------------ IIS5 HTTP500 internal error Cause Analysis and Solution-control ------------------------------------------------------------------------ IIS5's http 500 internal server error is one of the common errors. Its main error is that asp programs cannot browse but html static webpages are not affected. I. error message There will always be three manifestations when this error occurs: first, the most direct and incomprehensible performance in IE; second, the performance in security logs, IWAM_Machine Account Logon failure; the third is the performance in system logs. the IIS Out-Of-Process Pooled Applications cannot be started due to startup account errors. this leads to an ASP page browsing error. here we will only briefly introduce the performance of IE. The following error occurs when you browse asp pages that previously run normally: Webpage cannot be displayed The webpage you want to access has problems, so it cannot be displayed. --------------------------------------------- Please try the following operations: Go to the http: // 127.0.0.1/homepage and find a link to the desired information. Click Refresh or try again later. HTTP 500-Internal Server Error Internet Information Service   Server Application Error The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for maintenance. ---------------------------------------------------------------- (Skipped) Before analyzing the cause of an internal error in HTTP500 in detail, let's give a brief introduction to the IWAM account: the IWAM account is a built-in account automatically created by the system when IIS5 is installed, it is mainly used to start Internet Information Services for applications outside the process. The name of the IWAM account varies depending on the NETBIOS name of each computer. The common format is IWAM_MACHINE, it is composed of the prefix "IWAM", the connection line "_", and the computer's NETBIOS name. My computer's NETBIOS name is 2000. Therefore, the IWAM account name on my computer is IWAM_2000, which is similar to the name of the IIS Anonymous Account ISUR_MACHINE. After the IWAM account is created, it is used by the Active Directory, IIS metabase database, and COM + applications. The account and password are respectively saved by the three parties, the operating system is responsible for synchronizing the IWAM password stored by the three parties. We can rest assured that the work undertaken by the operating system does not have to worry about errors, but we do not know whether it is a BUG or another reason. The system sometimes fails to synchronize the password of the IWAM account, the password used by the third-party IWAM account is inconsistent. When IIS or COM + Applications use the wrong IWAM password to log on to the system and start IIS Out-Of-Process Pooled Applications, the system rejects this request due to a wrong password, as a result, IIS Out-Of-Process Pooled Applications cannot be started and cannot be transferred to IIS5 Applications. An internal HTTP 500 error occurs. -------------------------------------------------------------------- There are multiple reasons for internal IIS 500 errors, but the main reason is that the IWAM_MACHINE account is in Active Directory (or SAM ), the metabase database in IIS does not match the password in the COM + component. the key to solving the problem is to synchronize the passwords of the three parties. -------------------------------------------------------------------- Specific operations: You must log on to your computer as an administrator in three steps to provide sufficient operation permissions. 1. Change the password of the IWAM_MACHINE account in the Local Account Manager (that is, start the IIS process account) 2. Use the new password to reset the IIS Metabase database (that is, edit the user account used for anonymous access) 3. Synchronize the COM + application account and password (1) change the password of the IWAM_MACHINE account 1. Choose Start> program> Administrative Tools> Computer Management> local users and groups> user to select right-click IWAM_MACHINE and choose "set password". Here we set it to test. -------------------------------------------------------------------- (2) use the new password to reset the IIS Metabase database (that is, edit the user account used for anonymous access) Choose "Default Web site properties"-> directory security tag-> edit "Anonymous Access and verification control"-> select Anonymous access in the pop-up box, click Edit button-> User Name browsing, select IWAM_MACHINE, enter test in the password box, and select "allow IIS to control password"-> OK. If the dialog box is displayed, "non-local user accounts do not support password synchronization. Are you sure you want to continue? "OK. Are you sure you want to close all the dialog boxes. -------------------------------------------------------------------- (3) synchronize the IWAM_MACHINE password used by the com + application Use the component service mmc snap-in (1) Start the Component Service Management Unit: Choose Start> RUN> mmc to start the management console and open the Add/delete Management Unit dialog box, add the Component Service Management Unit. (2) choose component service> Computer> my computer> com + application> out-of-process pooled applications ", right-click "out-of-process pooled applications"-> "properties ". (3) switch to the "identifier" tab in the "out-of-process pooled applications" attribute dialog box. Select "this user", browse, and select the user name "IWAM_MACHINE ". These are all default values. Enter the correct password "test" in the "password" and "Confirm Password" text boxes below to exit. (4) If the system prompts "the application is created by more than one external product. Are you sure you want to be supported by these products ?" . (5) If we set "application protection" for some other web pages in iis to "high (independent )", the iwam account and password of the com + application used by the web must also be synchronized. Bytes -------------------------------------------------------------------------------------------------------- Now, the password of the IWAM account in Active Directory, IIS metabase database, and COM + application has been synchronized successfully, and your ASP program can run again! --------------------------------------------------------- IIS5 HTTP500 internal error Cause Analysis and Solution-script --------------------------------------------------------- There are multiple reasons for internal IIS 500 errors, but the main reason is that the IWAM_MACHINE account is in Active Directory (or SAM ), the metabase database in IIS does not match the password in the COM + component. the key to solving the problem is to synchronize the passwords of the three parties. Bytes ----------------------------------------------------------------------------------------------------- Specific operations: You must log on to your computer as an administrator to provide sufficient operation permissions. 1. Change the password of the IWAM_MACHINE account in the Local Account Manager (that is, start the IIS process account) 2. Use the new password to reset the IIS Metabase database (that is, edit the user account used for anonymous access) 3. Synchronize the COM + application account and password (1) change the password of the IWAM_MACHINE account 1. Choose Start> program> Administrative Tools> Computer Management> local users and groups> user to select right-click IWAM_MACHINE and choose "set password". Here we set it to test. Bytes ----------------------------------------------------------------------------------------------------- (2) use the new password to reset the IIS Metabase database. Run the following command: C: \ Inetpub \ AdminScripts> adsutil SET w3svc/WAMUserPass test The system displays: WAMUserPass: (String )"******" The password is successfully updated. Bytes ----------------------------------------------------------------------------------------------------- (3) synchronize the IWAM_MACHINE password used by the com + application We need to use the IIS management script synciwam. vbs, this script usually exists in c: \ inetpub \ adminscripts, and the previous management script is also placed here. (The location may vary depending on the settings you set when installing iis5 ). The command is as follows: Cscript c: \ inetpub \ adminscripts \ synciwam. vbs-v The-v parameter is used to enable the verbose mode. The update process is usually shown as follows: Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2000. All rights reserved. WamUserName: IWAM_xxxxx WamUserPass: test IIS Applications Defined: Name, AppIsolated, Package ID W3svc, 0, {3D14228C-FBE1-11d0-995D-00C04FD919C1} Root, 2, IISHelp, 2, IISAdmin, 2, IISSamples, 2, MSADC, 2, ROOT, 2, IISAdmin, 2, IISHelp, 2, Root, 2, Root, 2, Out of process applications defined: Count: 1 {3D14228D-FBE1-11d0-995D-00C04FD919C1} Updating Applications: Name: IIS Out-Of-Process Pooled Applications Key: {3D14228D-FBE1-11D0- 995D-00C04FD919C1} The password is synchronized successfully. If the password for IIS obtained by this script is incorrect, repeat Step 2 to synchronize the IIS Password. Now, the password of the IWAM account in Active Directory, IIS metabase database, and COM + application has been synchronized successfully, and your ASP program can run again! Quick response solution:-Quick Response Use the component service mmc snap-in 1. start the Component Service Management Unit: Choose Start> RUN> mmc to start the management console and open the "console"> "Add/delete Management Unit" dialog box, add the Component Service Management Unit. 2. find "component service"> "computer"> "my computer"> "com + application"> "out-of-process pooled applications ", right-click "out-of-process pooled applications"-> "properties ". 3. Switch to the "ID" tab. Select "Interactive User-currently logged on user" and confirm to exit. 4. If the system prompts "the application is created by more than one external product. Are you sure you want to be supported by these products ?" OK. Now try ASP. The COM + application cannot be opened. My computer still has a red icon, which is not available in the past .... See in Event Viewer "Application-the COM server application (CLSID is {A7CC2FDB-EED7-4FDA-880E-C762570CC005} ) To grant the user MICROSOF-C0F0E9 \ ghdo SID (S-1-5-21-1004336348-796845957-725345543-1004 ). You can use the component service management tool to modify this security permission. " "Error Code 8004E00F-COM + cannot be used with Microsoft Distributed Transaction Coordination Program" Solution: Run msdtc-resetlog Run mmc to open the iis Console ========================================================== ====================================== ========================================================== ====================================== Problems solved by scripting: 8004E00F 1. Reset the iis iwam account password. [In User Management in Computer Management] 2. Synchronize the password of IWAM_MYSERVER in IIS metabase, in CMD: c: \ inetput \ adminscripts> adsutil set w3svc/wamuserpass "yourpassword" 3. Synchronize the IWAM_MYSERVER password used by the COM + application, in CMD: c: \ inetput \ adminscripts> cscript synciwam. vbs-v, but the error is always reported during step 3. Later, the MSDTC Service was abnormal, so I started from here. The specific solution is as follows: 1. First, go to the component service and check the component service/computer/my computer/COM + application. The error "COM + cannot talk to Microsoft Distributed Transaction Coordination Program" is returned ", you cannot view the objects in it. 2. Go to the Event Viewer and find that the msdtc Service is not started properly. 3. Delete the keys in the registry: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ MSDTC HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSDTC HKEY_CLASSES_ROOT \ CID 4. stop MSDTC: net stop msdtc 5. uninstall the MSDTC Service: msdtc-uninstall 6. reinstall the MSDTC Service: msdtc-install 7. confirm that the msdtc Service has been started properly in the Event Viewer. [This step is critical. If not, restart the computer and check the password again (that is, the start step) In fact, there are no errors in these methods on the Internet, but there is a premise that all the necessary components of IIS are installed! In fact, after "COM + cannot talk to Microsoft Distributed Transaction Coordinator ()" is installed in the message queue of Windows Components, this error will not occur, at the same time, the "message queue" component is dependent on the "Distributed Transaction Coordinator" (msdtc Service) in the service. This service must be enabled before the Message Queue component can be installed! After the message queue is installed, the COM + application menu in can be opened, indicating that it is working properly! If you reinstall IIS or uninstall IIS at this time, you do not need the above manual password synchronization problem! That is to say, it is normal to install IIS by following this step! In fact, manual password synchronization is too troublesome and the success rate is not high! I tried it many times but failed. You can try it on your own! 2. Microsoft's article on how ms dtc cannot be installed: How to reinstall Microsoft Distributed Transaction Processing Coordinator on a computer running Windows XP Http://support.microsoft.com/default.aspx? Scid = kb % 3Bzh-cn % 3B891801 ====================================== Extract the steps here: This article describes how to reinstall Microsoft Distributed Transaction Coordinator (ms dtc) on a computer running Microsoft Windows XP ). More information Generally, you do not have to reinstall Microsoft Distributed Transaction Processing Coordinator (Msdtc.exe) on a computer running Windows XP or later ). If you use an earlier operating system, you may have to reinstall ms dtc after installing software such as Microsoft SQL Server 6.5, because the software overwrites the MS DTC binary file with the version it contains. Reinstall the correct version of Msdtc.exe to restore the binary file. In Windows XP and later versions, the Windows File Protection (WFP) feature ensures that the binary files of the current system are not replaced. However, if you must reinstall ms dtc on a computer that is running Windows XP, use the following procedure. Warning if you use the following steps, all unfinished transactions will be lost. Make sure there are no active transactions before performing the following steps. Warning improper use of the Registry Editor can cause serious problems and the operating system may need to be re-installed. Microsoft cannot guarantee that you can solve problems caused by improper use of the Registry Editor. You are at your own risk to use the Registry Editor. 1. Open "service" in "Administrative Tools" and stop all services. 2. In the "Start type" column, change the start type of all other services to "Manual" except the services listed in the following table ". Note: We recommend that you write down the changed services so that these values can be restored correctly in Step 7. COM + Event System Computer Browser Distributed Link Tracking Client DNS Client Event Log IPSEC Services Logical Disk Manager Messenger Net Logon Nt lm Security Support Provider Network Connections Plug and Play Remote Procedure Call (RPC) Remote Procedure Call (RPC) Locator Removable Storage Security Accounts Manager Server System Event Notification Task Scheduler TCP/IP NetBIOS Helper Windows Management Instrumentation Windows Management Instrumentation Driver Extensions Windows Time Workstation 3. Disable the "service" and restart the computer. 4. At the command prompt, type the following command: % WINDIR % \ System32 \ msdtc.exe-uninstall 5. Start Registry Editor. If the following registry key exists, delete it: HKEY_CLASSES_ROOT \ CID HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ MSDTC HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ Services \ MSDTC HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet002 \ Services \ MSDTC HKEY_LOCAL_MACHINE \ Software \ Microsoft \ MSDTC 6. at the command prompt, type % WINDIR % \ System32 \ msdtc.exe-install. 7. Wait for the disk activity to stop, and then restore the Startup Type of the changed service to its original value. 8. In the registry, create the following registry key: HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSDTC \ XADLL 9. At the command prompt, type regsvr32 mtxoci. dll. You will receive a message indicating that the DllRegisterServer in Mtxoci. dll has been successful. Click OK to close the message. 10. restart the computer. 11. at the command prompt, type % WINDIR % \ System32 \ msdtc.exe-resetlog. ========================================================== ========================================================== ======== Ms dtc has been installed and re-runs msdtc-resetlog.