IIS5 HTTP500 Internal Error resolution (transferred from Enet)------(ii)

Iis| Error | Resolution two. Causal analysis

Comprehensive analysis of the above error performance we can see, mainly because the IWAM account (in My computer is the Iwam_myserver account) of the password error caused an HTTP 500 internal error.


In the detailed analysis of the causes of HTTP500 internal errors, first of IWAM account for a brief introduction: IWAM account is installed IIS5 when the system automatically set up a built-in account, mainly for the start of the process outside the application of Internet Information Services. The name of the IWAM account differs depending on the NetBIOS name of each computer, and the common format is iwam_machine, which consists of the "IWAM" prefix, the connector "_" plus the NetBIOS name of the computer. My computer's NetBIOS name is MYSERVER, so the name of the IWAM account on my computer is Iwam_myserver, which is very similar to the way IIS Anonymous account Isur_machine is named.


IWAM account is established by active Directory, IIS metabase database and COM + application tripartite use, the account password is saved by three parties, and the operating system is responsible for the three-party saved IWAM Password synchronization work. According to common sense, the operating system is responsible for the work we can rest assured that there is no need to worry about mistakes, but I do not know is a bug or other reasons, the system of the IWAM account password synchronization work will sometimes fail, so that the three-party IWAM account password is not uniform. When IIS or COM + applications log on to the system using the wrong IWAM password, the system rejects the request because of a password error when the IIS Out-of-process pooled applications is started, causing IIS out-of-process pooled Applications failed to start, which is what we see in the ID10004 Error event "cannot run server {3d14228d-fbe1-11d0-995d-00c04fd919c1}" (Here { 3D14228D-FBE1-11D0-995D-00C04FD919C1} is an IIS Out-of-process pooled applications key) and cannot be transferred to the IIS5 application, and HTTP 500 internal errors are generated.