After the magic winmail server is installed on the Win2000 Server System, you can send and receive emails through SMTP and POP3 protocols. After setting IIS according to winmail help, it cannot be mentioned in help, enter the email system through IE browser. For details, please refer to an even help post:
Http://bbs.ccidnet.com/showthread.php? Threadid = 140864
Preliminary handling:
Try to go to The IISHelp page and reproduce the HTTP 500 error. You cannot determine the cause of the fault. Search for related content on the Internet and find a solution article about ASP not supported by IIS;
After research and analysis, it is basically similar to determining the fault phenomenon. The Cause Analysis is: the primary cause is that the iwam_myserver password of the IWAM account is incorrect.
HTTP 500 internal error.
The solution is to unify the passwords in Active Directory, IIS metabase database, and COM + applications. Operations
This article provides a detailed introduction.
View the log file, which is not exactly the same as the phenomenon described in the article. This computer does not have domain settings.
System logs are described as follows:
Events in system logs:
Event 1:
Event Type: Error
Event Source: DCOM
Event Type: None
Event ID: 10010
Date: 2004-11-17
Event: 17:23:04
User: nt authority/System
COMPUTER: ZY-BGL-FWQ
Description:
The server {3d14228d-fbe1-11d0-995d-00c04fd919c1} was not registered with DCOM within the specified time.
------------------------
Event 2:
Event Type: Warning
Event Source: w3svc
Event Type: None
Event ID: 36
Date: 2004-11-17
Event: 17:23:04
User: N/
COMPUTER: ZY-BGL-FWQ
Description:
The server failed to transfer to the application '/lm/w3svc/1/root/iishelp '. Error: 'server failed to run
'.
To get more information about this message, visit the Microsoft online support site: http://www.microsoft.com/contentredirect.asp.
-------------------------
There are also two events in the Application Log:
Event 1:
Event Type: Error
Event Source: COM +
Event Type: Management
Event ID: 4205
Date: 2004-11-17
Event: 17:23:04
User: N/
COMPUTER: ZY-BGL-FWQ
Description:
COM + service cannot be initialized due to the following system API errors. It is usually caused by system resource storage problems on the local computer.
Cryptacquirecontext
Process name: dllhost.exe
The severity of the error has led to Process Termination.
Error code = 0x80090017: The provider type is not defined.
COM + internal service information:
File:./security. cpp, row: 617
-------------------------
Event 2:
Event Type: Error
Event Source: COM +
Event Type: SVC
Event ID: 4097
Date: 2004-11-17
Event: 17:23:04
User: N/
COMPUTER: ZY-BGL-FWQ
Description:
Inconsistency is detected in the internal status of the runtime environment. Report this error to Microsoft Product Support Service Department. * ** Error in _ file _ (926): Application image Dump failed.
There are no information logs such as "unknown user name or wrong password" described in the article;
However, the basic judgment also belongs to this type of fault.
According to the Operations written in the article, the steps are executed step by step, but the results do not work and I do not know where the problem is.
Follow the final prompt: Set "application protection" in IIS to "low", and then reset IIS. A new problem occurs again, and some asp files on the site can be displayed, however, some ASP pages cannot be displayed, while ASP chat room pages can be opened, but are displayed as "opening the database failed or wrong "; however, if "application protection" in IIS is set to "medium", no ASP page can be opened. If there is no language, it cannot be used. The last method described in this article is to reinstall IIS, the procedure is as follows: uninstall the SDK, call SP3 (I am calling SP4), and reinstall the SDK. Restart IIS and find that the fault still persists.
According to the expert's advice, this is not the root cause of the problem. After careful inquiry, we found that the Sam file was deleted (which was not noticed before) and is a database file that saves the user password, after deletion, all user information will be lost, and the corresponding group information will be lost. Although the system has logged on to the system again, the system has re-created the Sam file, IIS is also re-installed, and the IWAM account has been re-established, but the special information in the original user group has not been restored. Start from here. Check Start> Settings> Control Panel> Administrative Tools> component services, "console root directory"-> "component service"-> "computer"-> "my computer"-> "COM + application, there is an IIS Out-of-process pooled application. The ID number of this application is {timeout}. Many system errors cannot be found in applications such as {3d14228d-fbe1-11d0-995d-00 c04fd919c1, this is because the application failed to start. Open the properties of the application and check that the identity is IWAM user. Right-click to start the application and report an error. After you change it to an administrator, it can be started normally. You can also add IWAM to the local administrator group. It is determined that the IWAM user is not authorized to access the application.
The specific solution is as follows:
1. Modify the password of the iwam_myserver account. Choose Start> set> Control Panel> Administrative Tools> Computer Management, "System Tools"-> "local users and groups"-> "users", a iwam_myserver (myserver is the name of the Local Computer) account, right-click to change the password, change it to a custom password. Here we set it to "000000 ";
2. Modify the password of the IIS iwam_myserver account. In the C:/inetpub/adminscripts/directory (the default directory for IIS installation), enter: C:/inetpub/adminscripts>
Cscript adsutil. vbs set w3svc/wamuserpass "000000"
("0" indicates the User-Defined password)
After the modification is successful, the system prompts as follows:
Wamuserpass: (string )"******"
3. Synchronize the iwam_myserver password used by the COM + application. There are two methods described in the original technical article. Here I use the second method, that is, "Use the IWAM account synchronization script synciwam. vbs"
That is, in the C:/inetpub/adminscripts directory (default directory), enter:
C:/inetpub/adminscripts> cscript synciwam. vbs-V
Everything went smoothly, but in "start"> "Settings"> "Control Panel"> "Management Tools"> "component service, "console root directory"-> "component service"-> "computer"-> "my computer"-> "COM + application, right-click to start IIS Out-of-process pooled applications and find that an error is still reported. You cannot restart IIS. If the problem persists, check the third step and enter csript synciwam. after the vbs-V command, there is an error prompt in the last section of the returned script execution. An English text description cannot be saved, meaning that the original IIS database is denied access.
4. You are helpless. Deleting the IIS component package and re-establishing it will still be ineffective.
Now there is another problem. Check the application logs and system logs. If an error is found, the ID number of the event is still 10010, 36, or 4205. The previous two steps should be correct, the last step seems to be a problem. Find the relevant information based on the event ID and find the solution as follows:
Choose Start> Settings> Control Panel> Administrative Tools> Computer Management, in "System Tools"-> "local users and groups"-> "users", check that iwam_my server users are only in the guest group, in "local user and group"-> "group", right-click the Users Group attribute and add it to the nt authority/Authenticated Users and nt authority/Interactive User Members. OK.
Repeat the third step, that is, enter C:/inetpub/adminscripts> csript synciwam. vbs-V under the default IIS installation directory.
Check the returned script execution. The error in the last segment is no longer available. Change the COM + program user back to IWAM user.
, Restart IIS Out-of-Process
Pooled applications. If no error is reported, restart IIS and check all web site services!
In other words, the ASP program under IIS is restored and restarted.
So far, all faults have been eliminated!
Therefore, pay attention to the following points:
1. The space settings of Event Logs are slightly enlarged. The default value is 512 KB. Depending on the hard disk space, you can zoom in to avoid the log file being full;
2. Do not easily clear the event records in the event log. You need to find the cause for many failures;
3. Check the returned system prompts carefully;
4. Application protection in IIS should be medium or high. If it is low, all ASP pages run with local system permissions, which causes security problems.
5. Check the user permissions and startup permissions of the COM + program.
6. the default system group sometimes plays an important role and cannot be easily deleted or modified.
7. Important system documents (such as Sam) cannot be easily deleted. Proper solutions should be taken as far as possible. For example, you can use an external program to modify the registry or Sam table information to obtain administrator privileges. Do not delete the file.
Through this problem, we may find some seemingly complicated and incredible problems, as long as we use our brains, through careful viewing and analysis, go to the Internet and find some relevant articles to compare them. Instead, find the root cause of your problem and find the corresponding solution. The problem will eventually be solved.