Workaround for 500 internal error in establishing ASP Web site in IIS under Win2003

Today, an attempt was made to create an ASP site under the Win2003 system, resulting in a "500-internal error" during the visit.

After many times on the Internet to find solutions and a lot of attempts to solve this problem finally.

IIS500 error is caused by a bug in Microsoft, mainly due to the IWAM account password error caused an internal HTTP 500 error.

In the detailed analysis of the causes of HTTP500 internal errors, the IWAM account for a brief introduction: IWAM account is installed IIS5 when the system automatically established a built-in account, mainly used to start the application outside the process 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 connection line "_", and the NetBIOS name of the computer. This is very similar to the way IIS Anonymous account iusr_machine is named.

IWAM account is established by active Directory, IIS metabase database and COM + application tripartite use, the account password is three parties respectively, and by the operating system responsible for the three-party 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 error, but do not know whether it is a bug or other reasons, the system of IWAM account password synchronization will sometimes fail, so that the three-party IWAM account password is not uniform. When IIS or COM + applications log on to the system with an incorrect IWAM password and start IIS out-of-process pooled applications, the system rejects the request because of a password error, causing IIS Out-of-process pooled Applications failed to start, which is what we saw in the ID10004 Error event "cannot run server {3d14228d-fbe1-11d0-995d-00c04fd919c1}" (Here { 3D14228D-FBE1-11D0-995D-00C04FD919C1} is a key to IIS Out-of-process pooled applications and cannot be transferred to a IIS5 application, and an HTTP 500 internal error is generated.

The workaround is in three steps: First, manually set the password for IWAM and IUSR, then synchronize the password in IIS, and finally, synchronize the password in COM +.

First, manually set the IWAM and IUSR password

Open Control Panel-Administrative Tools-Computer Management-Local Users and groups-users, change the password for the user starting with IWAM and IUSR, and set it to consistent. This is assumed to be "password".

Second, synchronize passwords in IIS

set the password using the Adsutil.vbs script provided below c:\Inetpub\AdminScripts. To use at the command line:

adsutil set W3svc/wamuserpass "Password"

cscript.exe adsutil.vbs set w3svc/anonymoususerpass "password"

Third, synchronize the password in COM +

Use the synciwam. vbs script provided below C:\Inetpub\AdminScripts. To use at the command line:

Synciwam.vbs-v

After the above three steps, and then visit the ASP website can be used normally.

This article is from the "Accplayer Small Place" blog, make sure to keep this source http://accplaystation.blog.51cto.com/9917407/1631760

Workaround for 500 internal error in establishing ASP Web site in IIS under Win2003