The description of the event ID ( 54 ) (in the resource ( HTTP )) could not find the description of the

event ID ( 54 ) (in the resource ( HTTP )) could not be found. . ..\\Device\\Http\\AppPool. The local computer may not have the necessary registration information or a message DLL file to display the message from the remote computer. You may be able to use the /AUXSOURCE= flag to retrieve word descriptions; see Help and Support for details.

Always see this in the event viewer's log:

Event Type: Warning Event Source: HTTP Event Category: None Event ID: 54 Date: 2008-7-1 Event : 10:52:59 User: N/A Computer: YONGFA365 Description: The description of the event ID ( 54 ) (in the resource ( HTTP )) could not be found. The local computer may not have the necessary registration information or message DLL files to display the message from the remote computer. You may be able to use the /AUXSOURCE= flag to retrieve word descriptions; see Help and Support for details. The following information is part of the event: \\Device\\Http\\AppPool. Data: 0000: 00 00 00 00 01 00 52 00 ......R. 0008: 00 00 00 00 36 00 04 80 ....6. .€ 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 . .......

Solution provided online: Solution:

I believe this is due to incorrectly setting up the recycling process. It is recommended to turn off the following process recycling settings: Recycling work Process (minutes): 1200 Recycled worker process (number of requests): 10000 Enable CPU monitoring, maximum CPU usage: 90% Since the process is automatically reclaimed, and every time 10,000 hits are reached, or the CPU exceeds 100%, Forcibly reclaiming the application causes the client to have a Sevice Unavailable error. (In fact, 10,000 clicks, a general traffic site, a few minutes is enough.) It is recommended to enable counter logs to monitor CPU utilization and asp.net metrics, which can help you locate every 5~10 minutes. Causes.

Also, don't open the recycling process and use the worker process pool for no reason. The general reason is usually unexplained memory leaks, thread hangs, etc.

After debugging, the above method is useless, and finally found the cause and solution: Reset C:\\Windows\\Temp file Clip permissions can be, plus everyone read and write permissions, this problem can be solved, most people want to see the immediate effect, so after the direct observation, or found that there are always related records, you can restart the server or It is not restarted when the Internet peaks, and then you will find that there are no such records. OK, the problem is solved.