none
WSUS Server Not Updating itself

    Question

  • Hi

    I have a strange problem with my WSUS server. All clients are able to report in and update except for the WSUS server itself. It hasn't reported in for a few months and I can't figure out why. Below is s snippet of the WindowsUpdate.log file:

     

     + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://sbs2003:8530/ClientWebService/client.asmx
    2013-08-30 09:08:21:593  984 4a54 PT WARNING: Cached cookie has expired or new PID is available
    2013-08-30 09:08:21:593  984 4a54 PT Initializing simple targeting cookie, clientId = c4841869-a30e-411f-9609-a4332ae80a3f, target group = Servers, DNS name = Server-sbs01.domain.local
    2013-08-30 09:08:21:594  984 4a54 PT   Server URL = http://sbs2003:8530/SimpleAuthWebService/SimpleAuth.asmx
    2013-08-30 09:08:45:207  984 4a54 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <10.0.0.2:8080> Bypass List used : <> Auth Schemes used : <>
    2013-08-30 09:08:45:207  984 4a54 PT   + Last proxy send request failed with hr = 0x80072EFE, HTTP status code = 0
    2013-08-30 09:08:45:207  984 4a54 PT   + Caller provided proxy = Yes
    2013-08-30 09:08:45:207  984 4a54 PT   + Proxy list used = 10.0.0.2:8080
    2013-08-30 09:08:45:207  984 4a54 PT   + Bypass list used =
    2013-08-30 09:08:45:207  984 4a54 PT   + Caller provided credentials = No
    2013-08-30 09:08:45:207  984 4a54 PT   + Impersonate flags = 0
    2013-08-30 09:08:45:207  984 4a54 PT   + Possible authorization schemes used =
    2013-08-30 09:08:45:207  984 4a54 PT WARNING: GetCookie failure, error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP status code = 200
    2013-08-30 09:08:45:207  984 4a54 PT WARNING: PTError: 0x80072efe
    2013-08-30 09:08:45:207  984 4a54 PT WARNING: GetCookie_WithRecovery failed : 0x80072efe
    2013-08-30 09:08:45:207  984 4a54 PT WARNING: RefreshCookie failed: 0x80072efe
    2013-08-30 09:08:45:207  984 4a54 PT WARNING: RefreshPTState failed: 0x80072efe
    2013-08-30 09:08:45:208  984 4a54 PT WARNING: Sync of Updates: 0x80072efe
    2013-08-30 09:08:45:208  984 4a54 PT WARNING: SyncServerUpdatesInternal failed: 0x80072efe
    2013-08-30 09:08:45:208  984 4a54 Agent   * WARNING: Failed to synchronize, error = 0x80072EFE
    2013-08-30 09:08:45:208  984 4a54 Agent   * WARNING: Exit code = 0x80072EFE

     

    I noticed in the log that it lists a proxy - 10.0.0.2 however it isn't (or at least shouldn't) be using a proxy. I also saw the error that the cookie has expired or a new PID is available. What does that mean?

    I have tried the WSUS Client Util but I just get the results below:

    WSUS Client Diagnostics Tool

    Checking Machine State
            Checking for admin rights to run tool . . . . . . . . . PASS
            Automatic Updates Service is running. . . . . . . . . . PASS
            Background Intelligent Transfer Service is running. . . PASS

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    The system cannot find the file specified.

    Any help would be greatly appreciated.

    Friday, August 30, 2013 12:08 AM

Answers

All replies

  • Hi,

    For the 0x80070002, we could start here:

    You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services

    http://support.microsoft.com/default.aspx/kb/910336

    Hope this helps.

    Regards,

    Yan Li


    Cataleya Li
    TechNet Community Support

    Friday, August 30, 2013 2:54 AM
    Moderator
  • Thanks Cataleya, I had already tried that one but it didn't help. I did find what the issue was though - mismatched versions between WSUS and the update client. I installed the update below and now the server is checking in:

    http://support.microsoft.com/kb/2720211/en-au

    Thanks again

    Friday, August 30, 2013 2:58 AM
  • 2013-08-30 09:08:45:207  984 4a54 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <10.0.0.2:8080>

    As you've observed, the proxy configuration is problematic.

    Error 0x80072EFE is an INTERNET_CONNECTION_ABORTED condition; likely caused by an invalid proxy configuration.

    Run netsh winhttp reset proxy to fix that.

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    The WSUS Client Diagnostic Tool is a 32-bit only tool and does not work on 64-bit systems. For 64-bit systems (actually for all systems given the age of the Microsoft CDT), I invite you to try the SolarWinds Diagnostic Tool for the WSUS Agent.

    One useful advantage of the SolarWinds tool in this scenario is that it does not use the WinHTTP proxy configuration for testing. It has its own internal proxy configuration, which allows you to explore "what if" scenarios with the proxy configuration and determine the correct proxy configuration to use. (Which, for a WSUS server talking to itself is NO PROXY.)


    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.

    Saturday, August 31, 2013 2:02 AM
    Moderator
  • For the 0x80070002, we could start here:

    You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services

    Not applicable in this case. The O.P. is getting this error because he's attempting to run a 32-bit tool on a 64-bit system.

    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.

    Saturday, August 31, 2013 2:03 AM
    Moderator
  • mismatched versions between WSUS and the update client. I installed the update below and now the server is checking in:

    http://support.microsoft.com/kb/2720211/en-au

    While failing to install the required patches to WSUS would certainly be problematic with respect to the WUAgent and WSUS communication, I have never seen that issue manifest as an 0x80072EFE error.

    The expected error for a missing KB2720211 patch is an 0x800B0001.

    The incorrect proxy configuration is much more consistent with the 0x80072EFE error code.

    Also, of note, since this seems to be an SBS installation (I'm inferring from the hostname in the WSUS URL, it should also be noted that a common cause of the SBS Server being unable to communicate with the WSUS services is the GPO not being linked to the Domain Controllers OU. Not the case in this scenario, but potentially relevant information for future readers of this thread.


    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.

    Saturday, August 31, 2013 2:06 AM
    Moderator