locked
Computer that can't talk with WSUS. RRS feed

  • Question

  • We are running WSUS 3.0 SP2 on our network.  However, I have one computer that hasn't talked with the WSUS server for a couple of months.  All the other computers are working fine with WSUS.  I've tried to read the log, but haven't made a lot of progress.  I have found similar situations online, but they're usually scenarios where none of the computers talk with WSUS or there's a proxy issue and we don't use a proxy server.  WSUS is configured on the computers via group policy, so the computer should have the same WSUS configuration as the others.  I've even taken it off the domain and put it back, but it made no difference.

    Here is a portion of the windows update log.  WSUS1 is the WSUS server.  There are no other such servers.

    2014-03-24 10:11:57:993 1052 2338 PT WARNING: Cached cookie has expired or new PID is available
    2014-03-24 10:11:57:993 1052 2338 PT Initializing simple targeting cookie, clientId = f67718fb-9b5a-4ab6-b138-df9048ceb711, target group = standard computers, DNS name = rdart3.eddycountynm.local
    2014-03-24 10:11:57:993 1052 2338 PT   Server URL = http://wsus1/SimpleAuthWebService/SimpleAuth.asmx
    2014-03-24 10:12:07:323 1052 2338 Misc WARNING: Send failed with hr = 80072ee7.
    2014-03-24 10:12:07:323 1052 2338 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-03-24 10:12:07:323 1052 2338 PT   + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
    2014-03-24 10:12:07:323 1052 2338 PT   + Caller provided credentials = No
    2014-03-24 10:12:07:323 1052 2338 PT   + Impersonate flags = 0
    2014-03-24 10:12:07:323 1052 2338 PT   + Possible authorization schemes used =
    2014-03-24 10:12:07:323 1052 2338 PT WARNING: GetAuthorizationCookie failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
    2014-03-24 10:12:07:323 1052 2338 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024402c
    2014-03-24 10:12:07:323 1052 2338 PT WARNING: PopulateAuthCookies failed: 0x8024402c
    2014-03-24 10:12:07:323 1052 2338 PT WARNING: RefreshCookie failed: 0x8024402c
    2014-03-24 10:12:07:323 1052 2338 PT WARNING: RefreshPTState failed: 0x8024402c
    2014-03-24 10:12:07:323 1052 2338 PT WARNING: PTError: 0x8024402c
    2014-03-24 10:12:07:323 1052 2338 Report WARNING: Reporter failed to upload events with hr = 8024402c.
    2014-03-24 10:24:17:366 1052 2338 PT WARNING: Cached cookie has expired or new PID is available
    2014-03-24 10:24:17:366 1052 2338 PT Initializing simple targeting cookie, clientId = f67718fb-9b5a-4ab6-b138-df9048ceb711, target group = standard computers, DNS name = rdart3.eddycountynm.local
    2014-03-24 10:24:17:366 1052 2338 PT   Server URL = http://wsus1/SimpleAuthWebService/SimpleAuth.asmx
    2014-03-24 10:24:26:696 1052 2338 Misc WARNING: Send failed with hr = 80072ee7.
    2014-03-24 10:24:26:696 1052 2338 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-03-24 10:24:26:696 1052 2338 PT   + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
    2014-03-24 10:24:26:696 1052 2338 PT   + Caller provided credentials = No
    2014-03-24 10:24:26:696 1052 2338 PT   + Impersonate flags = 0
    2014-03-24 10:24:26:696 1052 2338 PT   + Possible authorization schemes used =
    2014-03-24 10:24:26:696 1052 2338 PT WARNING: GetAuthorizationCookie failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
    2014-03-24 10:24:26:696 1052 2338 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024402c
    2014-03-24 10:24:26:696 1052 2338 PT WARNING: PopulateAuthCookies failed: 0x8024402c
    2014-03-24 10:24:26:696 1052 2338 PT WARNING: RefreshCookie failed: 0x8024402c
    2014-03-24 10:24:26:696 1052 2338 PT WARNING: RefreshPTState failed: 0x8024402c
    2014-03-24 10:24:26:696 1052 2338 PT WARNING: PTError: 0x8024402c
    2014-03-24 10:24:26:696 1052 2338 Report WARNING: Reporter failed to upload events with hr = 8024402c.
    2014-03-24 10:38:30:753 1052 2338 PT WARNING: Cached cookie has expired or new PID is available
    2014-03-24 10:38:30:753 1052 2338 PT Initializing simple targeting cookie, clientId = f67718fb-9b5a-4ab6-b138-df9048ceb711, target group = standard computers, DNS name = rdart3.eddycountynm.local
    2014-03-24 10:38:30:753 1052 2338 PT   Server URL = http://wsus1/SimpleAuthWebService/SimpleAuth.asmx
    2014-03-24 10:38:40:091 1052 2338 Misc WARNING: Send failed with hr = 80072ee7.
    2014-03-24 10:38:40:091 1052 2338 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-03-24 10:38:40:091 1052 2338 PT   + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
    2014-03-24 10:38:40:091 1052 2338 PT   + Caller provided credentials = No
    2014-03-24 10:38:40:091 1052 2338 PT   + Impersonate flags = 0
    2014-03-24 10:38:40:091 1052 2338 PT   + Possible authorization schemes used =
    2014-03-24 10:38:40:091 1052 2338 PT WARNING: GetAuthorizationCookie failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
    2014-03-24 10:38:40:091 1052 2338 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024402c
    2014-03-24 10:38:40:091 1052 2338 PT WARNING: PopulateAuthCookies failed: 0x8024402c
    2014-03-24 10:38:40:091 1052 2338 PT WARNING: RefreshCookie failed: 0x8024402c
    2014-03-24 10:38:40:091 1052 2338 PT WARNING: RefreshPTState failed: 0x8024402c
    2014-03-24 10:38:40:091 1052 2338 PT WARNING: PTError: 0x8024402c
    2014-03-24 10:38:40:091 1052 2338 Report WARNING: Reporter failed to upload events with hr = 8024402c.
    2014-03-24 10:47:22:795 1052 a88 AU Triggering AU detection through DetectNow API
    2014-03-24 10:47:22:795 1052 a88 AU Triggering Online detection (interactive)
    2014-03-24 10:47:22:795 1052 80c AU #############
    2014-03-24 10:47:22:795 1052 80c AU ## START ##  AU: Search for updates
    2014-03-24 10:47:22:795 1052 80c AU #########
    2014-03-24 10:47:22:795 1052 80c AU <<## SUBMITTED ## AU: Search for updates [CallId = {64CC71A7-201E-4202-89AB-696BFDCB59FA}]
    2014-03-24 10:47:22:795 1052 2338 Agent *************
    2014-03-24 10:47:22:795 1052 2338 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-03-24 10:47:22:795 1052 2338 Agent *********
    2014-03-24 10:47:22:795 1052 2338 Agent   * Online = Yes; Ignore download priority = No
    2014-03-24 10:47:22:795 1052 2338 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-03-24 10:47:22:795 1052 2338 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-03-24 10:47:22:795 1052 2338 Agent   * Search Scope = {Machine}
    2014-03-24 10:47:22:795 1052 2338 Setup Checking for agent SelfUpdate
    2014-03-24 10:47:22:795 1052 2338 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-03-24 10:47:22:795 1052 2338 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-03-24 10:47:22:811 1052 2338 Misc  Microsoft signed: Yes
    2014-03-24 10:47:32:295 1052 2338 Misc WARNING: Send failed with hr = 80072ee7.
    2014-03-24 10:47:32:295 1052 2338 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-03-24 10:47:32:295 1052 2338 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://wsus1/selfupdate/wuident.cab>. error 0x8024402c
    2014-03-24 10:47:32:295 1052 2338 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2014-03-24 10:47:32:295 1052 2338 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2014-03-24 10:47:32:295 1052 2338 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2014-03-24 10:47:36:897 1052 2338 Misc WARNING: Send failed with hr = 80072ee7.
    2014-03-24 10:47:36:897 1052 2338 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-03-24 10:47:36:897 1052 2338 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://wsus1/selfupdate/wuident.cab>. error 0x8024402c
    2014-03-24 10:47:36:897 1052 2338 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2014-03-24 10:47:36:897 1052 2338 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2014-03-24 10:47:36:897 1052 2338 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2014-03-24 10:47:41:500 1052 2338 Misc WARNING: Send failed with hr = 80072ee7.
    2014-03-24 10:47:41:500 1052 2338 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-03-24 10:47:41:500 1052 2338 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://wsus1/selfupdate/wuident.cab>. error 0x8024402c
    2014-03-24 10:47:41:500 1052 2338 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2014-03-24 10:47:41:500 1052 2338 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2014-03-24 10:47:41:500 1052 2338 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2014-03-24 10:47:50:672 1052 2338 Misc WARNING: Send failed with hr = 80072ee7.
    2014-03-24 10:47:50:672 1052 2338 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-03-24 10:47:50:672 1052 2338 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://wsus1/selfupdate/wuident.cab>. error 0x8024402c
    2014-03-24 10:47:50:672 1052 2338 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2014-03-24 10:47:50:672 1052 2338 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2014-03-24 10:47:50:672 1052 2338 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2014-03-24 10:47:50:672 1052 2338 Misc WARNING: DownloadFileInternal failed for http://wsus1/selfupdate/wuident.cab: error 0x8024402c
    2014-03-24 10:47:50:672 1052 2338 Setup WARNING: SelfUpdate check failed to download package information, error = 0x8024402C
    2014-03-24 10:47:50:672 1052 2338 Setup FATAL: SelfUpdate check failed, err = 0x8024402C
    2014-03-24 10:47:50:672 1052 2338 Agent   * WARNING: Skipping scan, self-update check returned 0x8024402C
    2014-03-24 10:47:50:750 1052 2338 Agent   * WARNING: Exit code = 0x8024402C
    2014-03-24 10:47:50:750 1052 2338 Agent *********
    2014-03-24 10:47:50:750 1052 2338 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-03-24 10:47:50:750 1052 2338 Agent *************
    2014-03-24 10:47:50:750 1052 2338 Agent WARNING: WU client failed Searching for update with error 0x8024402c
    2014-03-24 10:47:50:750 1052 200c AU >>##  RESUMED  ## AU: Search for updates [CallId = {64CC71A7-201E-4202-89AB-696BFDCB59FA}]
    `2014-03-24 10:47:50:750 1052 200c AU   # WARNING: Search callback failed, result = 0x8024402C
    2014-03-24 10:47:50:750 1052 200c AU   # WARNING: Failed to find updates with error code 8024402C
    2014-03-24 10:47:50:750 1052 200c AU #########
    2014-03-24 10:47:50:750 1052 200c AU ##  END  ##  AU: Search for updates [CallId = {64CC71A7-201E-4202-89AB-696BFDCB59FA}]
    2014-03-24 10:47:50:750 1052 200c AU #############
    2014-03-24 10:47:50:750 1052 200c AU Need to show Unable to Detect notification
    2014-03-24 10:47:50:750 1052 200c AU Successfully wrote event for AU health state:1
    2014-03-24 10:47:50:750 1052 200c AU AU setting next detection timeout to 2014-03-24 21:47:50
    2014-03-24 10:47:50:750 1052 200c AU Setting AU scheduled install time to 2014-03-25 09:00:00
    2014-03-24 10:47:50:750 1052 200c AU Successfully wrote event for AU health state:1
    2014-03-24 10:47:50:750 1052 200c AU Successfully wrote event for AU health state:1
    2014-03-24 10:47:55:758 1052 2338 Report CWERReporter finishing event handling. (00000000)


    Ken Kemp Eddy County, NM IT

    Tuesday, April 1, 2014 8:47 PM

Answers

  • I've seen this article.  That's not my case.  For one thing, I'm using a GPO to set the server name.  But I confirmed it in the registry just the same.

    However, your mention of nslookup made me find something.  Someone had put the wrong address in for WINS.  I corrected it, and WSUS can talk.  Odd that nothing else on the computer ever acted up.

    Thank you for the reply.


    Ken Kemp Eddy County, NM IT

    • Marked as answer by Daniel JiSun Monday, April 7, 2014 2:29 AM
    Thursday, April 3, 2014 10:16 PM

All replies

  • Hi,

    According this blog, the cause could be an incorrect WSUS server name.

    WSUS: Client sync fails with 80072ee7 and 0x8024402c errors in WindowsUpdate.log

    http://blogs.technet.com/b/sus/archive/2008/09/24/wsus-client-sync-fails-with-80072ee7-and-0x8024402c-errors-in-windowsupdate-log.aspx

    Perhaps you have already seen this article, but have you checked the registry key on the client?

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate

    Can this name be resolved on the client? You can test by using nslookup.

    Hope this helps.

    Thursday, April 3, 2014 6:52 AM
  • I've seen this article.  That's not my case.  For one thing, I'm using a GPO to set the server name.  But I confirmed it in the registry just the same.

    However, your mention of nslookup made me find something.  Someone had put the wrong address in for WINS.  I corrected it, and WSUS can talk.  Odd that nothing else on the computer ever acted up.

    Thank you for the reply.


    Ken Kemp Eddy County, NM IT

    • Marked as answer by Daniel JiSun Monday, April 7, 2014 2:29 AM
    Thursday, April 3, 2014 10:16 PM