none
80072efd error with no proxy or filewall in the way

    Question

  • Hi all,

    I am stumped here. I looked all over and found a lot of information, however none of it helped me.

    We are using System Center Essential 2010 and using WSUS within that to push out updates.

    We had this running for the last year without issues, however within the last week, we've noticed the 80072efd errors and clients are no longer connecting to WSUS.

    I saw issues out there related to Proxys, however we do not use, nor ever used a proxy.

    I also saw issues regarding firewall's blocking the updates to run, however windows firewall is off on the clients.

    There have not been any DNS changes within the last 6 months, (we added new DNS Servers 6 months ago, and there were no issues at that time)

    Here is a snippet of a log from one of the clients, but I am sure you all saw these before:

    2012-07-09    12:14:51:326     400    ecc    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-07-09    12:14:51:326     400    ecc    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://SCESERVER:8531/ClientWebService/client.asmx
    2012-07-09    12:14:51:354     400    ecc    PT    WARNING: Cached cookie has expired or new PID is available
    2012-07-09    12:14:51:354     400    ecc    PT    Initializing simple targeting cookie, clientId = 95b10e4f-1122-462c-8eb8-f8a9ce7c4d03, target group = , DNS name = CLIENTPC
    2012-07-09    12:14:51:354     400    ecc    PT      Server URL = https://SCESERVER:8531/SimpleAuthWebService/SimpleAuth.asmx
    2012-07-09    12:14:53:682     400    ecc    Misc    WARNING: Send failed with hr = 80072efd.
    2012-07-09    12:14:53:682     400    ecc    Misc    WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2012-07-09    12:14:53:682     400    ecc    PT      + Last proxy send request failed with hr = 0x80072EFD, HTTP status code = 0
    2012-07-09    12:14:53:682     400    ecc    PT      + Caller provided credentials = No
    2012-07-09    12:14:53:682     400    ecc    PT      + Impersonate flags = 0
    2012-07-09    12:14:53:682     400    ecc    PT      + Possible authorization schemes used =
    2012-07-09    12:14:53:683     400    ecc    PT    WARNING: GetAuthorizationCookie failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
    2012-07-09    12:14:53:683     400    ecc    PT    WARNING: Failed to initialize Simple Targeting Cookie: 0x80072efd
    2012-07-09    12:14:53:683     400    ecc    PT    WARNING: PopulateAuthCookies failed: 0x80072efd
    2012-07-09    12:14:53:683     400    ecc    PT    WARNING: RefreshCookie failed: 0x80072efd
    2012-07-09    12:14:53:683     400    ecc    PT    WARNING: RefreshPTState failed: 0x80072efd
    2012-07-09    12:14:53:683     400    ecc    PT    WARNING: Sync of Updates: 0x80072efd
    2012-07-09    12:14:53:683     400    ecc    PT    WARNING: SyncServerUpdatesInternal failed: 0x80072efd
    2012-07-09    12:14:53:683     400    ecc    Agent      * WARNING: Failed to synchronize, error = 0x80072EFD
    2012-07-09    12:14:53:685     400    ecc    Agent      * WARNING: Exit code = 0x80072EFD
    2012-07-09    12:14:53:685     400    ecc    Agent    *********
    2012-07-09    12:14:53:685     400    ecc    Agent    **  END  **  Agent: Finding updates [CallerId = ]
    2012-07-09    12:14:53:685     400    ecc    Agent    *************

    ClientPC and SCEServer are not the real names

    Also within the SCEServer using WSUS under Admin Tools All clients show they have not connected to the server in 10 days. So I am sure there is a connection issue some where but why and how I am not sure.

    Let me know if there are any ideas out there.


    • Edited by JCrescenzo Monday, July 09, 2012 5:35 PM added info
    Monday, July 09, 2012 5:11 PM

Answers

  • 2012-07-09    12:14:51:354     400    ecc    PT      Server URL = https://SCESERVER:8531/SimpleAuthWebService/SimpleAuth.asmx
    2012-07-09    12:14:53:682     400    ecc    Misc    WARNING: Send failed with hr = 80072efd.

    Simply stated.... there's no functioning WSUS server at https://SCESERVER:8531. In fact, there's no functioning WEB server at that URL. -- or so this client thinks.

    The 0x80072EFD error code is logged by the Windows Update Agent when it fails to get a valid HTTP result code from the web server it attempted to contact at the specified URL. This could be caused by a number of infrastructure defects, including DNS faults, routing errors, or proxy configuration. Given that we're dealing with the alternate v-root and SSL, that would be two additional possible failure points -- but since this WAS working, and now is NOT -- we should look to what changes were made that would have impacted connectivity.

    Since you know when the last successful connection was made (both from client logs as well as sorting All Computers on the Last Contact Time), it should be fairly easy to identify a very narrow timeframe in which the connectivity failed. My money would be on updates applied to the WSUS server -- say, maybe, KB2720211?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    • Marked as answer by JCrescenzo Monday, July 09, 2012 8:04 PM
    • Unmarked as answer by JCrescenzo Monday, July 09, 2012 8:04 PM
    • Marked as answer by JCrescenzo Monday, July 09, 2012 8:04 PM
    Monday, July 09, 2012 7:56 PM

All replies

  • 2012-07-09    12:14:51:354     400    ecc    PT      Server URL = https://SCESERVER:8531/SimpleAuthWebService/SimpleAuth.asmx
    2012-07-09    12:14:53:682     400    ecc    Misc    WARNING: Send failed with hr = 80072efd.

    Simply stated.... there's no functioning WSUS server at https://SCESERVER:8531. In fact, there's no functioning WEB server at that URL. -- or so this client thinks.

    The 0x80072EFD error code is logged by the Windows Update Agent when it fails to get a valid HTTP result code from the web server it attempted to contact at the specified URL. This could be caused by a number of infrastructure defects, including DNS faults, routing errors, or proxy configuration. Given that we're dealing with the alternate v-root and SSL, that would be two additional possible failure points -- but since this WAS working, and now is NOT -- we should look to what changes were made that would have impacted connectivity.

    Since you know when the last successful connection was made (both from client logs as well as sorting All Computers on the Last Contact Time), it should be fairly easy to identify a very narrow timeframe in which the connectivity failed. My money would be on updates applied to the WSUS server -- say, maybe, KB2720211?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    • Marked as answer by JCrescenzo Monday, July 09, 2012 8:04 PM
    • Unmarked as answer by JCrescenzo Monday, July 09, 2012 8:04 PM
    • Marked as answer by JCrescenzo Monday, July 09, 2012 8:04 PM
    Monday, July 09, 2012 7:56 PM
  • Hi Lawrence,

    I was testing some more after I posted this and noticed that I can't can't even get to the server via the URL.

    Something has me thinking something got messed up on the server, but it seems like it may be one of those games that it's harder to find what is wrong than how it fix it.

    Thank you. I am going to close this and super worse case, redo the whole process. but I will put that on the back burner for now.
    Monday, July 09, 2012 8:04 PM