Source: Haiti information
Features: The normal CPU consumption of the server should be below 75%, and the CPU consumption should be fluctuating. If such a problem occurs on the server, the CPU will suddenly remain at a level of 100% and will not decrease. View the task manager and you can find it is DLLHOST. EXE consumes all the CPU idle time. In this case, the Administrator has to restart the IIS service. The strange thing is that after the IIS service is restarted, everything works normally, however, after a while, the problem may occur again.
Cause:
One or more ACCESS databases are damaged during multiple read/write operations. When Microsoft's MDAC system writes this corrupt ACCESS file, the ASP thread is in the BLOCK state, and other threads can only wait, IIS is deadlocked, and all CPU time is consumed in DLLHOST.
Solution:
Install the "first-class information monitoring and interception system", and use the "Chief file examiner IIS health examiner" software,
Enable "find deadlock module" and set:
; -- Wblock = yes
; Monitoring directory, please specify the directory where your host files are located:
; -- Wblockdir = d: est
The log files generated by monitoring are stored in the log directory of the installation directory. The file name is logblock.htm.
Stop IIS, start "chief file examiner IIS health examiner", and then start IIS. "chief file examiner IIS health examiner" records the last ACCESS file written in logblock.htm.
After the timer time, when the question arises, for example, the CPU will go directly to the 100th level, you can stop iisand check the last 10 files recorded by logblock.htm. Note that the most problematic is the ACCESS file of the counter class, for example: "** COUNT. MDB "," ** COUNT. ASP ", you can first Delete the last 10 files or suspected files to the recycle bin, and then start IIS to see if the problem occurs again. We believe that, after careful searching, you will certainly find this one that makes you worry about for a while.