IIS5 HTTP500 internal error solution
I. Error performance IIS5 HTTP 500 internal server error is one of the mistakes we often encounter, and its main error performance is that the ASP program cannot be browsed but the HTM static page is not affected. In addition, when the error occurs, the system event log and the security event log have corresponding records. The specific: (1) The performance in IE When browsing the ASP page that is previously operated, it will appear: The web page cannot display the problem that the webpage you want to access, so it cannot be displayed. Try the following: Open http://127.0.0.1 home page to find links to the required information. Click Refresh button, or try again later. HTTP 500 - Internal server error Internet Information Services Technical Information (support personal) details: Microsoft Support either: 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 assist.
(2) Safety log record (2) Event type: failed audit event Source: security event type: Login / Logout Event ID: 529 Date: 2001-9-9 Event: 11:17:07 User: NT Authority / System Computer : MyServer Description: Login Fail: Reason: Username Unknown or Password Error User Name: IWAM_MYSERVER Domain: Mydom Login Type: 4 Login Procedure: Advapi Authentication_Package_V1_0 Workstation Name: MyServer
Event Type: Failure Audit Source: Security Event Category: Account Log In Events: 681 Date: 2001-9-9 Event: 11:17:07 User: NT Authority / System: MyServer Description: Log in to Account: IWAM_MYSERVER Login User: Microsoft_Authentication_package_v1_0 From the workstation: MyServer is unsuccessful. Error code is: 3221225578
(3) Record in system logs (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 encountered error "Unable to update your password. Provide a value that is provided to the new password contains the value that is not allowed in the password." And you cannot log in to ./iwam_myserver to run the server to run the server: {3D1428D-FBE1-119C1}
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: The server fails to transfer to the application '/ lm / W3SVC / 4 / root '. The error is the 'RunAs' format must be
/
Or just
'.
To get more information about this message, please visit the Microsoft Online Support Site:
Http://www.microsoft.com/contentredirect.asp.
II. Cause Analysis Comprehensive Analysis The above error performance We can see that the password error of the IWAM account (in my computer is IWAM_MYSERVER account), the HTTP 500 internal error is caused.
Before detailed analysis of the reason for the internal error of the HTTP500, first make a brief introduction to the IWAM account: IWAM account is a built-in account that automatically established when installing IIS5, mainly for the Internet information service of the application outside the process. The name of the IWAM account will be different depending on each computer NetBIOS name. The general format is iWam_Machine, which is composed of the "iWam" prefix, the connection line "_" plus computer's NetBIOS name. My computer's NetBIOS name is MyServer, so my computer IWAM account is IWAM_MYSERVER, which is very similar to the naming method of IIS anonymous account isur_machine.
After IWAM account is established, it is used by the Active Directory, IIS Metabase database, and COM applications. The account password is saved separately, and the operating system is responsible for the synchronization of the IWAM password saved by these three parties. According to the constant, we are responsible for the operating system, we can rest assured that we don't have to worry about mistakes, but I don't know if it is bug or what is the reason for the system's password synchronization, the password of the IWAM account sometimes fails, so that the password used by the triplet IWAM account is not uniform. When IIS or COM application uses error IWAM's password login system, start IIS OUT-OF-Process Pooled Applications, the system will refuse this request due to password errors, resulting in the failure of IIS OUT-OF-Process Pooled Applications, that is Our "Cannot Run Server {3D14228D-FBE1-11D0-995D-00c04FD919C1}" (here {3D14228D-FBE1-119C1} is the key) of IIS Out-of-Process Pooled Applications If you cannot transfer to IIS5 applications, HTTP 500 internal errors are produced.
III. Solution
I know the reason for the internal error caused by HTTP 500, and solve it is relatively simple, that is the password in the artificial synchronization IWAM account in the Active Directory, IIS Metabase database, and COM applications. For specific operations, you need to log in to your computer as an administrator to provide sufficient operating rights (IWAM account as an example of IWAM_MYSERVER).
(1) Change the password of the iWam_myserver account in Active Directory, because the password of the IWAM account is controlled, randomly, we don't know what it is, to complete the password of the following two steps, we must set the password of the IWAM account to one We know the value. 1. Select "Start" -> Programs -> Administrative Tools -> "Active Directory User and Computers", launch the "Active Directory User and Computer" management unit. 2. Click "User", select "IWAM_MYSERVER" on the right, right-click Select "Reset Password (T) ...", set the new password for IWAM_MYSERVER in the reset password other box, which we set it into "AboutNT2001" (without quotation marks), determine, wait for the password to modify success.
(2) Synchronous IIS METABASE IWAM_MYSERVER account password may be too sensitive and important, Microsoft does not modify the IIS Metabase IWAM_MYSERVER account password to provide an explicit user interface, only with IIS5, a management script adsutil .vbs, this script is located in the C: / INETPUB / Adminscripts subdirectory (location may vary depending on the settings when you install IIS5). ADSUTIL.VBS script is powerful, the parameters are very many and the usage is complex. This only provides this script to modify the IWAM_MYSERVER account password: AdsuTil Set W3SVC / WAMUSERPASS Password "password" parameter is the new password to set the IWAM account. So we modify the password of IIS Metabase IWAM_MYSERVER account to "AboutNT2001" command is: c: / inetpub / adminsscripts> AdsuTil Set W3SVC / WAMUSERPASS "ABOUTNT2001" After the change is successful, the system will have the following tips: WamuserPass: (String) " Aboutnt2001 "(3) Synchronization COM application's IWAM_MYSERVER password synchronization COM application's IWAM_MYSERVER password, we have two ways to choose: one is to use component service MMC management unit, the other is to use IWAM account Synchronization Script Synciwam.vbs.
1. Use the component service MMC management unit (1) Start the component service management unit: Select "Start" -> "Run" -> "MMC", start the management console, open the "Add / Delete Management Unit" dialog box, will " Component Services management unit Add. (2) Find "Component Services" -> "Computer" -> "My Computer" -> "Com Applications" -> "Out-of-Process Pooled Applications", right-click "OUT-OF-Process Pooled Applications" -> "Properties". (3) Switch to the "Sign" tab of the "OUT-OF-Process Pooled Applications" Properties dialog. "This application runs under the following account" Select "This user" will be selected, the username is "iWam_MyServer". These are default, no need to change. Enter the correct password "AboutNT2001" in the "Password" and "Confirm Password" text box to determine exit. (4) System If prompted "The application is created by more than one external product. Do you have to support these products?" Is determined. (5) If we set other web "Application Protection" to "High (independent)" in IIS, the IWAM account password for the COM application used by this web also needs to be synchronized. Repeat (1) - (4) step, synchronize the other Out of Process Application IWAM account password.
2. Using the IWAM Account Synchronization Script SynciWam.vbs In fact Microsoft has found that IWAM account has problems in password synchronization, so a script synciwam.vbs is written separately for the IWAM account password in the IIS5 management script. This script is located in C: / INETPUB / ADMINSCRIPTS subdirectory (location may vary depending on the settings of setting IIS5). Synciwam.vbs Script Usage is relatively simple: CScript synciwam.vbs [-v | -h] "-v" parameter represents the entire process of detailed display scripts (recommended), "- h" parameters are used to display simple help information. We want to sync the password IWAM_MYSERVER account in the COM application, just need to perform "CScript synciwam.vbs -v", as follows: Cscript C: /inetpub/adminscripts/synciwam.vbs -v Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2000. all rights reserved.
WamUserName: IWAM_MYSERVER WamUserPass: Aboutnt2001 IIS Applications Defined: Name, AppIsolated, Package ID w3svc, 0, {3D14228C-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 Applications: Name: IIS OUT-OF-Process Pooled Applications Key: {3D14228D-FBE1-11D0-995D-00c04FD919C1}
It can be seen from the execution of the above scripts that use the SynciWam.vbs script to be more comprehensive and fast than using the components. It first finds the IIS's Metabase database to find the IWAM account "iWam_Myserver" and remove the corresponding password "ABOUTR2001", then find all the defined IIS Applications and Out of Process Applications, and synchronize each Out of Process Applications application IWAM account. password. When using the synciwam.vbs script, pay attention to a question, that is, before you run SynciWam.vbs, you must ensure that the IIS Metabase database and the iWam password in the Active Directory have been consistent. Because SynciWam.vbs scripts are passwords from the IIS Metabase database rather than get the IWAM account from Active Directory, if the password in IIS Metabase is incorrect, the password obtained by SynciWam.vbs will be incorrect, and the synchronization operation is executed to "Updating Applications" The system will report 80110414 errors, ie "not finding the application {3D14228D-FBE1-11D0-995D-00c04FD919C1}". Ok, until now, IWAM accounts are successful in Active Directory, IIS Metabase database, and COM applications, and your ASP program can run! ??
