Error 0x80072EFE While trying to Synchronize Child SUS Server from Parent SUS for Service Packs


In this article, I will explain about an error while trying to Synchronize Child SUS from Parent SUS Server for Service Packs.


SYMPTOMS


You get an error while trying to synchronize the Child SUS from Parent SUS Server


Error: Windows XP Service Pack 2: Failed to download from URL
‘http://Head_Office_SUSserver/content/xpSP2_f8e85320da933bb0ec76a2ba3a2f7a8.exe’.
(Error 0x80072EFE: The connection to the server was lost.)


Error:
Windows Server 2003 Service Pack 1: Failed to download from URL
‘http://Head_Office_SUSserver/content/WindowsServer2003-KB­889101-SP1-x86-ENU_6e6d2db2782­26bf7a257f86d8b5e056.exe’.
(Error 0x80072EFE: The connection to the server was lost.) –


Error:
Windows Server 2003 Service Pack 1: Failed to download from URL
‘http://Head_Office_SUSserver/content/WindowsServer2003-KB­889101-SP1-x86-ENU_6e6d2db2782­26bf7a257f86d8b5e056.exe’.
(Error 0x80072EE2: Timeout waiting for server response.) –


CAUSE


Timeout waiting for server response or the connection to the server was lost.


DESCRIPTION


The Error means the connection with the server has been terminated.


WORKAROUND:


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 them.


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.


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.


3) Restart the IIS Admin service to effect the changes. 


REFERENCES


Microsoft.Public.Softwareupdatesvcs

Leave a Reply

Your email address will not be published. Required fields are marked *