HTTP500 Errors and Solutions I. Error performance IIS5 HTTP 500 Internal server error is one of our common mistakes, its main error is that the ASP program can not browse but HTM static Web page is not affected. In addition, when errors occur, the system event log and the security event log have corresponding records.
Specifically as follows:
(i) performance in IE when browsing an ASP page that previously worked correctly, the following error occurs: The Web page cannot display a problem with the page you are visiting and cannot be displayed. Try the following: Open the http://127.0.0.1 home page and find a link to the information you want. Click the Refresh button, or try again later. HTTP 500-Internal server error Internet Information Service Technical information (support personal) Details: Microsoft Support or: 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 assistance.
(ii) Security log record (2) event Type: Failure Audit event Source: Type of Event: Logon/Logoff event id:529 Date: 2001-9-9 event: 11:17:07 User: NT Authoritysystem computer: Myser Ver Description: Logon failure: Reason: username unknown or password wrong username: iwam_myserver domain: Mydom logon Type: 4 logon Process: ADVAPI Authentication package: MICROSOFT_AUTHENTICATION_PACKAGE_V1 _0 Workstation Name: MyServer Event Type: Failure Audit event Source: Security Event Category: Account logon event id:681 Date: 2001-9-9 event: 11:17:07 User: NT Authoritysystem computer: my Server Description: Log on to account: Iwam_myserver logged in User: Microsoft_authentication_package_v1_0 from workstation: myserver unsuccessful. The error code is: 3221225578
(iii) records in the System log (2) Event Type: Error Event Source: DCOM Event Type: No event id:10004 Date: 2001-9-9 event: 11:20:26 User: N/a computer: MyServer Description: DCOM encounters an error "cannot be more The new password. The value provided to the new password contains values that are not allowed in the password. "and cannot log on to. Iwam_myserver to run server: 3d14228d-fbe1-11d0-995d-00c04fd919c1} Event Type: Warning Event Source: W3SVC Event Type: No event id:36 Date: 2001-9-9 Event: 11:20:26 User: N/a computer: MyServer Description: Server failed to transfer to application '/LM/W3SVC/4/Root '. Error is ' runas ' format must be < domain >< username > or just < username > '. To get more information about this message, please visit the Microsoft Online Support site: http://www.microsoft.com/contentredirect.asp.
Two. A comprehensive analysis of cause analysis the above error performance we can see, mainly because the IWAM account (in My computer is the Iwam_myserver account) 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.
Three. The solution knows the cause of the HTTP 500 internal error and is simpler to solve, which is the password for manually synchronizing the IWAM account in Active Directory, the IIS metabase database, and the COM + application. The specific operation in three steps, all need to log on to the computer as an administrator to provide sufficient operational rights (IWAM account to Iwam_myserver for example).
(i) Change the password for the Iwam_myserver account in Active Directory because the password of the IWAM account is controlled by the system, randomly generated, we do not know what, in order to complete the following two steps of the password synchronization work, we have to the IWAM account password set to a value we know. 1. Select Start-> program-> Administrative Tools-> Active Directory Users and Computers to start the Active Directory Users and Computers snap-in. 2, click "User", select the right "Iwam_myserver", right-click Select "Reset Password (t) ...", in the pop-up Reset Password box to iwam_myserver set a new password, here we set to "aboutnt2001" (no quotes), OK, wait for password modification to succeed.
(ii) to synchronize the password for the Iwam_myserver account in IIS metabase because of the sensitivity and importance of this change, Microsoft has not provided an explicit user interface for us to modify the Iwam_myserver account password in the IIS metabase. Only a management script adsutil.vbs is provided with IIS5, which is located under the C:inetpubadminscripts subdirectory (the location may vary depending on how you set up the IIS5). The Adsutil.vbs script is powerful, has a lot of parameters and is complex to use, and only provides a way to modify the Iwam_myserver account password using this script: adsutil set w3svc/wamuserpass password "password" parameter is the new password for the IWAM account you want to set. Therefore, we will modify the password of the Iwam_myserver account in IIS metabase to the "aboutnt2001" command: C:inetpubadminscripts>adsutil set W3svc/wamuserpass " aboutnt2001 "After successful modification, the system will have the following prompt: WAMUserPass: (String)" aboutnt2001 "
(iii) To synchronize the iwam_myserver password used by the COM + application to synchronize the iwam_myserver password for the COM + application, there are two ways to choose: one is to use the Component Services MMC snap-in, The other is to use the IWAM Account Synchronization script Synciwam.vbs. 1, use the Component Services MMC snap-in (1) to start the Component Services Snap-in: Select Start-> run-> MMC, start the management console, open the Add/Remove snap-in dialog box, add the Component Services snap-in. (2) Locate "Component Services"-> "Computer"-> "My Computer"-> "COM + application"-> "Out-of-process Pooled Applications", right-click "Out-of-process Pooled Applications the "->" attribute. (3) switch to the Flags tab of the Out-of-process Pooled Applications Properties dialog box. This application runs under the following account "This user" in the selection is selected and the username is "Iwam_myserver". These are all defaults and do not have to be changed. Enter the correct password "aboutnt2001" in the "password" and "Confirm password" text boxes below to confirm the 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? is OK. (5) If we set some other Web application protection to high (standalone) in IIS, the IWAM account password for the COM + application used by the web will also need to be synchronized. Repeat (1)-(4) step, synchronize the other corresponding out of process application IWAM account password. 2, the use of IWAM Account Synchronization script Synciwam.vbs In fact, Microsoft has found that the IWAM account in the password synchronization problem, so in the IIS5 management script for IWAM account password in a separate synchronization script Synciwam.vbs, this script is located in C: Inetpubadminscripts (location may vary depending on how you install IIS5). Synciwam.vbs script usage is simpler: The cscript Synciwam.vbs [-v|-h] "-V" parameter represents the entire process of displaying script execution in detail (recommended), and the "-H" parameter is used to display simple help information. We want to sync iwam_myserver account passwords in COM + applications, just execute "cscrIPT Synciwam.vbs-v "can be, as follows: Cscript c:inetpubadminscriptssynciwam.vbs-v Microsoft (r) Script Host version 5.6 all rights reserved (c) Microsoft Corporation 1996-2000. All rights reserved. Wamusername:iwam_myserver wamuserpass:aboutnt2001 IIS Applications Defined:name, appisolated, package ID w3svc, 0, 3d142 28C-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 Applica Tions:name:iis out-of-process Pooled Applications key:3d14228d-fbe1-11d0-995d-00c04fd919c1} from the execution of the above script, you can see that Using Synciwam.vbs scripts is more comprehensive and faster than using Component Services. It first finds the IWAM account "Iwam_myserver" from the IIS Metabase database and takes out the corresponding password "aboutnt2001" and finds all the defined IIS applications and out of process Applications and synchronizes the IWAM account password for each out of the process applications application. When using the Synciwam.vbs script, be aware that before you run Synciwam.vbs, you must ensure that the IIS metabase database is consistent with the IWAM password in Active Directory. Because Synciwam.vbs scripts are obtained from IIS metabase databases instead of from Active Directory IWAMThe password of the account, if the password in the IIS metabase is incorrect, the password that Synciwam.vbs obtains also will be incorrect, the synchronization operation executes to "updating applications" the system will report 80110414 error, namely "Cannot find the application 3D14228D-FBE1-11D0-995D-00C04FD919C1} ".