none
Event ID 10032 Some old updates not downloading causing errors in logs

    Question

  • Hi Guys,

    I am having problems with downloading certain updates on the USS. They are very old and unwanted updates which are failing.

    For example in the Software Distribution.log

     Error WsusService.26 ContentSyncAgent.Download File windows2000-kb2524426-x86-custom-enu.exe, RowId 1e945748-ac45-4d43-90be-8430b29b85aa: MUUrl is null/empty

    There are also some errors like this which I am not sure are related

    2013-07-24 17:00:21.544 UTC Warning w3wp.7 ServerImplementation.DownloadFiles spDownloadFiles rejected the following requested FileDigests.
    7F61C1DDA0B276360E065FB51D2EA9FD5F0389A4|
    2013-07-24 17:00:21.544 UTC Warning w3wp.7 SoapUtilities.CreateException ThrowException: actor = http://WSUSServer/ServerSyncWebService/ServerSyncWebService.asmx, ID=4f9c7d90-82c0-49dd-b60d-5bc04adb17fb, ErrorCode=FileDigestsMissing, Message=7F61C1DDA0B276360E065FB51D2EA9FD5F0389A4|, Client=?

    There are some errors in the DSS which I would like to come to after the USS issue has been resolved.

    How do I get rid of these unwanted updates that are trying to download?

    Also, what does ErrorCode=FileDigestsMissing mean and why is this error coming up?




    • Edited by Webbeye Tuesday, September 17, 2013 1:43 PM
    Tuesday, September 17, 2013 1:41 PM

Answers

  • Thanks Lawrence...

    Is it okay to unsinatll wsus on upsteam server and start with a new database? Would the downstream servers be upset if done this way? Would the resync from downstream servers cause problems?




    Installing a new wsus with database on an upstream server is fine, just be sure to do the initial sync of that server as a replica from an existing replica server so the database is consistent with the replica servers.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    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 Webbeye Wednesday, October 16, 2013 1:53 PM
    Wednesday, October 16, 2013 1:47 PM

