-Internal IIS server error Solution

Recently, the machine's IIS is always abnormal. It always says that the HTTP Error cannot parse the ASP file, but it can display static html. If 'show friendly URL error' is removed, an error is returned:
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.

The online saying is that the IWAM _ computer name and password are not synchronized Between Active Directory, IIS metabase database, and COM + application.
However, when I click 'administrative tools-component services-component service', the message "COM + cannot talk to the Microsoft Distributed Transaction Coordinator," 8004e00f "is incorrect.

Check the event log and find that the MSDTC Service is abnormal.

The specific solution is as follows:

1. Delete the keys in the registry:
• HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/MSDTC
• HKEY_LOCAL_MACHINE/software/Microsoft/MSDTC
• Hkey_classes_root/CID
2. Stop MSDTC: net stop MSDTC
3. Uninstall the MSDTC Service: MSDTC-uninstall
4. reinstall the MSDTC Service: MSDTC-install
5. Start MSDTC: Net start MSDTC
6. confirm that the MSDTC Service has been started properly in the Event Viewer. [This step is critical. If not, restart the computer.]
7. Reset the iis iwam account password. [In User Management in Computer Management]
8. Synchronize the password of iwam_myserver in IIS metabase, in cmd: C:/inetput/adminscripts> adsutil set w3svc/wamuserpass Password
The "password" parameter is the new password of the IWAM account to be set.
9. Synchronize the iwam_myserver password used by the COM + application. In cmd: C:/inetput/adminscripts> cscript synciwam. vbs-V
10. Success!

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. However, the system sometimes fails to synchronize the password of the IWAM account, resulting in inconsistent passwords used by the third-party IWAM account. 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, this causes IIS Out-of-process pooled applications to fail to start, that is, the "cannot run server {3d14228d-fbe1-11d0-995d-00c04fd919c1}" we see in the id10004 error event (here {token} is the key of IIS Out-of-process pooled applications ), it cannot be transferred to the iis5 application. An internal HTTP 500 error occurs.