locked
Content file download failed. Reason: HTTP status 404: The requested URL does not exist on the server. RRS feed

  • Question

  • Hi,

    I am getting this error in most of our WSUS servers.

    Content file download failed.
    Reason: HTTP status 404: The requested URL does not exist on the server.

    Source File: /Content/FB/134501186F4C81089054E4EC3376E74EEC895EFB.exe 
    Destination File: d:\wsus\WsusContent\FB\134501186F4C81089054E4EC3376E74EEC895EFB.exe

     After few minutes, getting below error as well. But i could see the synchronization has completed successfully.

    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          12/19/2014 4:45:55 PM
    Event ID:      10032
    Task Category: 7
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ******
    Description:
    The server is failing to download some updates.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Server Update Services" />
        <EventID Qualifiers="0">10032</EventID>
        <Level>2</Level>
        <Task>7</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-12-19T08:45:55.000000000Z" />
        <EventRecordID>496887</EventRecordID>
        <Channel>Application</Channel>
        <Computer>*****</Computer>
         <Data>The server is failing to download some updates.</Data>
      

    This error is happening everyday. Please advise for a fix.


    • Edited by VenuPsgTech Friday, December 19, 2014 9:30 PM
    Friday, December 19, 2014 9:29 PM

Answers

  • Reason: HTTP status 404: The requested URL does not exist on the server.

    Source File: /Content/FB/134501186F4C81089054E4EC3376E74EEC895EFB.exe 
    Destination File: d:\wsus\WsusContent\FB\134501186F4C81089054E4EC3376E74EEC895EFB.exe

    Source:        Windows Server Update Services
    Description:
    The server is failing to download some updates.

    This error is happening everyday. Please advise for a fix.


    If this is happening on an UPSTREAM server it is because you have approved updates that are no longer available from Microsoft. Almost always this involves approvals of *EXPIRED* updates (which have been pulled from the catalog and cannot be downloaded).

    If this is happening on a DOWNSTREAM server it's because something/someone deleted the files from the upstream server. It can also happen if the entire upstream ~\WSUSContent folder has gone amuk.

    For an upstream server, find the expired updates, remove the approvals, cancel the downloads, and then decline the updates.

    For a downstream server, figure out what the affected updates are and fix the upstream server.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Steven_Lee0510 Wednesday, January 7, 2015 9:00 AM
    Saturday, December 20, 2014 4:20 AM
  • We are managing the updates and computers through SCCM 2012 R2 and not deleting or approving any updates in WSUS.

    Doesn't really matter! A *FILE* that is expected to be present and downloadable is NOT. You need to FIX that defect.

    If this is a Configuration Manager environment, then my question would be this: Why is a downstream server trying to download *FILES* from an upstream server in the first place. The **ONLY** way a downstream server wants to download a *FILE* from an upstream server is because somebody has issued an APPROVAL for that update.

    Finally.. since this is a Configuration Manager issue (would have been very helpful for you to state that in the original post), you really should inquire in the Configuration Manager forum. Our assumption here is that posters are using standalone WSUS server (unless explicitly stated otherwise).


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Steven_Lee0510 Wednesday, January 7, 2015 8:59 AM
    Tuesday, December 23, 2014 6:05 PM

All replies

  • Friday, December 19, 2014 10:51 PM
  • Reason: HTTP status 404: The requested URL does not exist on the server.

    Source File: /Content/FB/134501186F4C81089054E4EC3376E74EEC895EFB.exe 
    Destination File: d:\wsus\WsusContent\FB\134501186F4C81089054E4EC3376E74EEC895EFB.exe

    Source:        Windows Server Update Services
    Description:
    The server is failing to download some updates.

    This error is happening everyday. Please advise for a fix.


    If this is happening on an UPSTREAM server it is because you have approved updates that are no longer available from Microsoft. Almost always this involves approvals of *EXPIRED* updates (which have been pulled from the catalog and cannot be downloaded).

    If this is happening on a DOWNSTREAM server it's because something/someone deleted the files from the upstream server. It can also happen if the entire upstream ~\WSUSContent folder has gone amuk.

    For an upstream server, find the expired updates, remove the approvals, cancel the downloads, and then decline the updates.

    For a downstream server, figure out what the affected updates are and fix the upstream server.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Steven_Lee0510 Wednesday, January 7, 2015 9:00 AM
    Saturday, December 20, 2014 4:20 AM
  • Hi Lawrence, 

    Thanks. But We are managing the updates and computers through SCCM 2012 R2 and not deleting or approving any updates in WSUS. Eventhough synchronization is successful, still receiving this error in most/all of the Downstream servers. 

    All of the servers are giving this path only.

    /Content/FB/134501186F4C81089054E4EC3376E74EEC895EFB.exe

    How to locate this file in the Upstream server?

    • Edited by VenuPsgTech Saturday, December 20, 2014 8:45 PM
    Saturday, December 20, 2014 8:32 PM
  • Hi Lawrence, 

    Thanks. But We are managing the updates and computers through SCCM 2012 R2 and not deleting or approving any updates in WSUS. Eventhough synchronization is successful, still receiving this error in most/all of the Downstream servers. 

    All of the servers are giving this path only.

    /Content/FB/134501186F4C81089054E4EC3376E74EEC895EFB.exe

    How to locate this file in the Upstream server?


    ConfigMgr doesn't download update files from MSFT via WSUS (with the single exception of SCEP definitions). (only the catalog data is download via WSUS)
    And, ConfigMgr doesn't use downstream WSUS concepts at all.

    Something is very wrong with your WSUS/SUP configuration.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Sunday, December 21, 2014 2:55 AM
  • We are managing the updates and computers through SCCM 2012 R2 and not deleting or approving any updates in WSUS.

    Doesn't really matter! A *FILE* that is expected to be present and downloadable is NOT. You need to FIX that defect.

    If this is a Configuration Manager environment, then my question would be this: Why is a downstream server trying to download *FILES* from an upstream server in the first place. The **ONLY** way a downstream server wants to download a *FILE* from an upstream server is because somebody has issued an APPROVAL for that update.

    Finally.. since this is a Configuration Manager issue (would have been very helpful for you to state that in the original post), you really should inquire in the Configuration Manager forum. Our assumption here is that posters are using standalone WSUS server (unless explicitly stated otherwise).


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Steven_Lee0510 Wednesday, January 7, 2015 8:59 AM
    Tuesday, December 23, 2014 6:05 PM
  • Very old thread but I guess below link may help you out

    https://nitishkumar.net/2017/03/19/wsus-and-powershell-declining-and-deleting-updates-based-on-keywords/

    Monday, March 20, 2017 12:08 PM