All replies

  • They are very old and unwanted updates which are failing.

    So why are they even approved? What value exists in downloading the content?

    Error WsusService.26 ContentSyncAgent.Download File windows2000-kb2524426-x86-custom-enu.exe, RowId 1e945748-ac45-4d43-90be-8430b29b85aa: MUUrl is null/empty

    Also, even if you got it downloaded, none of your Windows 2000 systems will be able to install it.

    Aside from that KB2524426 (MS11-035) is a superseded update, by MS11-070 (which also does not have a Windows 2000 instance).

    Also, it has a Release Date after the end of Extended Support for Windows 2000, so I'm even surprised that there IS a KB2524426 for Windows 2000. Actually, on the lab system where I still sync Windows 2000 updates, I don't have a Win2000 update for MS11-035.

    However the use of the keyword *CUSTOM* in that filename is highly suggestive to me, so another relevant question is how you got this Windows 2000 update into your WSUS Server (and when?). My guess would be that the named file isn't available for download from the public catalog, and whatever methodology was used to import this custom (extra-support) update into WSUS probably was not performed correctly (which would have included the binary).

    How do I get rid of these unwanted updates that are trying to download?

    Remove the update approvals, right click on the update and select "Cancel Download"


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

    Tuesday, September 17, 2013 6:48 PM
  • Hi Lawrence,

    I really appreciate your help.

    I have confirmed that the update in question has a status of declined, there is no option in the console when right clicking the update to "cancel download"

    I am clearing in BITS queue and going to see if that helps

    BITSADMIN /RESET /ALLUSERS

    Then run

    Run the command wsusutil reset to re-queue the updates that do need to download content files.


    • Edited by Webbeye Wednesday, September 18, 2013 11:38 AM
    Wednesday, September 18, 2013 11:38 AM
  • I have confirmed that the update in question has a status of declined, there is no option in the console when right clicking the update to "cancel download"

    Cancelling the download should occur prior to declining the update. The exact sequence of steps would be:

    1. Remove any existing approvals.
    2. Cancel the download.
    3. Decline the update.

    I am clearing in BITS queue and going to see if that helps

    BITSADMIN /RESET /ALLUSERS

    Yes, on a WS2003 system this command can also be used.


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

    Wednesday, September 18, 2013 3:56 PM
  • I am waiting for the results of clearing the bits queue..

    If the issue with the updates persists after then what is the next move I your opinion? Locate and delete from the database?



    • Edited by Webbeye Thursday, September 19, 2013 1:18 PM
    Thursday, September 19, 2013 1:18 PM
  • I am waiting for the results of clearing the bits queue..

    I'm not quite understanding what you mean by this. The results should be instantaneous.

    Following the execution of BITSADMIN /RESET /ALLUSERS run another BITSADMIN /LIST /ALLUSERS and there should be no jobs in the queue.

    If the issue with the updates persists after then what is the next move I your opinion? Locate and delete from the database?

    Locating and deleting from the database is not a practical option. For one, because the database knows nothing about the download queue. All it knows is that [a] a request has been queued, or [b] the queued request has been completed (or cancelled).

    For two, even if it did know, finding all of the requisite rows in the various tables needed is an onerous task, and still wouldn't impact the pending downloads in the BITS queue.


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

    Friday, September 20, 2013 11:12 PM
  • After clearing the BITS queue and running and wsusutil reset

    The same old updates reappeared and are failing to download?

    I don't really know where to go from here?

    Thanks in advance



    • Edited by Webbeye Monday, September 23, 2013 11:35 AM
    Monday, September 23, 2013 11:35 AM
  • After clearing the BITS queue and running and wsusutil reset

    The same old updates reappeared and are failing to download?

    The only way this sequence of events could occur is if those updates are still Approved for Install.

    OR the BITSADMIN /RESET failed, and these are still the original jobs queued.


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

    Tuesday, September 24, 2013 10:22 PM
  • This is how I advised to clear the bits queue

         Copy and then paste the following commands into Notepad.

    net stop bits
    net stop wuauserv
    Ipconfig /flushdns
    cd "Documents and Settings\All Users\Application Data\Microsoft\Network\Downloader"
    del qmgr0.dat
    del qmgr1.dat
    net start bits
    net start wuauserv

    1.       Save the file to your desktop as clear.bat. To do this, follow these steps:
      1.       In Notepad, click File, click Save As, and then type clear.bat.
      2.       Click the Save as type list, select All Files (*.*), and then click Save.
    2.       On the desktop, right-click the clear.bat file, and then click Run as administrator

    How do I check if the queue was cleared?

    From the WSUS console the updates are declined status...

    This does not make sense :(


    • Edited by Webbeye Wednesday, September 25, 2013 3:44 PM
    Wednesday, September 25, 2013 3:44 PM
  • This is how I advised to clear the bits queue

    I can't speak to the script. On BITS v3 and earlier implementations on WS2008 and earlier, the BITSADMIN utility can be used to both check the queue and clear the queue.

    Also available starting with BITS v3 and WS2008 is a PowerShell cmdlet collection, but it has a couple of quirky behaviors, discussed elsehwere, but still it amounts to using the provided interface tools for that purpose.

    (And not really sure what the point is in clearing the DNS client cache. Most intriguing though.)

    From the WSUS console the updates are declined status...

    This does not make sense :(

    Makes perfect sense. Updates were approved. Download never actually happened. Updates got declined with a pending download. Not the ideal order of things.

    Better choice would be:

    1. Set update to Not Approved.
    2. Cancel Download using WSUS console.
    3. Verify download is cancelled (using BITSADMIN or PowerShell, as appropriate).
    4. Decline update.

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

    Wednesday, September 25, 2013 8:31 PM
  • Again thanks for your reply, Lawrence.

    I used the BITSADMIN Utility this time

    C:\>BITSADMIN /RESET /ALLUSERS

    BITSADMIN version 3.0 [ 7.5.7600 ]

    BITS administration utility.

    (C) Copyright 2000-2006 Microsoft Corp.

    BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.

    Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

    0 out of 0 jobs canceled.

    C:\>BITSADMIN /LIST /ALLUSERS

    BITSADMIN version 3.0 [ 7.5.7600 ]

    BITS administration utility.

    (C) Copyright 2000-2006 Microsoft Corp.

    BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.

    Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

    Listed 0 job(s).

    This suggests the queue was already empty..

    I am checking the SoftwareDistribution.log when I get it to see if the old update is still in there



    • Edited by Webbeye Friday, September 27, 2013 3:30 PM
    Friday, September 27, 2013 3:30 PM
  • To address event 10032, please refer to the following article:

    http://social.technet.microsoft.com/Forums/en-US/7f63915a-7ddb-408c-8a91-034df9b96342/event-id-10032-the-server-is-failing-to-download-some-updates

    http://social.technet.microsoft.com/Forums/en-US/c8bbb8b7-b619-4c9d-8787-3611bf2f2958/the-server-is-failing-to-download-some-updates-event-id-10032


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, September 28, 2013 3:31 AM
  • They custom updates were imported using WSUSImportTool.exe ...

    They are declined in WSUS console and I have cleared the BITS queue but they still come back in the SoftareDistribution.log..

    There must be a way to get rid of these updates manually?

    WHat table in the database can I check to see if the updates has been declined or if its required for download?

    Thanks in advance




    • Edited by Webbeye Tuesday, October 01, 2013 3:36 PM
    Tuesday, October 01, 2013 2:06 PM
  • In the database view PUBLIC_VIEWS.vUpdate I can see the Is Declined colum is set to 1 which means its been declined...

    Alsp, there are 0 rows for the particular UpdateID in PUBLIC_VIEWS.vUpdateApproval

    Any thoughts?



    • Edited by Webbeye Monday, October 07, 2013 12:20 PM
    Monday, October 07, 2013 12:20 PM
  • They custom updates were imported using WSUSImportTool.exe ...

    Well... that explains a LOT. :-//

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

    Monday, October 07, 2013 11:30 PM
  • Do you mean that the WSUSImportTool.exe tool is not good in your experience and can cause issues, or, have I not provided enough information and I have not picked up on the sarcasm? :)



    • Edited by Webbeye Tuesday, October 08, 2013 8:38 AM
    Tuesday, October 08, 2013 8:38 AM
  • Do you mean that the WSUSImportTool.exe tool is not good in your experience and can cause issues, or, have I not provided enough information and I have not picked up on the sarcasm? :)

    A bit of both, actually, but also some clarification should exist before I launch into a detailed explanation. By "WSUSImportTool.exe" -- which I'm not aware actually exists in that name -- are you referring to the wsusutil import command (which is designed to work with a CAB file built from a wsusutil export command) which is a supported tool for WSUS v3, or are you referring to the WSUSMigrationImport tool (which is designed to work with an XML file built from the WSUSMigrationExport tool) and is an unsupported tool contained in the API Samples and Tools Kit?

    If the former, there's a significant possibility that the schema of the custom update XML provided for those Windows 2000 updates is not compatible with a WSUS v3.2.7600.256 server (never mind the fact that a Windows 2000 system couldn't get those updates from a build 251 or newer WSUS server anyway). A very distinct possibility is that your import was corrupted from the start (which may also explain the download failures), and would, of course, also potentially explain issues with cleanup efforts.

    If the latter, the WSUSImportTool is part of the WSUS API Samples and Tools kit -- the key point here being the keyword "Samples". It is unsupported code, and was originally written to the WSUS v2 API specification. Also notable is that it's x86 (32-bit) code, although that shouldn't necessarily be an issue itself.

    Both tools were designed for migrating data from one WSUS server to another, and may be dependent upon XML schemas specific to those tools. The wsusutil tool is designed to migrate update metadata (but not approvals). The WSUSMigration tools (in the API Samples and Tools Kit) is designed to migrate update approvals and target groups -- primarily to facilitate the migration of WSUS v2 servers. Actually, I don't even think the WSUSMigrationImport tool is capable of reading update metadata.

    In any event, the purpose of these tools did not include importing fresh updates, or custom updates (such as those written for Windows 2000 Premier Support customers), and that may well be the root cause of all of these issues.

    With respect to the sample tools, numerous issues have been encountered using this legacy code on WSUS v3 servers. The code was intended as a sample, and may well have defects in it incurred as a result of changes to the API over the past eight years.

    Regardless of which tool was actually used, my guess would be that using this tool to import your Windows 2000 updates worked just well enough to get portions of the database populated with relevant table data, but not well enough to actually allow them to be used (or, apparently, as was the original issue -- to be downloaded -- which is also dependent on whether those binaries are actually publicly available from the URL encoded into the metadata).

    Finally, not directly related to the tool used, but now also relevant that I've learned the provenance of these particular updates,  there is also the matter of when those packages were created, and what certificate chain was used to create them, inasmuch as the entire WU/WSUS certificate infrastructure was replaced in April, 2012, those packages may well be unusable in their form in any capacity -- except on a WSUS v3.27600.226 (unpatched) server.


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

    Tuesday, October 08, 2013 6:53 PM
  • Thank you for the detailed response, Lawrence!

    I found this information in a TechNet forum with a link to a guys blog below, also, which has steps on how the tool is used. I have never came across this tool either!

    http://social.technet.microsoft.com/Forums/systemcenter/en-US/5fd8c223-d18a-48f2-bf39-1f7c54cad5c9/custom-support-agreement-updatespatches-with-scup?forum=configmgrsum

    Summary: The native WSUSUtil.exe tool is NOT the tool to use for CSA patches.  SCUP is also NOT the tool for the job.  The special super-secret WSUS CSA Insert Tool is the only thing that can handle pumping the metadata into WSUS for Custom Support Agreement patches.  I was given the July 2010 release which has a file version of 3.1.7600.228.  I have no idea if there are other versions.  The documentation version is 1.0 and is a mere 5 pages.  There isn't really much to it, just a few parameters on a command line:

    WSUSImportTool.exe <ScanCAB> <PayloadDir> [WorkingDir] [help]

    http://chadstech.net/microsoft-csa-patches

    I assume that they have imported the Metadata and either deleted the patch files or did not specify the local location to download the patch files? But I am guessing at this point..


    • Edited by Webbeye Wednesday, October 09, 2013 8:53 AM
    Wednesday, October 09, 2013 8:53 AM
  • The source location of this update is "Microsoft Update".. I would expect it to be a local source location...


    • Edited by Webbeye Wednesday, October 09, 2013 10:31 AM
    Wednesday, October 09, 2013 10:31 AM
  • I want to determine if this issue is related to WSUS requesting bits to download the update or Bits queue not being cleared/hanging onto the job...

    I have changed the MUUrl is null/empty value from "Null" to "Local" in the database and will wait if the SoftwareDistribution.log stops complaining about it being empty...

    Also, as the bits job fails in a second I am not sure when clearing the queue it actually catches the job and cancels it... as when clearing it comes back with 0 jobs cancelled..

    Would reinstalling bits be an issue?? I am thinking it will wipe the bits slate clean..

    Thanks





    • Edited by Webbeye Friday, October 11, 2013 4:33 PM
    Friday, October 11, 2013 4:30 PM
  • If the most recent version of the tool is v3.1, then you can assume it was written to work in conjunction with WSUS v3 (SP1) (which also makes it about six years old, in that incarnation), and it's possible that schema and/or API changes made in WSUS v3 since then will be problematic for that tool.

    Most significantly the aforementioned KB2734608, which modifies the WSUS schema to support SHA-256 hashes for Win8/WS2012 updates.

    My expectation would be that importing those updates into anything except a WSUS v3.1 server would be problematic. Whether such updates would survive an upgrade to SP2 and/or the installation of KB2734608 is yet another question for testing.

    However, to the point made in the ConfigMgr thread... if you're using that super-secret tool for CSA updates, then this forum is not going to be much help, and I would suggest making use of that Premier Support Agreement and open a ticket with Microsoft. :-)


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

    Friday, October 11, 2013 5:59 PM
  • Thanks Lawrence..

    Last question, If it turned out as a reinstall down the line for the wsus upstream server which is having the issues, would this be a problem as there are quite a few downstream servers replicas and autonomous?



    • Edited by Webbeye Monday, October 14, 2013 2:59 PM
    Monday, October 14, 2013 2:59 PM
  • If it turned out as a reinstall down the line for the wsus upstream server which is having the issues, would this be a problem as there are quite a few downstream servers replicas and autonomous?

    Generally speaking... if you've already deployed KB2734608 to your servers, then it would be critical to ensure KB2734608 is installed to a new upstream server prior to allowing the downstream servers to synchronize.

    Otherwise, I'm not aware there would be any other issues as a result of reinstalling the upstream server.


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

    Monday, October 14, 2013 9:42 PM
  • Thanks Lawrence...

    Is it okay to unsinatll wsus on upsteam server and start with a new database? Would the downstream servers be upset if done this way? Would the resync from downstream servers cause problems?




    • Edited by Webbeye Wednesday, October 16, 2013 11:45 AM
    Wednesday, October 16, 2013 11:44 AM
  • Thanks Lawrence...

    Is it okay to unsinatll wsus on upsteam server and start with a new database? Would the downstream servers be upset if done this way? Would the resync from downstream servers cause problems?




    Installing a new wsus with database on an upstream server is fine, just be sure to do the initial sync of that server as a replica from an existing replica server so the database is consistent with the replica servers.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    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 Webbeye Wednesday, October 16, 2013 1:53 PM
    Wednesday, October 16, 2013 1:47 PM
  • Thanks for the links Anna

    I have read these in the past.

    I found a PS script to delete declined updates so I am waiting to see if this sorts the problem out to stop the rogue updates from downloading even though they are declined



    • Edited by Webbeye Friday, November 01, 2013 10:56 AM
    Friday, November 01, 2013 10:56 AM
  • Any updates? Webbeye

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, November 12, 2013 8:27 AM
  • The best I could do is use a script to delete the declined updates. Even though they are declined the custom updates are still presented to bits for download... so deleting the updates is the only way I could find to stop them

    Kevin Case | My blog www.sccmroad.wordpress.com/ Twitter: @casekev | | Please mark as helpful/answer if this resolved your issue

    • Marked as answer by Webbeye Tuesday, November 12, 2013 11:29 AM
    • Unmarked as answer by Webbeye Tuesday, November 12, 2013 11:29 AM
    Tuesday, November 12, 2013 11:29 AM