locked
WSUS EVENT ID: 364 RRS feed

  • Question

  • Event Type: Error
    Event Source: Windows Server Update Services
    Event Category: Synchronization
    Event ID: 364
    Date:  11/20/2009
    Time:  2:28:49 PM
    User:  N/A
    Computer: MICROPRODUCT
    Description:
    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/software/defu/2009/11/mpam-fe_bd_bfaab82af6344bba688fcadfd6c8d8fd669a8a43.exe Destination File: c:\WSUS\WsusContent\43\BFAAB82AF6344BBA688FCADFD6C8D8FD669A8A43.exe.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    Since last month, I have been facing this issue. Thought the issue must be with the firewall but as I change the server's IP, WSUS will start downloading updates & the clients will also get updated. Again after 1 or 2 days, the event viewer will show up the above message again. All the updates will have red cross or the warning icons. What actually could be the reason for this ?

    Wednesday, November 25, 2009 4:25 AM

Answers

  • After running the below command

    %programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

    I am receiving the error message '%program' is not recognized as an internal or external command, operable program or batch file.

    You do realize that %programfiles% is an environment variable?
    Normally refers to C:\Program Files, but can be redirected to an alternate volume.

    The error cited reads as if the substitution was not properly made.

    Alternatively, you can just CD to the necessary directory:

    cd \Program Files\Update Services\Setup
    executeSQL -S %computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

    Also, if you have SQLCMD.exe installed, you can also run this command using the native SQL management utilities.

    sqlcmd.exe -S <sqlserver\instance> -E -b -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"





    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Marked as answer by Eric Zhang CHN Thursday, December 3, 2009 2:22 AM
    Friday, November 27, 2009 6:42 AM

All replies

  • Hi Surya,

    See solution in this KB article:

    922330    Error message when you try to download a file by using the Background Intelligent Transfer Service: "Content file download failed"

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;922330
    Wednesday, November 25, 2009 8:46 AM

  • Hello Eric, thank you for the link.
    As I went through the page, I feel the below section will be the solution for me. But if in case something goes wrong, how do I revert the scenario ?


    If you configured WSUS 3.0 to use an existing installation of SQL Server, type the following command:
    %programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"


    And why is that the problem seems to work out after changing the server's IP ?

    Wednesday, November 25, 2009 1:03 PM
  • how do I revert the scenario?
    %programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=0"

    And why is that the problem seems to work out after changing the server's IP?
    I would be surprised that it did. The culprit in this case is the proxy/firewall/router sitting between the WSUS Server and the Internet, not the IP Address assigned to the WSUS Server -- unless by changing that IP Address you also put it on a different subnet using a different proxy/firewall/router.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, November 25, 2009 6:12 PM
  • After running the below command

    %programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

    I am receiving the error message '%program' is not recognized as an internal or external command, operable program or batch file.
    Thursday, November 26, 2009 7:29 AM
  • After running the below command

    %programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

    I am receiving the error message '%program' is not recognized as an internal or external command, operable program or batch file.

    Well, since I didn't get any response :P ..  I once again changed the server's IP and as I guessed WSUS is downloding those red crossed & ohter updates also.
    Even the server's antivirus definitions including the online clients are updated.

    And I am sure that tomorrow or day after again, WSUS will be idle.

    The new IP falls under the same subnet, same firewall/router.  I have asked my Network Admin whether he's blocked any ports. He denies it.

    Let me check how long this IP will last ! I'll be posting soon again to update the status.
    Thursday, November 26, 2009 3:36 PM
  • After running the below command

    %programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

    I am receiving the error message '%program' is not recognized as an internal or external command, operable program or batch file.

    You do realize that %programfiles% is an environment variable?
    Normally refers to C:\Program Files, but can be redirected to an alternate volume.

    The error cited reads as if the substitution was not properly made.

    Alternatively, you can just CD to the necessary directory:

    cd \Program Files\Update Services\Setup
    executeSQL -S %computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"

    Also, if you have SQLCMD.exe installed, you can also run this command using the native SQL management utilities.

    sqlcmd.exe -S <sqlserver\instance> -E -b -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"





    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Marked as answer by Eric Zhang CHN Thursday, December 3, 2009 2:22 AM
    Friday, November 27, 2009 6:42 AM
  • @Lawrence:
    Well, this is 7th day that I have changed the IP last time and now WSUS is working fine as of now. I didn't trigger the command line 'foreground=1'. (May be)My Network Admin have set some configurations in the firewall that blocked the WSUS ports. My new IP falls under the server-zone in the firewall as designed by Network Admin.

    Lawrence & Eric Zhan, thank you all for your support & suggestions.

     

    Thursday, December 3, 2009 3:44 AM
  • There is a little typo in the command (due to the blank in the pathname). try this instead:

    "%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"


    Thursday, July 28, 2011 9:39 PM
  • There is a little typo in the command (due to the blank in the pathname). try this instead:

    "%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"


    Good catch! I missed that as the specific cause the first time through.

    Yes.. the command string %programfiles%\Update Services\Setup\ExecuteSQL.exe must be enclosed in quotation marks, for two reasons!:

    • The space in the substitution for Program Files.
    • The space in Update Services.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, July 29, 2011 5:12 PM