locked
Client computers pulling some updates from decommissioned WSUS server, not the new WSUS server - how to re-point old update packages? (Not GPO related) RRS feed

  • Question

  • Hello,

    I've recently created a new WSUS server to which all my clients ARE properly reporting to.  Some, but not all, patches are not installing throwing the following error codes:

    Code 80092004
    Code 8024402C

    I started digging into the WindowsUpdates.log file and found that the failed entries are a result of the clients trying to grab the updates from an older (decommissioned) WSUS server. My hunch is the clients were not fully patched but had downloaded "pointers" for update packages associated to my old WSUS server. I then re-pointed my clients via GPO and the update packages are still associated to that old server. New packages are just fine and download/install/report correctly. How does one correct this package pointer association?

    --- SNIP from WindowsUpdates.log ---

    Successfully wrote event for AU health state:0
    2015-06-11 12:48:22:780 456 dcc DnldMgr BITS job {2E8CA723-BC92-454B-BBAE-4D7547F97D4A} hit a transient error, updateId = {642B981F-BF50-467E-B0F3-30EF96CA6CD9}.201, error = 0x80072EE7
    2015-06-11 12:48:22:780 456 dcc Misc WARNING: Send failed with hr = 80072ee7.
    2015-06-11 12:48:22:780 456 dcc Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2015-06-11 12:48:22:780 456 dcc Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://OLD_WSUS_Server_FQDN/Content/A8/33DD180FB1CA49FF4955C7C80033E216AADAA7A8.exe>. error 0x8024402c
    2015-06-11 12:48:22:780 456 dcc Misc WARNING: MakeRequest failed at CDownloadSession::GetResponseHeaders(). error 0x8024402c
    2015-06-11 12:48:22:780 456 dcc DnldMgr WARNING: CUpdateDownloadJob::GetCDN() failed to get response headers for BITS job, error = 8024402c
    2015-06-11 12:48:22:780 456 dcc DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
    2015-06-11 12:48:25:030 456 1e04 DnldMgr BITS job {80EB3A8C-7177-4D96-89E5-733E581E2D26} hit a transient error, updateId = {B21B5882-BD05-4ACC-B30F-28D5F556A5A4}.202, error = 0x80072EE7
    2015-06-11 12:48:25:030 456 1e04 Misc WARNING: Send failed with hr = 80072ee7.
    2015-06-11 12:48:25:030 456 1e04 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2015-06-11 12:48:25:030 456 1e04 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://OLD_WSUS_Server_FQDN/Content/B6/0F3585701CD216781AD7D2C0E5A5A451854B6FB6.exe>. error 0x8024402c
    2015-06-11 12:48:25:030 456 1e04 Misc WARNING: MakeRequest failed at CDownloadSession::GetResponseHeaders(). error 0x8024402c
    2015-06-11 12:48:25:030 456 1e04 DnldMgr WARNING: CUpdateDownloadJob::GetCDN() failed to get response headers for BITS job, error = 8024402c
    2015-06-11 12:48:25:030 456 1e04 DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
    2015-06-11 12:48:25:030 456 190c AU Getting featured update notifications.  fIncludeDismissed = true
    2015-06-11 12:48:25:030 456 190c AU No featured updates available.
    2015-06-11 12:48:25:108 456 190c AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2015-06-11 12:48:25:108 456 190c AU Triggering Offline detection (non-interactive)
    2015-06-11 12:48:25:108 456 190c AU AU setting pending client directive to 'Reboot Pending'
    2015-06-11 12:48:25:108 456 190c AU Changing existing AU client directive from 'Progress Ux' to 'Reboot Pending', session id = 0x2
    2015-06-11 12:48:25:108 456 190c AU Successfully wrote event for AU health state:0

    --- SNIP from WindowsUpdates.log ---

    Thank you for any advice.

    MJ


    • Edited by JFSEC Thursday, June 11, 2015 8:15 PM title update
    Thursday, June 11, 2015 8:11 PM

Answers

  • Probably, these are incomplete BITS jobs, which need to be deleted/removed, and then WUAgent will create new BITS jobs to pull from your new WSUS.

    BITSADMIN (or the Powershell equivalent) can help you zap those futile jobs.


    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!)

    Thursday, June 11, 2015 9:06 PM

All replies

  • Probably, these are incomplete BITS jobs, which need to be deleted/removed, and then WUAgent will create new BITS jobs to pull from your new WSUS.

    BITSADMIN (or the Powershell equivalent) can help you zap those futile jobs.


    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!)

    Thursday, June 11, 2015 9:06 PM
  • Thanks Don, i'll read up on how to do that and see what I get.  I'm not familiar with BITSADMIN use, but i'm sure a little searching will provide my answer.

    Friday, June 12, 2015 2:46 PM
  • Hello

    This problem is probably nothing to do with BITS and everything to do with stale content in the client-side SOFTWAREDISTRIBUTION folder.

    Please read this post carefully:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/50f16d20-88a3-4964-99b0-c8ad155dac63/wsus-30-ipv4-issue-download-failures?forum=winserverwsus

    good luck :-)

    Sunday, June 14, 2015 6:08 PM