locked
Client Computer not yet reported with error 0x80072ee2 RRS feed

  • Question

  • We have recently put the WSUS service on one of our Server 2012 servers that we use as a catch all for administrative tools.  After testing it with a couple of servers and some PCs, all of which worked perfectly, we rolled out our GPOs to have the entire network talk to the WSUS server.

    Now, however, we have several Servers and PCs that have shown up and it shows the Last Status Report as being Not Reported Yet.  I have started working on one of the servers and have seen that in the Event Viewer it received the error 0x80072ee2.  I have looked on the internet and almost all the comments are to check my proxy.  We have NO proxy server being used.  I have checked to make sure the client doesn't have that set up.  I have done the following steps on the client to no avail:

    1. Made sure there was no proxy.
    2. Pinged WSUS Server from Client (Pings go through)
    3. HTTP web request from client to server (http://servername:8530/SimpleAuthWebService/SimpleAuth.asmx returns a page)
    4. Reset Windows Update Components (https://support.microsoft.com/en-us/kb/971058)
    5. Checked the Registry settings of WUServer and WUStatusServer are correct
    6. Since the Server we have WSUS on has multiple IP addresses, I changed in the GPO to select http://<IPaddy>:8530 instead

    Unfortunately, none of these things have helped.  When I look at the other server logs I am seeing a combination of 80072ee2 and other error codes stating that they are timing out trying to access WSUS. 

    I appreciate any help provided.

    Thank you.

    Tuesday, April 5, 2016 4:09 PM

All replies

  • Hi,

    >>Since the Server we have WSUS on has multiple IP addresses, I changed in the GPO to select http://<IPaddy>:8530 instead

    Multi-homed may cause communication issue. Please try to disable other adapters then check the updates on the client again. If issue persists, please post the Windowsupdate.log of the client here.

    This log is useful for further troubleshooting.

    Best Regards,


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, April 6, 2016 12:51 PM
  • Hi Steven,

    Thank you for your help.  We have only one adapter on the WSUS server, and it has multiple IP addresses.  I was talking to my other admin who set it up the virtual server and we would not be able to remove both do the the way the server was set up.  Here is the windows log I have gotten as of this morning.

    Again thank you for your help.

    2016-04-06    00:47:21:632    1004    90c    AU    AU received policy change subscription event
    2016-04-06    05:38:41:960    1004    90c    AU    #############
    2016-04-06    05:38:41:960    1004    90c    AU    ## START ##  AU: Search for updates
    2016-04-06    05:38:41:960    1004    90c    AU    #########
    2016-04-06    05:38:41:960    1004    90c    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {E4D3310A-34C1-4D59-BDF6-E700A854108A}]
    2016-04-06    05:38:41:960    1004    13f0    Agent    *************
    2016-04-06    05:38:41:960    1004    13f0    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-04-06    05:38:41:960    1004    13f0    Agent    *********
    2016-04-06    05:38:41:960    1004    13f0    Agent      * Online = Yes; Ignore download priority = No
    2016-04-06    05:38:41:960    1004    13f0    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"
    2016-04-06    05:38:41:960    1004    13f0    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-04-06    05:38:41:960    1004    13f0    Agent      * Search Scope = {Machine}
    2016-04-06    05:38:42:023    1004    13f0    Setup    Checking for agent SelfUpdate
    2016-04-06    05:38:42:023    1004    13f0    Setup    Client version: Core: 7.6.7601.19161  Aux: 7.6.7601.19161
    2016-04-06    05:38:44:615    1004    13f0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-04-06    05:38:44:615    1004    13f0    Misc     Microsoft signed: NA
    2016-04-06    05:38:44:615    1004    13f0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP7970.tmp with dwProvFlags 0x00000080:
    2016-04-06    05:38:44:646    1004    13f0    Misc     Microsoft signed: NA
    2016-04-06    05:38:44:646    1004    13f0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-04-06    05:38:44:646    1004    13f0    Misc     Microsoft signed: NA
    2016-04-06    05:38:44:646    1004    13f0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-04-06    05:38:44:646    1004    13f0    Misc     Microsoft signed: NA
    2016-04-06    05:38:44:693    1004    13f0    Setup    Determining whether a new setup handler needs to be downloaded
    2016-04-06    05:38:44:693    1004    13f0    Setup    SelfUpdate handler is not found.  It will be downloaded
    2016-04-06    05:38:44:693    1004    13f0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-04-06    05:38:45:864    1004    13f0    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-04-06    05:38:45:864    1004    13f0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-04-06    05:38:45:896    1004    13f0    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-04-06    05:38:45:896    1004    13f0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-04-06    05:38:45:943    1004    13f0    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-04-06    05:38:45:943    1004    13f0    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-04-06    05:38:47:379    1004    13f0    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-04-06    05:38:47:379    1004    13f0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.0.168:8530/ClientWebService/client.asmx
    2016-04-06    05:38:47:411    1004    13f0    PT    WARNING: Cached cookie has expired or new PID is available
    2016-04-06    05:38:47:411    1004    13f0    PT    Initializing simple targeting cookie, clientId = 4503ab35-53a6-4451-88d6-0767d6215e25, target group = , DNS name = client.domain.int
    2016-04-06    05:38:47:411    1004    13f0    PT      Server URL = http://192.168.0.168:8530/SimpleAuthWebService/SimpleAuth.asmx
    2016-04-06    05:39:49:895    1004    13f0    Misc    WARNING: Send failed with hr = 80072ee2.
    2016-04-06    05:39:49:895    1004    13f0    Misc    WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-04-06    05:39:49:895    1004    13f0    Misc    FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    PT      + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-04-06    05:39:49:895    1004    13f0    PT      + Caller provided credentials = No
    2016-04-06    05:39:49:895    1004    13f0    PT      + Impersonate flags = 0
    2016-04-06    05:39:49:895    1004    13f0    PT      + Possible authorization schemes used =
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: PTError: 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: Sync of Updates: 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    Agent      * WARNING: Failed to synchronize, error = 0x80072EE2
    2016-04-06    05:39:49:895    1004    13f0    Agent      * WARNING: Exit code = 0x80072EE2
    2016-04-06    05:39:49:895    1004    13f0    Agent    *********
    2016-04-06    05:39:49:895    1004    13f0    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-04-06    05:39:49:895    1004    13f0    Agent    *************
    2016-04-06    05:39:49:895    1004    13f0    Agent    WARNING: WU client failed Searching for update with error 0x80072ee2
    2016-04-06    05:39:49:910    1004    d2c    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {E4D3310A-34C1-4D59-BDF6-E700A854108A}]
    2016-04-06    05:39:49:910    1004    d2c    AU      # WARNING: Search callback failed, result = 0x80072EE2
    2016-04-06    05:39:49:910    1004    d2c    AU      # WARNING: Failed to find updates with error code 80072EE2
    2016-04-06    05:39:49:910    1004    d2c    AU    #########
    2016-04-06    05:39:49:910    1004    d2c    AU    ##  END  ##  AU: Search for updates [CallId = {E4D3310A-34C1-4D59-BDF6-E700A854108A}]
    2016-04-06    05:39:49:910    1004    d2c    AU    #############
    2016-04-06    05:39:49:910    1004    d2c    AU    Successfully wrote event for AU health state:0
    2016-04-06    05:39:49:910    1004    d2c    AU    AU setting next detection timeout to 2016-04-06 15:39:49
    2016-04-06    05:39:49:910    1004    d2c    AU    Setting AU scheduled install time to 2016-04-10 03:00:00
    2016-04-06    05:39:49:910    1004    d2c    AU    Successfully wrote event for AU health state:0
    2016-04-06    05:39:49:910    1004    d2c    AU    Successfully wrote event for AU health state:0
    2016-04-06    05:39:54:892    1004    13f0    Report    REPORT EVENT: {D201CB55-7442-41E2-AA15-BD1C47EBBC6E}    2016-04-06 05:39:49:895-0500    1    148    101    {00000000-0000-0000-0000-000000000000}    0    80072ee2    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80072ee2.
    2016-04-06    05:39:54:924    1004    13f0    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-04-06    05:39:54:924    1004    13f0    Report    WER Report sent: 7.6.7601.19161 0x80072ee2(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2016-04-06    05:43:13:809    1004    13f0    PT    WARNING: Cached cookie has expired or new PID is available
    2016-04-06    05:43:13:809    1004    13f0    PT    Initializing simple targeting cookie, clientId = 4503ab35-53a6-4451-88d6-0767d6215e25, target group = , DNS name = client.domain.int
    2016-04-06    05:43:13:809    1004    13f0    PT      Server URL = http://192.168.0.168:8530/SimpleAuthWebService/SimpleAuth.asmx
    2016-04-06    05:43:16:137    1004    13f0    Report    Uploading 1 events using cached cookie, reporting URL = http://192.168.0.168:8530/ReportingWebService/ReportingWebService.asmx
    2016-04-06    05:43:16:137    1004    13f0    Report    Reporter successfully uploaded 1 events.2016-04-06    00:47:21:632    1004    90c    AU    AU received policy change subscription event
    2016-04-06    05:38:41:960    1004    90c    AU    #############
    2016-04-06    05:38:41:960    1004    90c    AU    ## START ##  AU: Search for updates
    2016-04-06    05:38:41:960    1004    90c    AU    #########
    2016-04-06    05:38:41:960    1004    90c    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {E4D3310A-34C1-4D59-BDF6-E700A854108A}]
    2016-04-06    05:38:41:960    1004    13f0    Agent    *************
    2016-04-06    05:38:41:960    1004    13f0    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-04-06    05:38:41:960    1004    13f0    Agent    *********
    2016-04-06    05:38:41:960    1004    13f0    Agent      * Online = Yes; Ignore download priority = No
    2016-04-06    05:38:41:960    1004    13f0    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"
    2016-04-06    05:38:41:960    1004    13f0    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-04-06    05:38:41:960    1004    13f0    Agent      * Search Scope = {Machine}
    2016-04-06    05:38:42:023    1004    13f0    Setup    Checking for agent SelfUpdate
    2016-04-06    05:38:42:023    1004    13f0    Setup    Client version: Core: 7.6.7601.19161  Aux: 7.6.7601.19161
    2016-04-06    05:38:44:615    1004    13f0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-04-06    05:38:44:615    1004    13f0    Misc     Microsoft signed: NA
    2016-04-06    05:38:44:615    1004    13f0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP7970.tmp with dwProvFlags 0x00000080:
    2016-04-06    05:38:44:646    1004    13f0    Misc     Microsoft signed: NA
    2016-04-06    05:38:44:646    1004    13f0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-04-06    05:38:44:646    1004    13f0    Misc     Microsoft signed: NA
    2016-04-06    05:38:44:646    1004    13f0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-04-06    05:38:44:646    1004    13f0    Misc     Microsoft signed: NA
    2016-04-06    05:38:44:693    1004    13f0    Setup    Determining whether a new setup handler needs to be downloaded
    2016-04-06    05:38:44:693    1004    13f0    Setup    SelfUpdate handler is not found.  It will be downloaded
    2016-04-06    05:38:44:693    1004    13f0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-04-06    05:38:45:864    1004    13f0    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-04-06    05:38:45:864    1004    13f0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-04-06    05:38:45:896    1004    13f0    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-04-06    05:38:45:896    1004    13f0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-04-06    05:38:45:943    1004    13f0    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-04-06    05:38:45:943    1004    13f0    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-04-06    05:38:47:379    1004    13f0    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-04-06    05:38:47:379    1004    13f0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.0.168:8530/ClientWebService/client.asmx
    2016-04-06    05:38:47:411    1004    13f0    PT    WARNING: Cached cookie has expired or new PID is available
    2016-04-06    05:38:47:411    1004    13f0    PT    Initializing simple targeting cookie, clientId = 4503ab35-53a6-4451-88d6-0767d6215e25, target group = , DNS name = client.domain.int
    2016-04-06    05:38:47:411    1004    13f0    PT      Server URL = http://192.168.0.168:8530/SimpleAuthWebService/SimpleAuth.asmx
    2016-04-06    05:39:49:895    1004    13f0    Misc    WARNING: Send failed with hr = 80072ee2.
    2016-04-06    05:39:49:895    1004    13f0    Misc    WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-04-06    05:39:49:895    1004    13f0    Misc    FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    PT      + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-04-06    05:39:49:895    1004    13f0    PT      + Caller provided credentials = No
    2016-04-06    05:39:49:895    1004    13f0    PT      + Impersonate flags = 0
    2016-04-06    05:39:49:895    1004    13f0    PT      + Possible authorization schemes used =
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: PTError: 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: Sync of Updates: 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    PT    WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
    2016-04-06    05:39:49:895    1004    13f0    Agent      * WARNING: Failed to synchronize, error = 0x80072EE2
    2016-04-06    05:39:49:895    1004    13f0    Agent      * WARNING: Exit code = 0x80072EE2
    2016-04-06    05:39:49:895    1004    13f0    Agent    *********
    2016-04-06    05:39:49:895    1004    13f0    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-04-06    05:39:49:895    1004    13f0    Agent    *************
    2016-04-06    05:39:49:895    1004    13f0    Agent    WARNING: WU client failed Searching for update with error 0x80072ee2
    2016-04-06    05:39:49:910    1004    d2c    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {E4D3310A-34C1-4D59-BDF6-E700A854108A}]
    2016-04-06    05:39:49:910    1004    d2c    AU      # WARNING: Search callback failed, result = 0x80072EE2
    2016-04-06    05:39:49:910    1004    d2c    AU      # WARNING: Failed to find updates with error code 80072EE2
    2016-04-06    05:39:49:910    1004    d2c    AU    #########
    2016-04-06    05:39:49:910    1004    d2c    AU    ##  END  ##  AU: Search for updates [CallId = {E4D3310A-34C1-4D59-BDF6-E700A854108A}]
    2016-04-06    05:39:49:910    1004    d2c    AU    #############
    2016-04-06    05:39:49:910    1004    d2c    AU    Successfully wrote event for AU health state:0
    2016-04-06    05:39:49:910    1004    d2c    AU    AU setting next detection timeout to 2016-04-06 15:39:49
    2016-04-06    05:39:49:910    1004    d2c    AU    Setting AU scheduled install time to 2016-04-10 03:00:00
    2016-04-06    05:39:49:910    1004    d2c    AU    Successfully wrote event for AU health state:0
    2016-04-06    05:39:49:910    1004    d2c    AU    Successfully wrote event for AU health state:0
    2016-04-06    05:39:54:892    1004    13f0    Report    REPORT EVENT: {D201CB55-7442-41E2-AA15-BD1C47EBBC6E}    2016-04-06 05:39:49:895-0500    1    148    101    {00000000-0000-0000-0000-000000000000}    0    80072ee2    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80072ee2.
    2016-04-06    05:39:54:924    1004    13f0    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-04-06    05:39:54:924    1004    13f0    Report    WER Report sent: 7.6.7601.19161 0x80072ee2(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2016-04-06    05:43:13:809    1004    13f0    PT    WARNING: Cached cookie has expired or new PID is available
    2016-04-06    05:43:13:809    1004    13f0    PT    Initializing simple targeting cookie, clientId = 4503ab35-53a6-4451-88d6-0767d6215e25, target group = , DNS name = client.domain.int
    2016-04-06    05:43:13:809    1004    13f0    PT      Server URL = http://192.168.0.168:8530/SimpleAuthWebService/SimpleAuth.asmx
    2016-04-06    05:43:16:137    1004    13f0    Report    Uploading 1 events using cached cookie, reporting URL = http://192.168.0.168:8530/ReportingWebService/ReportingWebService.asmx
    2016-04-06    05:43:16:137    1004    13f0    Report    Reporter successfully uploaded 1 events.

    Wednesday, April 6, 2016 2:04 PM
  • I was checking the application log of my server and found the following error:

    Log Name:      Application
    Source:        ASP.NET 4.0.30319.0
    Date:          4/6/2016 3:43:21 PM
    Event ID:      1309
    Task Category: Web Event
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Blevins37.blevinsinc.int
    Description:
    Event code: 3001
    Event message: The request has been aborted.
    Event time: 4/6/2016 3:43:20 PM
    Event time (UTC): 4/6/2016 8:43:20 PM
    Event ID: 1c670254a08b4280ad03ec16ea17587e
    Event sequence: 1446
    Event occurrence: 3
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/385749604/ROOT/ClientWebService-4-131044127949876971
        Trust level: Full
        Application Virtual Path: /ClientWebService
        Application Path: C:\Program Files\Update Services\WebServices\ClientWebService\
        Machine name: BLEVINS37
     
    Process information:
        Process ID: 12792
        Process name: w3wp.exe
        Account name: NT AUTHORITY\NETWORK SERVICE
     
    Exception information:
        Exception type: HttpException
        Exception message: Request timed out.

     
     
    Request information:
        Request URL: http://192.168.0.168:8530/ClientWebService/client.asmx
        Request path: /ClientWebService/client.asmx
        User host address: 192.168.0.161
        User:  
        Is authenticated: False
        Authentication Type:  
        Thread account name: NT AUTHORITY\NETWORK SERVICE
     
    Thread information:
        Thread ID: 74
        Thread account name: NT AUTHORITY\NETWORK SERVICE
        Is impersonating: False
        Stack trace:
     

    Wednesday, April 6, 2016 9:00 PM
  • Just went through this same issue.  In my case I had existing wsus clients that were fine.  When I tried to add new ones I got the "not yet reported" on the server console and the 80072ee2 error on the clients.  I spent some time thinking this was a client problem since they were new machines I was trying to add.  Turns out it was the wsus server.  I had neglected any maintenance on it for some time.  Run the server cleanup wizard which may bomb out and you will have to do repeatedly.  Eventually this ran overnight for well over 10 hours before finishing. Get rid of any products you don't need. I still had XP, windows 8, vista, etc... on my wsus server patch products list but I don't have any of them anymore.  Run the database maint. script and get rid of superseded updates you no longer need. This all takes a lot of time and effort but eventually once I got it running lean and mean the clients worked just fine.  WSUS does take some continual maintenance to work well and MS could make this a much better product but you get what you pay for (its free after all).  Have a look at this link to point you in the right direction:

    blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/

    Others have simply given up and uninstalled/reinstalled which also presents a host of problems.  This is my second go around for this and I will now do weekly maintenance on wsus so I don't end of wasting a couple days of my time to fix this.  Good luck.

    Thursday, April 7, 2016 1:08 PM
  • Thank you kzoorich, I was thinking something with the server might be up.  I have all my client servers communicating (about 38 out of 40) except for two, and it was just driving me up a wall trying to figure it out.  I'll try this and let you all know if it helped or not.

    Thursday, April 7, 2016 1:58 PM
  • How long did you have to wait till after doing what you did before your clients responded?  I did a wuauclt.exe /detectnow /reportnow on the client and it still hasn't reported anything even if it has contacted the WSUS server. 
    Thursday, April 7, 2016 4:47 PM
  • I do an:

    wuauclt /detectnow

    wuauclt /updatenow

    wuauclt /reportnow

    in that order and I usually wait a minute in between them although it probably doesn't matter.  I didn't see instantaneous results especially on the console.  After 5-10 minutes or so I would check the windowsupdate log on the client.  If the server is OK the 80072ee2 errors would not be there.

    Thursday, April 7, 2016 9:06 PM
  • Unfortunately that did not fix my problem and it is still happening.  Thank you for the update anyway. 
    Friday, April 8, 2016 3:35 PM