IIS6.0系统日志中出现此错误Timer_MinBytesPerSecond,Timer_ConnectionIdle
2010-01-07 09:50
357 查看
问题描述:这个错误是由于服务器连接被中断导致的。
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 o 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服务
替代方法
如果您安装最新 for Windows Server 2003, ServicePack 后问题仍然存在网络连接可能太慢。
使用网络跟踪来确定客户是否接收响应和重传数据包中延迟。
要变通解决此问题, 减少或禁用 IIS 6.0 以阻止从早关闭慢速客户连接中 MinFileBytesPerSec 属性。
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 o 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服务
替代方法
如果您安装最新 for Windows Server 2003, ServicePack 后问题仍然存在网络连接可能太慢。
使用网络跟踪来确定客户是否接收响应和重传数据包中延迟。
要变通解决此问题, 减少或禁用 IIS 6.0 以阻止从早关闭慢速客户连接中 MinFileBytesPerSec 属性。
相关文章推荐
- IIS6.0系统日志中出现此错误Timer_MinBytesPerSecond,Timer_ConnectionIdle
- IIS6.0系统日志中出现此错误Timer_MinBytesPerSecond,Timer_ConnectionIdle
- IIS6.0 HttpErr 日志中出现 Timer_MinBytesPerSecond Timer_ConnectionIdle 错误
- HTTPERR的日志中出现大量Timer_MinBytesPerSecond,Timer_ConnectionIdle错误
- Timer_MinBytesPerSecond,Timer_ConnectionIdle解决办法
- 大量Timer_MinBytesPerSecond,Timer_ConnectionIdle错误
- 大量Timer_MinBytesPerSecond,Timer_ConnectionIdle错误
- IIS6.0添加上.net4.0后,以前的.net系统出现“服务器应用程序不可用”的错误提示解决办法
- 安装补丁出现0xC8000222错误和系统日志中wuaueng.dll SUS20ClientDataStore 无法读取日志文件的错误
- Asp.Net : 捕捉和记录网站中出现的所有未处理错误,抛出详细的页面来源和访问ip,调用的接口方法及异常实例(记事本日志,系统日志及数据库日志)
- was系统错误日志大量出现标识符缺失
- 安装补丁出现0xC8000222错误和系统日志中wuaueng.dll SUS20ClientDataStore: 无法读取日志文件的错误
- 系统日志里面出现:错误应用程序 mysqld-nt.exe,版本 0.0.0.0
- 日志(跟后台打印程序系统服务通讯时出现错误)解决办法
- 服务器系统日志出现“挂起模块 hungapp”错误信息处理办法
- unix等系统出现断错误(Segmentation Fault)的总结
- window live writer出现日志服务器错误
- 备份系统时候出现错误
- Ubuntu系统编译整个osdrv时出现错误
- 系统启动时出现错误:应用程序-特定 权限设置未将 COM 服务器应用程序(CLSID 为 {BA126AD1-2166-11D1-B1D0-00805FC1270E})的 本地 激活 权限授予用户 NT AUTHORITY/NETWORK SERVICE