none
Ran WSUSUTIL RESET on a Disconnected WSUS Server, Now All Updates Are Reporting As Needing Downloading

คำตอบ

  • Might I suggest that if all of the updates are already downloaded, then run BITSADMIN /ALLUSERS /RESET and clear out the BITS queue.

    If you had updates that were showing as needed downloading, and the WSUS console says files are still waiting to be downloaded, then  you have an entirely different issue to diagnose, and running WSUSUTIL RESET did nothing, except perhaps to complicate things.

    The question is whether the downloading is progressing, albeit slowly, or it's been completely stopped. Review the Application Event Log of the WSUS Server for any entries that might explain why the downloading is not progressing.

    Also, if you could itemize the specific updates that are not yet downloaded. Then remove the approvals, clear the BITS queue, and retry by approving ONE update and observing if the download starts and completes.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    • ทำเครื่องหมายเป็นคำตอบโดย Eric Zhang CHNModerator 28 เมษายน 2552 6:49
    23 เมษายน 2552 21:26
    ผู้ดูแล

ตอบทั้งหมด

  • Well it's never a good a idea to run a command without knowing what it will do. What let you to do this in the first place? The command is supposed to look at the metadata and check for missing or corrupted updates. If either case is true then wsus will want to download those updates. Since you say they are there perhaps they are corrupt? Hard to diagnose without knowing why you ran the command in the first place.
    23 เมษายน 2552 14:24
  • Thanks for your response.  I ran the command in the first place because a few updates where showing as needing downloading.  I knew they were there so I thought WSUSUTIL RESET would reindex the database.  Do you have any idea as why WSUS is showing that all the updates need downloading yet they are all on the server?  Is this a corrupt database issue?
    23 เมษายน 2552 14:53
  • It is possible that your database has become corrupt but unfortunately I don't know how you would go about checking this. Your database could be corrupt but if you can access wsus console then chances are it's ok. It could just be that your updates got corrupted and when you ran the reset command it noticed this and said you had to download them again. Have you tried downloading one of the updates and seeing if it downloads fine? If it does then you just might have to take the bullet and download them again over the weekend than trying to mess with the database. Do you have wsus to automatically download the updates during synch or just the metadata? If you just have the metadata then the updates aren't downloaded until you approve them for some group. Is it possible you overlooked this? Also, have you already connected the server to the network?
    23 เมษายน 2552 20:20
  • Might I suggest that if all of the updates are already downloaded, then run BITSADMIN /ALLUSERS /RESET and clear out the BITS queue.

    If you had updates that were showing as needed downloading, and the WSUS console says files are still waiting to be downloaded, then  you have an entirely different issue to diagnose, and running WSUSUTIL RESET did nothing, except perhaps to complicate things.

    The question is whether the downloading is progressing, albeit slowly, or it's been completely stopped. Review the Application Event Log of the WSUS Server for any entries that might explain why the downloading is not progressing.

    Also, if you could itemize the specific updates that are not yet downloaded. Then remove the approvals, clear the BITS queue, and retry by approving ONE update and observing if the download starts and completes.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    • ทำเครื่องหมายเป็นคำตอบโดย Eric Zhang CHNModerator 28 เมษายน 2552 6:49
    23 เมษายน 2552 21:26
    ผู้ดูแล
  • Lawrence,

    When all files were present but WSUS said files are downloading even after an extended period of time, I found the above suggestion to reset BITS, which I did using the psexec -s command.

    What should be the next step to fix this condition:  1) Re-run WSUSUTIL Import again, 2) Run WSUSUTIL RESET, 3) Stop and Restart BITS/WSUS services, 4) Do nothing; the condition should clear within a day or two?

    Before resetting BITS, two errors in the App log are "The server is failing to download some updates." and ""Content file download failed. Reason: The server name or address could not be resolved. Source File... Destination File..."

    This second error seems to be due to the server being a disconnected system unable to reach Microsoft (/msdownload/update/...).  The question really is why does WSUS think it needs to download a file that already exists in its content store?  I properly restored the files before importing the metadata, so that's not the reason.

    Updates prior to about December 2006 are shown as 'Ready for installation', but updates with release dates after then show as 'The update is downloading'.  I do not note any file permission differences between files that WSUS acknowledges are present and those it thinks it doesn't have.



    • แก้ไขโดย StevenBaty 20 สิงหาคม 2557 20:02
    20 สิงหาคม 2557 18:36
  • What should be the next step to fix this condition

    If this is a *disconnected* server, then refresh the ~\WSUSContent store from the connected server and rerun the WSUSUTIL IMPORT. You should never run a WSUSUTIL RESET directly on a disconnected server (but that is what the IMPORT calls "under the covers" that accounts for the 3-4 hours to fully reconcile content with metadata).

    Before resetting BITS, two errors in the App log are "The server is failing to download some updates." and ""Content file download failed. Reason: The server name or address could not be resolved. Source File... Destination File..."

    This second error seems to be due to the server being a disconnected system unable to reach Microsoft (/msdownload/update/...).

    Correct.

    The question really is why does WSUS think it needs to download a file that already exists in its content store?

    That is the key question. The fact that the file is physically present is only half the battle; the file must also be accessible to the WSUSService in order to reconcile it's need against the existing approval for the update.

    There are four scenarios in which a disconnected server will queue a file for "download":

    1. The file was missing from the connected server at the time the ~\WSUSContent folder was copied. (The root cause here is simply not verifying that the connected server has completed its download activities from its own approvals.)
    2. The file did not get copied from the connected server to the disconnected server. (Rarely happens, but I have encountered it.)
    3. The ACLs on the disconnected server are incorrect effectively making the file(s) inaccessible to the WSUSServer, so as a result the service assumes the file is not present, and queues a request with BITS to replace it. (The service doesn't actually know that it's a disconnected server.)
    4. The ~\WSUSContent folder on the disconnected server is not where the WSUSService expects it to be. (Check the 'ContentDir' value in HKLM\Software\Microsoft\Update Services\Server\Setup and verify that it points to the PARENT folder of ~\WSUSContent.)


    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.

    21 สิงหาคม 2557 15:25
    ผู้ดูแล