WSUS 3.0 The update Failed to download
DaveW
It is the only WSUS server and I am using the built in Windows database.
On Oct 10th my Synchronization log showed that 22 new and 3 revised updates
were successfully added to the system. However, when I look in the All
Updates area I see 9 updates with that date and only 1 of them seems to have
been successfully downloaded, the other 8 have a red X and the message The
Update Failed to Download. When I try and do a Retry Download on a few of
the files it fails and I get the following message in Event Viewer ID: 364
Content file download failed. Reason: The server does not support the
necessary HTTP protocol. Background Intelligent Transfer Service (BITS)
requires that the server support the Range protocol header.
Source File:
/msdownload/update/v3-19990518/cabpool/winword_0e0a5f988a25b3228144effb52ba19290f5d650a.cab
Destination File: s:\WSUS
Updates\WsusContent\0A\0E0A5F988A25B3228144EFFB52BA19290F5D650A.CAB.
I did some searching on this error and found some posts to do with WSUS 2.0
and they suggested a fix using an OSQL command but I have no OSQL.EXE file in
my installation and I'm using 3.0.
It seems odd that 1 out of the 9 updates got downloaded but not the other 8.
If I get 1 it seems to me that my basic communication setup must be OK.
Any help would be appreciated.
Winfried Sonntag [MVP]
> On Oct 10th my Synchronization log showed that 22 new and 3 revised updates
> were successfully added to the system. However, when I look in the All
> Updates area I see 9 updates with that date and only 1 of them seems to have
> been successfully downloaded, the other 8 have a red X and the message The
> Update Failed to Download. When I try and do a Retry Download on a few of
> the files it fails and I get the following message in Event Viewer ID: 364
>
> Content file download failed. Reason: The server does not support the
> necessary HTTP protocol. Background Intelligent Transfer Service (BITS)
> requires that the server support the Range protocol header.
> Source File:
> /msdownload/update/v3-19990518/cabpool/winword_0e0a5f988a25b3228144effb52ba19290f5d650a.cab
> Destination File: s:\WSUS
> Updates\WsusContent\0A\0E0A5F988A25B3228144EFFB52BA19290F5D650A.CAB.
Download WsusDebugTool
http://download.microsoft.com/download/7/7/4/7745a34e-f563-443b-b4f8-3a289e995255/WSUS%20Server%20Debug%20Tool.EXE
WsusDebugTool.exe /Tool:SetForegroundDownload
Restart the Server or the Services.
Winfried
--
http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx
http://www.wsuswiki.com/Home
Lawrence Garvin [MVP]
news:9A94812F-E40E-4E06...@microsoft.com...
> Content file download failed. Reason: The server does not support the
> necessary HTTP protocol. Background Intelligent Transfer Service (BITS)
> requires that the server support the Range protocol header.
The reference to "server" in this message means "firewall or proxy server",
and is almost always traceable to an issue with the installed proxy/firewall
not being properly configured to support the HTTP v1.1 protocol
specifications. Most notably this occurs on Sonicwall devices, but they're
not alone in this fault.
> I did some searching on this error and found some posts to do with WSUS
> 2.0
> and they suggested a fix using an OSQL command but I have no OSQL.EXE file
> in
> my installation and I'm using 3.0.
The OSQL.exe/WSUS2.0 command is not a fix, but merely a workaround which
avoids the unfortunate misconfiguration of the proxy/firewall.
The correct *FIX* is to reconfigure the misconfigured device.
> It seems odd that 1 out of the 9 updates got downloaded but not the other
> 8.
Has to do with filesize, and whether or not the range protocol header is
needed.
> If I get 1 it seems to me that my basic communication setup must be OK.
The *basic* setup... yes... but not the *advanced* setup. :-)
--
Lawrence Garvin, M.S., MCTS, MCP
MVP - Software Distribution (2005-2007)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin