Home
.. About WSUS Wiki

RSS

WSUS
.. WSUS FAQ
.. WSUS on SBS
.. WSUS Troubleshooting
.. WSUS News Groups
.. Known WSUS Issues
.. WSUS Links
.. WSUS Wish List

WSUS Documents
.. WSUS Deployment Guide
.. WSUS Installation Guide
.. WSUS Release Notes
.. WSUS Best Practice

SUS
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues

Wiki Community
.. Wiki Contributors
.. I Love WSUS
.. WSUS Wiki Diary
.. Wiki Statistics
.. To Do Page

Miscellaneous Stuff
.. Other Resources
.. Do You Know?

Site Meter


Terms of Use
Trademarks
Privacy Statement

 

Content File Download Failed: The server does not support the necessary HTTP protocol


SYMPTOMS

During the Synchronization you see the following Messages in the Event log:

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/windowsxp-kb329441-x86-deu_add906039f76792094f57cc70f55397.exe

Destination File:
D:\WSUS\WsusContent\02\894D6674015D614B6933A109FB3BA02D7466D202.exe.

CAUSE

This is most likely a problem with a proxy server or firewall that you have. BITS downloads use HTTP 1.1 range requests commonly while running in the background download mode. If you have a proxy or firewall that either block these requests or does not fully support them, you might run into this issue.

WORKAROUND

Try these steps as a workaround on the WSUS server, if you unable resolve
this issue from the proxy/firewall side.

1. net stop WSusService

2. CD "%programfiles%\Update Services\tools\osql\osql.exe" -S <SQL instance name -E -b -n -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1"

3. net start WSusService

[Replace <SQL instance name with your SQL server or %computername%\WSUS if you are using WMSDE]


Comments:

From Gund - 9/18/07 4:33 PM

Seems everybody is battling with this and me too. After today, here is how to do this if you opted for SQL2005 Express instead of the default horrible little Windows DB.

The Windows DB is very memory and processor intensive with no control, so I installed SQL 2005 Express, the details are on another  page here. Also, be sure to have installed Native Client Option when installing 2005Express(Actually you are guessing by now correctly that I know nothing of SQL).

 SQLCMD.exe -S <Server>\SQLEXPRESS -E -b -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1"

 Worked for me, thanks heaps.

 

From pavloh - 8/20/07 10:26 PM

I do not have this directory tools\osql\. there is no folders within my tools directory?

 

also searched for this osql.exe and nothing came up??

From kansascity1 - 8/16/07 8:21 AM

Script worked perfect.  Been beating my head against the wall over this one for quite a while.  Thanks!

From dcouturier - 8/8/07 10:43 AM

Une autre commande SQLCMD.exe -S \\.\pipe\mssql$microsoft##ssee\sql\query -E -b -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1"

Another command SQLCMD.exe -S \\.\pipe\mssql$microsoft##ssee\sql\query -E -b -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1"

From dcouturier - 8/3/07 6:19 AM

Voici la commande pour contourner cette erreur avec WSUS 3.0 et SQL 2005 Express :

 SQLCMD.exe -S <Server>\Microsoft##SSEE -E -b -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1"

Pour utiliser l'utilitaire SQLCMD.exe, il faut télécharger le NativeClient (sqlncli.msi) et sqlcmd (SQLServer2005_SQLCMD.msi)

 English version

For troubleshoot this error :

SQLCMD.exe -S <Server>\Microsoft##SSEE -E -b -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1"

For use SQLCMD.exe, you must download and install those files : NativeClient (sqlncli.msi) and sqlcmd (SQLServer2005_SQLCMD.msi)

From ewall - 7/16/07 3:15 PM

Wkelley79-- In SQL Server 2005 Express Edition, OSQL has been replaced by SQLCMD. The syntax is nearly always the same as the old OSQL options; see http://msdn2.microsoft.com/en-us/library/ms180944.aspx if you need more help with it.

From Wkelley79 - 7/3/07 12:53 PM

HELP!!!!! I tried to use this work around for WSUS3.0 but it does not have the OSQL Tool. We cannot locate a BITS Version for 2003 X64. Should the standard x86 version run on the x64 OS? We have tried to install this but we receive an error not supported on this hardware! Could these be due to using Network Card Teams ???? please help its doing my brain in now!

From ewall - 2/26/07 10:19 AM

Thanks, Dan--very useful tip for the SonicWALL firewalls!

However, I should mention that the option to "Enable HTTP Byte-Range requests with Gateway AV" has moved into the regular SonicWALL web interface now. Login and browse to the Security Services tab, Gateway Anti-Virus option, then look for the button labeled "Configure Gateway AV Settings". That will open up a new window/dialog which contains a checkbox option we're looking for: "Enable HTTP Byte-Range requests with Gateway AV".

~ewall

From ComputerX - 2/7/06 4:39 PM

For WSUS to work through a SonicWall with a Gateway antivirus you need to enable HTTP Byte-Range requests.  If you are running the content filter you will probably need to add some sites to the exclusion list.

To enable HTTP Byte-Range requests connect to the internal settings page of your firewall.  There are no links to this page.  You will have to enter the address by hand.

When you connect to your firewall you will have an address like http://10.1.1.1/main.html

Change the adderss to http://10.1.1.1/diag.html to access the hidden page.  Click on "Internal Settings"

Check the box next to "Enable HTTP Byte-Range requests with Gateway AV" about two thirds of the way down.

Click "Apply" in the upper right of the screen.

Click "Close" in the bottom left of the screen.


If you are running the content filter you will have to create exceptions for Microsoft's distribution sites.

I have *.microsoft.com in both my "Trusted Domains" and in my "Allowed Domains" and it works.  The following is verbatim from SonicWall tech support.

enter the following URL's in the Allowed domains http://windowsupdate.microsoft.com http://*.windowsupdate.microsoft.com https://*.windowsupdate.microsoft.com http://*.update.microsoft.com https://*.update.microsoft.com http://*.windowsupdate.com http://download.windowsupdate.com http://download.microsoft.com http://*.download.windowsupdate.com http://wustat.windows.com http://ntservicepack.microsoft.com

Good luck,

 

Dan 

From CharlesR - 2/2/06 1:51 PM

The workaround worked great for me with that script. Thanks.

From Rolphus - 12/22/05 10:43 AM

An additional issue with this is that some gateway-level anti-virus systems (such as those produced by SonicWALL) block the HTTP RANGE request for reasons of security - if you're comfortable disabling this option (which is hidden on the SonicWALL), you can get around it that way.



Last Modified 9/6/05 2:38 PM

Hide Tools