System problem resolution record: Internal IIS 500 Error Solution

0

These two days the computer has been infected with viruses, causing headaches. Reinstall the system. One night's rising was used to kill McAfee.
Looking at the refreshing desktop, you can finally have a good sleep!
Tomorrow, we will find that IIS will not run after windows xp sp2 is installed.
According to the previous history. Almost every time I install windows 2003, windows, and windows xp IIS, I cannot go through it.
But every time google tries to solve it. It's a pity that it's not recorded yet. It's a waste of time for google to repeat it again next time. This time, you cannot be lazy.

Click record.

The solution to IIS 500 internal errors is summarized as follows:

Problem characteristics:

1. IE Local web browsing performance:
Webpage cannot be displayed
The webpage you want to access has problems, so it cannot be displayed.
HTTP 500-Internal Server Error
Internet Information Service

2. The event viewer has the following records:
The server failed to transfer to the application '/LM/W3SVC/1/ROOT/webmail '. The error is 'server failed to run [as mentioned in the document].
Or:
The server cannot load the application '/LM/W3SVC/1/root '. Error: 'No registration category [actual situation of my machine]

Analyze and solve the problem:
1,
Analysis:
There are multiple causes of an internal IIS 500 error, but the main cause 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, which is the most out-of-sync. Therefore, the key to solving the problem lies in

The password is synchronized.
Solution:
1.1) change the IWAM_MACHINE password to 123456
1.2) reset the IIS Metabase database with the new password and run:
C: \ inetpub \ AdminScripts> adsutil SET w3svc/WAMUserPass 123456
After running, the system displays:
WAMUserPass: (String) "12345678"

The password is successfully updated.
1.3) synchronize COM + account password and run
C: \ inetpub \ adminscripts \ synciwam. vbs-v
If there is no such information as error, it is generally successful.
Note that you must first start the MSDTC Service (Distributed Transaction Coordinator)

Note: After several labs, IIS does not solve the internal IIS 500 error.
Detailed: http://www.axin.net/article/ShowArticle.asp? ArticleID = 529

2,
2.1) Ensure that the MSDTC Service (Distributed Transaction Coordinator) can be started properly)
2.2) Run-> CMD-> and enter windir \ system32 \ inetsrv to run
Rundll32 wamreg. dll, CreateIISPackage
Regsvr32 asptxn. dll
2.3) restart the machine. OK pull
Details:
Http://bluethinking.cnblogs.com/archive/2006/06/14/425266.html

Note:
Because the problem cannot be repeated. I do not know whether the two processes are related. So if you have this problem.
You can consider the process described in method 2. I can't do it. Think about 1 more.