[點(diǎn)晴永久免費(fèi)OA]IIS6.0Timer_MinBytesPerSecond，Timer_ConnectionIdle
Description: The Error means The connection with the server has been terminated.
問題描述：這個(gè)錯(cuò)誤是由于服務(wù)器連接被中斷導(dǎo)致的。 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. 這個(gè)問題是由于在某些應(yīng)用下，IIS的默認(rèn)設(shè)置不當(dāng)?shù)?BR> 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 信息服務(wù)（IIS）管理器，右鍵點(diǎn)“我的計(jì)算機(jī)”——屬性，選上“允許直接編輯配置數(shù)據(jù)庫(kù)(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 參數(shù)值從240改為0，把ConnectionTimeout參數(shù)設(shè)成600。 3) Restart the IIS Admin service to effect the changes. 3）重新起動(dòng)IIS服務(wù) 替代方法如果您安裝最新 for Windows Server 2003, ServicePack 后問題仍然存在網(wǎng)絡(luò)連接可能太慢。使用網(wǎng)絡(luò)跟蹤來確定客戶是否接收響應(yīng)和重傳數(shù)據(jù)包中延遲。 要變通解決此問題, 減少或禁用 IIS 6.0 以阻止從早關(guān)閉慢速客戶連接中 MinFileBytesPerSec 屬性。 http://support.microsoft.com/?id=820729 該文章在 2011/2/28 11:24:55 編輯過 |
關(guān)鍵字查詢
相關(guān)文章
正在查詢... 
|
400 186 1886
