none
Error Code 80072EFD

    Question

  • We have a number of servers that have stopped registering with our WSUS Server. When I try to run a manual update on the server I get this error

    We also have servers that have disappeared from the console altogether.

    mardi 4 décembre 2012 10:02

Réponses

  • I've resolved the problem thanks to the diagnostic tool you suggested. It indicated that clients in one OU were still poined to our old WSUS server a bit more digging in group policy and I found the GPO that still had the old server as a setting

    Thanks for the help !

    mardi 4 décembre 2012 15:19

Toutes les réponses

  • 0x80072EFD -2147012867 ERROR_INTERNET_CANNOT_CONNECT  The attempt to connect to the server failed.

    I can't see the image, but, if the client does not regularly maintain communication with the WSUS, it will disappear from the console if you are performing routine maintenance tasks on your WSUS.

    Check the client windowsupdate.log file, to determine the health of the WUA on the client machine. Confirm connectivity to the WSUS is uninterrupted.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    mardi 4 décembre 2012 10:15
  • The error I get is

    Windows could not search for new updates

    An error occured while checking for new updates for your computer

    Code 80072EFD

    The log file for the latest attempt at running the update is

    2012-12-04    10:21:27:870     300    34c    Misc    WARNING: Send failed with hr = 80072efd.
    2012-12-04    10:21:27:870     300    34c    Misc    WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2012-12-04    10:21:27:870     300    34c    PT      + Last proxy send request failed with hr = 0x80072EFD, HTTP status code = 0
    2012-12-04    10:21:27:870     300    34c    PT      + Caller provided credentials = No
    2012-12-04    10:21:27:870     300    34c    PT      + Impersonate flags = 0
    2012-12-04    10:21:27:870     300    34c    PT      + Possible authorization schemes used =
    2012-12-04    10:21:27:870     300    34c    PT    WARNING: GetConfig failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
    2012-12-04    10:21:27:870     300    34c    PT    WARNING: PTError: 0x80072efd
    2012-12-04    10:21:27:870     300    34c    PT    WARNING: GetConfig_WithRecovery failed: 0x80072efd
    2012-12-04    10:21:27:870     300    34c    PT    WARNING: RefreshConfig failed: 0x80072efd
    2012-12-04    10:21:27:870     300    34c    PT    WARNING: RefreshPTState failed: 0x80072efd
    2012-12-04    10:21:27:870     300    34c    PT    WARNING: PTError: 0x80072efd
    2012-12-04    10:21:27:870     300    34c    Report    WARNING: Reporter failed to upload events with hr = 80072efd.

    mardi 4 décembre 2012 10:29
  • if you look earlier in the logfile, you may find the WSUS server configured is incorrect?

    you can check the client with the diagnostic tool:
    Download the FREE SolarWinds Diagnostic Tool for the WSUS Agent, export the results to TEXT, and post them.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    mardi 4 décembre 2012 11:00
  • I've resolved the problem thanks to the diagnostic tool you suggested. It indicated that clients in one OU were still poined to our old WSUS server a bit more digging in group policy and I found the GPO that still had the old server as a setting

    Thanks for the help !

    mardi 4 décembre 2012 15:19