iis| Error | Resolve |iis IIS5 HTTP500 Internal Error resolution
I. Error performance
IIS5 HTTP 500 Internal server error is one of our common errors, 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:
A The performance in IE
The following error occurs when you browse to an ASP page that previously worked correctly:
Web page cannot be displayed
The page you are trying to access has a problem and cannot be displayed.
Please try the following actions:
Open the http://127.0.0.1 home page for a link to the information you want.
Click the Refresh button, or try again later.
HTTP 500-Internal server error
Internet Information Services
Technical information (Personal support)
Detailed information:
Microsoft Support
Or is:
Server Application Error
The server has encountered an error while loading a application during the processing of your of request. Please refer to the event log for more detail information. Please contact the server Administrator for assistance.
(ii) Security log records (2 article)
Event Type: Failure audit
Event Source: Security
Event Type: Logon/Logoff
Event id:529
Date: 2001-9-9
Event: 11:17:07
User: NT Authority\System
Computer: MYSERVER
Describe:
Login failed:
Reason: Unknown user name or bad password
User name: 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 Type: Account Login
Event id:681
Date: 2001-9-9
Event: 11:17:07
User: NT Authority\System
Computer: MYSERVER
Describe:
Log on to account: Iwam_myserver
Logged in User: Microsoft_authentication_package_v1_0
From workstation: MYSERVER
did not succeed. The error code is: 3221225578
(iii) records in the System log (2 article)
Event Type: Error
Event Source: DCOM
Event Type: None
Event id:10004
Date: 2001-9-9
Event: 11:20:26
Users: N/A
Computer: MYSERVER
Describe:
DCOM encountered an error ' Unable to update password. The value provided to the new password contains values that are not allowed in the password. "and cannot log on to the. \iwam_myserver to run the server:
{3D14228D-FBE1-11D0-995D-00C04FD919C1}
Event Type: Warning
Event Source: W3SVC
Event Type: None
Event id:36
Date: 2001-9-9
Event: 11:20:26
Users: N/A
Computer: MYSERVER
Describe:
The server failed to transfer to the 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. 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.
Three. Solutions
Knowing the cause of the HTTP 500 internal error is easier to solve, which is the password for manually synchronizing IWAM accounts in active Directory, IIS metabase database, and COM + applications.
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 active Dire
[1] [2] [3] Next page
