Httperr a solution that takes up a lot of system space _win server

There are a lot of small files under the C:\WIN2003\system32\LogFiles\HTTPERR folder, one that happens to be 1024KB file name is httperr****.log in this format.

In IIS 6.0, the logging functionality has been changed to http.sys implementation, and HTTP.sys is running in kernel mode. This improvement accelerates log write speed while avoiding multiple worker processes competing for the same log file. In some special cases, HTTP.sys encounters an error, and it should but cannot write log information to the Web site's log, for example, the worker process is being reclaimed, the HTTP.sys is prevented from processing the user's request, or the user is trying to connect to the server, but only part of the information required for IIS is provided in the If such a situation occurs, HTTP.sys writes the event to a new log file Httperr.log.

Httperr.log log files are important in troubleshooting and optimizing IIS 6.0. By default, the Httperr.log file is saved in the \System32\LogFiles directory. The information that can be found in the Httperr.log log file includes all 503 (Service Unavailable) errors, idle connection timeout, various errors that occur when parsing URLs, and the last 10 requests submitted to the failed application pool.

IIS 6.0 also has a feature called binary logging that, when enabled, IIS 6.0 writes all the log information for a Web site to a binary-formatted log file with the name extension. ibl. To enable binary logging, simply set the w3svcc/centralbinaryloggingenabled entry of the configuration file to Ture (1). This feature should be useful for ISPs. There may be 1000 or more Web sites on each ISP's machine, and if each Web site generates a log file every day, the total number of log files will soon reach an astronomical figure. Microsoft's recently released Log Parser 2.0 tool is able to read binary log files and generate reports that can be made from http://download.microsoft.com/download/iis50/utility/2.0/nt5xp/ En-us/setup.exe download. Log Parser 2.0 can also read the Httperr.log file described earlier and generate a report.

Solution

If you check the C:\windows\system32\logfiles\httperr\httperr*.log file on the parent SUS server, you will likely see Timer_minbytespersecond errors or Timer_ Connectionidle error. These are set by the IIS defaults, within their metabase, which are defined to allow connection interrupts prior to keeping the active small traffic flow rate and maximum idle time.

1 Right-click the Internet Information Server (IIS) Manager level root directory from IIS Manager and go to the property. Select to enable the direct Edit metabase box. Click OK.
Open C:\Windows\system32\inetsrv\MetaBase.xml file 2 in Notepad. To search for "minfilebytespersec." Change the MinFileBytesPerSec setting from 240 to 0. Perform other searches, which will be "ConnectionTimeout". Save the changes and exit.
3 Restart the IISAdmin service for changes to take effect.

First, turn off the IIS Httprerr log feature

By default, the 2003 server writes all IIS access error records to the log file under C:\WINDOWS\system32\LogFiles\HTTPERR, and if the traffic is large, the log file may be full of C disk space for a period of time. Causing the server to panic

At the same time, because to write all IIS access records, if a large number of visits will greatly increase the server CPU utilization

Ways to turn off Httperr

Run input regedit enter Registry Editor
[Hkey_local_machine\system\currentcontrolset\services\http\parameters]

right mouse button to create new DWORD value enableerrorlogging reboot the server

"Enableerrorlogging" =dword:00000000

After the restart, 2003 no longer write to the Httperr log file, you can see the server CPU footprint significantly reduced!

Second, modify the storage directory is also a good way

Find:
Hkey_local_machine\system\currentcontrolset\services\http\parameters
Create a string value below. That's REG_SZ.
The numeric name is named: errorloggingdir
Numeric data for the path you specify, such as D:\logofilse