locked
Error 80072efd when connecting to WSUS server RRS feed

  • Question

  • I am trying to install updates using a WSUS server and am getting a 80072efd error. I am sure this is a client configuration issue but I can't seem to find it.  I understand that this is an error that says essentially that it cannot access the server and have read the various articles including all trying all of the steps in KB836941 and posts but can't seem to find the root cause of this error. The following is the relevant information

    Any help would be greatly appreciated.

    1. Problem only occurs with W2008R2 and W2008 physical servers (probably something in our image configuration). Our Virtual Servers seem to be fine.
    2. Access is to an internal WSUS server, however you get the same error if you try and download from Microsoft.
    3. No firewall is turned on the server and no firewall in between server and WSUS server
    4. Browsing works fine from the server. You can browse to Microsoft (and all other sites) and I could even browse to one of the Microsoft .CAB files that were referenced in the log (and it allowed me to download it).
    5. AntiVirus is disabled
    6. The WSUS server is working fine with other servers  
    7. There is no WinHttp proxy

    A snippet of the log file is posted below

    Service ** START **  Service: Service startup
    2012-05-31 13:32:03:922  940 1650 Service *********
    2012-05-31 13:32:04:032  940 1650 Agent   * WU client version 7.1.6001.65
    2012-05-31 13:32:04:032  940 1650 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2012-05-31 13:32:04:125  940 1650 Agent   * Access type: No proxy
    2012-05-31 13:32:04:265  940 1650 Agent   * Network state: Connected
    2012-05-31 13:32:49:521  940 1650 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2012-05-31 13:32:49:521  940 1650 Agent ***********  Agent: Initializing global settings cache  ***********
    2012-05-31 13:32:49:521  940 1650 Agent   * WSUS server: http://mdc-wsus.na.abc.com:8530
    2012-05-31 13:32:49:521  940 1650 Agent   * WSUS status server: http://mdc-wsus.na.abc.com:8530
    2012-05-31 13:32:49:521  940 1650 Agent   * Target group: (Unassigned Computers)
    2012-05-31 13:32:49:521  940 1650 Agent   * Windows Update access disabled: No
    2012-05-31 13:32:49:537  940 1650 DnldMgr Download manager restoring 0 downloads
    2012-05-31 13:32:49:553  940 1650 AU ###########  AU: Initializing Automatic Updates  ###########
    2012-05-31 13:32:49:568  940 1650 AU   # WSUS server: http://mdc-wsus.na.abc.com:8530
    2012-05-31 13:32:49:568  940 1650 AU   # Detection frequency: 12
    2012-05-31 13:32:49:568  940 1650 AU   # Approval type: Scheduled (User preference)
    2012-05-31 13:32:49:568  940 1650 AU   # Scheduled install day/time: Every day at 3:00
    2012-05-31 13:32:49:568  940 1650 AU   # Auto-install minor updates: Yes (User preference)
    2012-05-31 13:32:49:568  940 1650 AU   # Auto update required (cannot be disabled)
    2012-05-31 13:32:49:568  940 1650 AU Setting AU scheduled install time to 2012-06-01 08:00:00
    2012-05-31 13:32:49:568  940 1650 AU AU setting pending client directive to 'Unable To Detect'
    2012-05-31 13:32:49:568  940 1650 AU AU finished delayed initialization
    2012-05-31 13:32:49:709  940 1650 Report ***********  Report: Initializing static reporting data  ***********
    2012-05-31 13:32:49:709  940 1650 Report   * OS Version = 6.0.6002.2.0.196882
    2012-05-31 13:32:49:709  940 1650 Report   * OS Product Type = 0x0000000A
    2012-05-31 13:32:49:740  940 1650 Report   * Computer Brand = HP
    2012-05-31 13:32:49:740  940 1650 Report   * Computer Model = ProLiant BL460c G7
    2012-05-31 13:32:49:740  940 1650 Report   * Bios Revision = I27
    2012-05-31 13:32:49:740  940 1650 Report   * Bios Name = Default System BIOS
    2012-05-31 13:32:49:740  940 1650 Report   * Bios Release Date = 2011-05-05T00:00:00
    2012-05-31 13:32:49:740  940 1650 Report   * Locale ID = 1033
    2012-05-31 13:33:04:565  940 1650 AU WARNING: AU found no suitable session to launch client in
    2012-05-31 13:33:15:634  940 16d4 Misc WARNING: Send failed with hr = 80072efd.
    2012-05-31 13:33:15:634  940 16d4 Misc WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2012-05-31 13:33:15:634  940 16d4 PT   + Last proxy send request failed with hr = 0x80072EFD, HTTP status code = 0
    2012-05-31 13:33:15:634  940 16d4 PT   + Caller provided credentials = No
    2012-05-31 13:33:15:634  940 16d4 PT   + Impersonate flags = 0
    2012-05-31 13:33:15:634  940 16d4 PT   + Possible authorization schemes used

    2012-05-31 13:33:15:634  940 16d4 PT WARNING: GetConfig failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
    2012-05-31 13:33:15:634  940 16d4 PT WARNING: PTError: 0x80072efd
    2012-05-31 13:33:15:634  940 16d4 PT WARNING: GetConfig_WithRecovery failed: 0x80072efd
    2012-05-31 13:33:15:634  940 16d4 PT WARNING: RefreshConfig failed: 0x80072efd
    2012-05-31 13:33:15:634  940 16d4 PT WARNING: RefreshPTState failed: 0x80072efd
    2012-05-31 13:33:15:634  940 16d4 PT WARNING: PTError: 0x80072efd
    2012-05-31 13:33:15:634  940 16d4 Report WARNING: Reporter failed to upload events with hr = 80072efd.
    2012-05-31 13:33:41:200  940 16d4 Misc WARNING: Send failed with hr = 80072efd.
    2012-05-31 13:33:41:200  940 16d4 Misc WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2012-05-31 13:33:41:200  940 16d4 PT   + Last proxy send request failed with hr = 0x80072EFD, HTTP status code = 0
    2012-05-31 13:33:41:200  940 16d4 PT   + Caller provided credentials = No
    2012-05-31 13:33:41:200  940 16d4 PT   + Impersonate flags = 0
    2012-05-31 13:33:41:200  940 16d4 PT   + Possible authorization schemes used =
    2012-05-31 13:33:41:200  940 16d4 PT WARNING: GetConfig failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
    2012-05-31 13:33:41:200  940 16d4 PT WARNING: PTError: 0x80072efd
    2012-05-31 13:33:41:200  940 16d4 PT WARNING: GetConfig_WithRecovery failed: 0x80072efd
    2012-05-31 13:33:41:200  940 16d4 PT WARNING: RefreshConfig failed: 0x80072efd
    2012-05-31 13:33:41:200  940 16d4 PT WARNING: RefreshPTState failed: 0x80072efd
    2012-05-31 13:33:41:200  940 16d4 PT WARNING: PTError: 0x80072efd
    2012-05-31 13:33:41:200  940 16d4 Report WARNING: Reporter failed to upload events with hr = 80072efd.
    2012-05-31 13:34:06:783  940 16d4 Misc WARNING: Send failed with hr = 80072efd.
    2012-05-31 13:34:06:783  940 16d4 Misc WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2012-05-31 13:34:06:783  940 16d4 PT   + Last proxy send request failed with hr = 0x80072EFD, HTTP status code = 0
    2012-05-31 13:34:06:783  940 16d4 PT   + Caller provided credentials = No
    2012-05-31 13:34:06:783  940 16d4 PT   + Impersonate flags = 0
    2012-05-31 13:34:06:783  940 16d4 PT   + Possible authorization schemes used =
    2012-05-31 13:34:06:783  940 16d4 PT WARNING: GetConfig failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
    2012-05-31 13:34:06:783  940 16d4 PT WARNING: PTError: 0x80072efd
    2012-05-31 13:34:06:783  940 16d4 PT WARNING: GetConfig_WithRecovery failed: 0x80072efd
    2012-05-31 13:34:06:783  940 16d4 PT WARNING: RefreshConfig failed: 0x80072efd
    2012-05-31 13:34:06:783  940 16d4 PT WARNING: RefreshPTState failed: 0x80072efd
    2012-05-31 13:34:06:783  940 16d4 PT WARNING: PTError: 0x80072efd
    2012-05-31 13:34:06:783  940 16d4 Report WARNING: Reporter failed to upload events with hr = 80072efd.
    2012-05-31 13:35:05:461  940 1650 AU Launched new AU client for directive 'Unable To Detect', session id = 0x2
    2012-05-31 13:35:05:492 1156 1568 Misc ===========  Logging initialized (build: 7.1.6001.65, tz: -0500)  ===========
    2012-05-31 13:35:05:492 1156 1568 Misc   = Process: C:\Windows\system32\wuauclt.exe
    2012-05-31 13:35:05:492 1156 1568 AUClnt Launched Client UI process
    2012-05-31 13:35:05:602 1156 1568 Misc ===========  Logging initialized (build: 7.1.6001.65, tz: -0500)  ===========
    2012-05-31 13:35:05:602 1156 1568 Misc   = Process: C:\Windows\system32\wuauclt.exe
    2012-05-31 13:35:05:602 1156 1568 Misc   = Module: C:\Windows\system32\wucltux.dll
    2012-05-31 13:35:05:602 1156 1568 CltUI AU client got new directive = 'Unable To Detect', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0
    2012-05-31 13:35:05:617 1156 1568 AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x80070002)
    2012-05-31 13:35:05:617 1156 1568 AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x80070002)
    2012-05-31 13:35:05:617 1156 1568 AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x80070002)
    2012-05-31 13:35:05:617 1156 1568 AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x80070002)
    2012-05-31 13:35:05:617  940 1650 AU AU received handle event
    2012-05-31 13:35:05:617  940 1650 AU AU setting pending client directive to 'Unable To Detect'
    2012-05-31 13:35:20:621  940 1650 AU Launched new AU client for directive 'Unable To Detect', session id = 0x2
    2012-05-31 13:35:20:636 5980 1778 Misc ===========  Logging initialized (build: 7.1.6001.65, tz: -0500)  ===========
    2012-05-31 13:35:20:636 5980 1778 Misc   = Process: C:\Windows\system32\wuauclt.exe
    2012-05-31 13:35:20:636 5980 1778 AUClnt Launched Client UI process
    2012-05-31 13:35:20:668 5980 1778 Misc ===========  Logging initialized (build: 7.1.6001.65, tz: -0500)  ===========
    2012-05-31 13:35:20:668 5980 1778 Misc   = Process: C:\Windows\system32\wuauclt.exe
    2012-05-31 13:35:20:668 5980 1778 Misc   = Module: C:\Windows\system32\wucltux.dll
    2012-05-31 13:35:20:668 5980 1778 CltUI AU client got new directive = 'Unable To Detect', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0


    Roger

    Friday, June 1, 2012 7:59 PM

