IIS6.0系统日志中出现此错误Timer_MinBytesPerSecond,Timer_ConnectionIdle - 编程吧

上一篇 | 下一篇

IIS6.0系统日志中出现此错误Timer_MinBytesPerSecond,Timer_ConnectionIdle

发布: 2008-3-24 21:03 | 作者: admin | 来源: | 查看: 27次

 IIS6.0系统日志中出现此错误Timer_MinBytesPerSecond,Timer_ConnectionIdle  文章指数:0  CSDN Blog推出文章指数概念,文章指数是对Blog文章综合评分后推算出的,综合评分项分别是该文章的点击量,回复次数,被网摘收录数量,文章长度和文章类型;满分100,每月更新一次。
 Description: The Error means The connection with the server has been terminated.
问题描述:这个错误是由于服务器连接被中断导致的。

If you check out the C:\Windows\system32\LogFiles\HTTPERR\httperr*.log files on the distribution server, you'll likely see either Timer_MinBytesPerSecond errors or Timer_ConnectionIdle errors. These are caused by IIS' default settings, contained within its metabase, which define the minimum traffic flow rate for a connection to be kept alive and the maximum idle time allowed before a connection is dropped. For some reason, SUS servers seem to take their good old time while downloading updates, and these parameters are exceeded and the distribution server drops 'em.
这个问题是由于在某些应用下,IIS的默认设置不当的

1) From IIS Manager, right click on the Internet Information Server (IIS) Manager root level folder and go to Properties. Check the box to enable direct metabase editing. Click OK.
1)打开Internet 信息服务(IIS)管理器,右键点“我的计算机”——属性,选上“允许直接编辑配置数据库(N)”,确定。

2) Open the C:\Windows\system32\inetsrv\MetaBase.xml file in Notepad. Do a search for "MinFileBytesPerSec". Change the setting for MinFileBytesPerSec from 240 to 0. Do another search, this time for "ConnectionTimeout" to be 600. Save changes and exit.
2)编辑C:\Windows\system32\inetsrv\MetaBase.xml文件,把MinFileBytesPerSec 参数值从240改为0,把ConnectionTimeout参数设成600。

3) Restart the IIS Admin service to effect the changes.
3)重新起动IIS服务

Trackback: http://tb.blog.csdn.net/TrackBack.aspx?PostId=1854572

TAG: IIS错误

字号: | 推荐给好友

 

评分:0

我来说两句

seccode