Some clients not connecting to WSUS with error Error: 0x80072efd

Discussion in 'Update Services' started by Peggy B., Aug 21, 2006.

  1. Peggy B.

    Peggy B. Guest

    We have 1200 machines at business partners and about 200 of them are not
    connecting to WSUS. Here is errors from the windowsupdate.log are:

    2006-08-21 12:01:07 788 464 Misc WARNING: DownloadFileInternal failed for
    http://Wsus8.usps.gov/selfupdate/wuident.cab: error 0x80072efd
    2006-08-21 12:01:07 788 464 Setup FATAL: IsUpdateRequired failed with error
    0x80072efd
    2006-08-21 12:01:07 788 464 Setup WARNING: SelfUpdate: Default Service:
    IsUpdateRequired failed: 0x80072efd
    2006-08-21 12:01:07 788 464 Setup WARNING: SelfUpdate: Default Service:
    IsUpdateRequired failed, error = 0x80072EFD
    2006-08-21 12:01:07 788 464 Agent * WARNING: Skipping scan, self-update
    check returned 0x80072EFD
    2006-08-21 12:01:08 788 464 Agent * WARNING: Exit code = 0x80072EFD
    2006-08-21 12:01:08 788 464 Agent *********
    2006-08-21 12:01:08 788 464 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2006-08-21 12:01:08 788 464 Agent *************
    2006-08-21 12:01:08 788 464 Agent WARNING: WU client failed Searching for
    update with error 0x80072efd
    2006-08-21 12:01:08 788 464 AU >>## RESUMED ## AU: Search for updates
    [CallId = {958E064D-D359-47EB-90CA-412A666EFFB5}]
    2006-08-21 12:01:08 788 464 AU # WARNING: Search callback failed, result
    = 0x80072EFD
    2006-08-21 12:01:08 788 464 AU #########
    2006-08-21 12:01:08 788 464 AU ## END ## AU: Search for updates [CallId
    = {958E064D-D359-47EB-90CA-412A666EFFB5}]
    2006-08-21 12:01:08 788 464 AU #############
    2006-08-21 12:01:08 788 464 AU AU setting next detection timeout to
    2006-08-22 00:01:08
    2006-08-21 12:01:12 788 464 Report REPORT EVENT:
    {6AA08D5E-6D75-46A0-956F-8724FCFC6A27} 2006-08-21
    12:01:07-0700 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80072efd SelfUpdate Failure Software
    Synchronization Error: Agent failed detecting with reason: 0x80072efd
    2006-08-21 12:07:57 788 328 Misc WARNING: Send failed with hr = 80072efd.
    2006-08-21 12:07:57 788 328 Misc WARNING: SendRequest failed with hr =
    80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
    used : <>
    2006-08-21 12:07:57 788 328 PT + Last proxy send request failed with hr =
    0x80072EFD, HTTP status code = 0
    2006-08-21 12:07:57 788 328 PT + Caller provided credentials = No
    2006-08-21 12:07:57 788 328 PT + Impersonate flags = 0
    2006-08-21 12:07:57 788 328 PT + Possible authorization schemes used =
    2006-08-21 12:07:57 788 328 PT WARNING: GetConfig failure, error =
    0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
    2006-08-21 12:07:57 788 328 Report WARNING: Reporter failed to upload
    events with hr = 80072efd.

    I have done the following troubleshooting:

    1) The machines are getting the correct GPO.
    2) From IE - I can manually connect to the WSUS server by connecting to:
    http://WSUSServerName/selfupdate/AU/x86/XP/EN/wuaucomp.cab (and others
    listed in the troubleshoot)- it prompts me to download so I don't feel like
    it is a firewall issue - plus I have 1000 machines reporting.
    3) ran proxycfg -d then ran a detectnow
    4) ran proxycfg -u then ran a detectnow
    5) deleted the sids and ran wuauclt /resetauthorization /detectnow
    6) stopped SAV, and force detected, did not help.
    7) We manually installed the new client, bits 2.0, windows installer, etc.

    We have the proxy configured in the lan settings and seem to be correct.
    We use DHCP.

    Any suggestions?
     
    Peggy B., Aug 21, 2006
    #1
    1. Advertisements

  2. You've covered everything I can think of off the top of my head.

    The 0x80072efd error is a "Cannot Connect" error, and is almost always
    traced to something in the networking infrastructure that is failing.
    Checking DNS, routing tables, firewalls, proxy servers, proxy client
    configurations are generally the first steps, and the ones that usually
    repair the problem.

    Let me give this some thought.

    If you can provide any additional diagnostics and results, that may also
    help, though I'm not sure at the moment what that would be.

    --
    Lawrence Garvin, M.S., MVP-Software Distribution
    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
    And, everything else is at
    http://wsusinfo.onsitechsolutions.com
    .....
     
    Lawrence Garvin \(MVP\), Aug 21, 2006
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.