Answers

  • I am trying to install updates using a WSUS server and am getting a 80072efd error. I am sure this is a client configuration issue.

    Actually, it's typically a networkconfiguration issue, but could be implemented on the client, on the WSUS server, or at any device in between.

    I understand that this is an error that says essentially that it cannot access the server

    More specifically that it cannot CONNECT to the server, meaning, in this case, that the client cannot traverse the network to get to mdc-wsus.na.abc.com<machinename></machinename>. A number of typical causes for this error are:

    • The hostname provided does not exist.
    • The hostname configured is not properly registered in DNS.
    • The client cannot communicate with a DNS server to resolve the hostname.
    • The IP Address returned from DNS is not valid.
    • The IP Address returned from DNS does not have a web server configured.
    • The IP Address returned from DNS does not have a valid network pathway from this client.
    • The WSUS server is not installed on port 8530.
    • A proxy server is required to access the WSUS server, and the client is not configured to use it.
    • The client is configured to use a proxy server that does not exist.
    • The client is configured to use a proxy server that cannot get to the WSUS server (and is returning the wrong error codes).

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


    Saturday, June 2, 2012 5:26 PM

All replies

  • I am trying to install updates using a WSUS server and am getting a 80072efd error. I am sure this is a client configuration issue.

    Actually, it's typically a networkconfiguration issue, but could be implemented on the client, on the WSUS server, or at any device in between.

    I understand that this is an error that says essentially that it cannot access the server

    More specifically that it cannot CONNECT to the server, meaning, in this case, that the client cannot traverse the network to get to mdc-wsus.na.abc.com<machinename></machinename>. A number of typical causes for this error are:

    • The hostname provided does not exist.
    • The hostname configured is not properly registered in DNS.
    • The client cannot communicate with a DNS server to resolve the hostname.
    • The IP Address returned from DNS is not valid.
    • The IP Address returned from DNS does not have a web server configured.
    • The IP Address returned from DNS does not have a valid network pathway from this client.
    • The WSUS server is not installed on port 8530.
    • A proxy server is required to access the WSUS server, and the client is not configured to use it.
    • The client is configured to use a proxy server that does not exist.
    • The client is configured to use a proxy server that cannot get to the WSUS server (and is returning the wrong error codes).

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


    Saturday, June 2, 2012 5:26 PM
  • After going through the list twice, I found it. It was in fact a client configuration problem and turned out to be a DNS problem. For some strange reason, some server(s) had a Host file which had the WSUS server name in it and it was configured to an old WSUS server. The result was the server was not able to connect to the WSUS server.

    Simply deleted the hosts file and all is well.

    Thanks.


    Roger


    Monday, June 4, 2012 9:09 PM
  • I am trying to install updates using a WSUS server and am getting a 80072efd error. I am sure this is a client configuration issue.

    Actually, it's typically a networkconfiguration issue, but could be implemented on the client, on the WSUS server, or at any device in between.

    I understand that this is an error that says essentially that it cannot access the server

    More specifically that it cannot CONNECT to the server, meaning, in this case, that the client cannot traverse the network to get to mdc-wsus.na.abc.com<machinename></machinename>. A number of typical causes for this error are:

    • The hostname provided does not exist.
    • The hostname configured is not properly registered in DNS.
    • The client cannot communicate with a DNS server to resolve the hostname.
    • The IP Address returned from DNS is not valid.
    • The IP Address returned from DNS does not have a web server configured.
    • The IP Address returned from DNS does not have a valid network pathway from this client.
    • The WSUS server is not installed on port 8530.
    • A proxy server is required to access the WSUS server, and the client is not configured to use it.
    • The client is configured to use a proxy server that does not exist.
    • The client is configured to use a proxy server that cannot get to the WSUS server (and is returning the wrong error codes).

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


    What if it's none of these? 

    I am on a client right now that continues to get this error. I can successfully ping the server by name. I found the old server name in the registry and actually manually entered the new server name but still get this error. I deleted the 2 keys with the wrong server name and ran gpupdate/force but the old server name came back. (That is why I manually entered the correct server name.)  I also ran the Windows Update Diagnostic tool which *said* it repaired service registration and problems installing updates but did not fix the error.

    Any other guesses? I have seen many other *so-called* answers, none of which were actually applicable to my set up. 

    Thursday, September 1, 2016 5:21 PM