+ Proxy list used = proxy:8080 (WindowsUpdate.log)

Discussion in 'Windows Update' started by Claude Lachapelle, May 7, 2009.

  1. I think you missed something important in the WindowsUpdate.log file, just
    before the line you mentioned below:

    WARNING: SendRequest failed with hr = 80072efd. Proxy List used:
    <proxy:8080> Bypass List used : <(null)> Auth Schemes used : <>

    --------------> Proxy List used: <proxy:8080>

    This is the closed bridge, since this server DOES NOT EXIST!

    ;-)

    What I'm trying to find, it is WHERE Automatic Update is getting this
    settings?

    Thanks.
     
    Claude Lachapelle, May 13, 2009
    #21
    1. Advertisements

  2. Brand new server installation (new VMWare virtual machine with the same name,
    new Windows Server 2003 R2 Enterprise 64 bit), SP2 + all Windows update =
    SAME PROBLEM!

    Incredible but true, here the NEW log:

    2009-05-13 17:09:20-0400 808 130 WU client with version 5.7.3790.3959
    successfully initialized
    2009-05-13 17:09:20-0400 808 130 Service status is now SERVICE_RUNNING
    2009-05-13 17:10:05-0400 808 130 start delayed initialization of WU client
    2009-05-13 17:10:05-0400 808 130 BatchFlushAge = 12636.
    2009-05-13 17:10:05-0400 808 130 SamplingValue = 575, sampling required = Yes
    2009-05-13 17:10:05-0400 808 130 Client Call Recorder finished delayed
    initialization
    2009-05-13 17:10:05-0400 808 130 Setting next AU detection timeout to
    2009-05-13 21:10:05
    2009-05-13 17:10:05-0400 808 130 AU finished delayed initialization
    2009-05-13 17:10:05-0400 808 130 AU received event of type: 1
    2009-05-13 17:10:05-0400 808 130 WU client succeeds
    CClientCallRecorder::BeginFindUpdatesEx from AutomaticUpdates with call id
    {DE11318B-BA3E-4E3B-A85E-9985297CA773}
    2009-05-13 17:10:05-0400 808 350 WU client executing call
    {DE11318B-BA3E-4E3B-A85E-9985297CA773} of type Search Call
    2009-05-13 17:10:19-0400 808 350 SendRequest failed with hr = 80072efd.
    Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth Schemes used :
    <>
    2009-05-13 17:10:19-0400 808 350 WinHttp: SendRequestUsingProxy failed for
    <http://wsus01.domain.com/SelfUpdate/wuident.cab>. error 0x80072efd
    2009-05-13 17:10:19-0400 808 350 WinHttp:
    SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
    2009-05-13 17:10:19-0400 808 350 WinHttp:
    SendRequestToServerForFileInformation failed with 0x80072efd
    2009-05-13 17:10:19-0400 808 350 WinHttp: ShouldFileBeDownloaded failed
    with 0x80072efd
    2009-05-13 17:10:28-0400 1684 698 CreateObject for
    Microsoft.Update.AgentInfo failed: error 0x800401f3
    2009-05-13 17:10:28-0400 808 3ac WU client succeeds
    CClientCallRecorder::EnumerateService

    Wow... now I'll try changing network settings (new VMWare network - another
    VLAN where other servers are functionning properly). I will let you know!

    Thanks.
     
    Claude Lachapelle, May 13, 2009
    #22
    1. Advertisements

  3. No, I didn't miss anything at all. the 0x80072efd error is a CANNOT CONNECT
    error,
    and the reason why hasn't changed a bit -- the network pathway is blocked.
    But, previously, we were focusing on the "Proxy" entry itself, and the
    0x80070002 error in the CDT. Those may or may not be misleading items of
    information. What's significant is that the client can't talk to the server,
    and that spells N E T W O R K F A U L T -- whereever it happens to be.

    Until you find out WHY that machine cannot communicate with the WSUS Server
    (or even if it can communicate with *anything* outside of the VMWare Host
    machine), building a new server isn't likely to do anything except waste
    time -- the most significant risk is your "new" server will get this same
    configuration data from wherever this server is getting it now, and you will
    have accomplished nothing of significance.

    The CORRECT procedure is to identify the CAUSE of the issue, and then repair
    the CAUSE.

    Yes.. we all understand there's no physical proxy server installed. That's
    not the problem. The problem is that *something* is feeding *configuration
    data* to your virtual machine - you need to find out what that is. Actually,
    you should already know what that is. In a message dated yesterday morning
    you stated, in regards to the alleged proxy server -- "This server already
    existed in the company, but it is not used any more (it have been
    decomissionned)" -- so you already have the answer to that question. What
    was done when that server existed to tell the clients to use that server.
    I'll bet dollars-to-donuts that decommissioning the server isn't enough, and
    something else still needs to be "unconfigured".

    Exactly -- that's what you need to do -- but we're not going to be able to
    give you that answer in this forum. It's *NOT* the WSUS Server providing
    that information. You used to have a proxy server; now, apparently, you do
    not, but this machine thinks it's still there -- that's because *something*
    is telling this machine to use the proxy server. You need to find out what
    that is. Once you do, your problem will be solved. Until you do -- it's
    highly unlikely any machine is going to be able to successfully
    detect/install updates from the WSUS Server.


    --
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], May 13, 2009
    #23
  4. My best guess at this point is that this is proxy autodetection. Is there an
    entry for wpad in your DNS?

    Could you check the contents of the Connections key again? Is the first byte
    still 28 instead of 18? If so, I'm guessing autodetection is being enabled by
    group policy. You may or may not want to turn this policy setting off, but
    you'll definitely want to remove the wpad DNS entry if it is indeed present.

    Harry.
     
    Harry Johnston [MVP], May 13, 2009
    #24
  5. Imagine that! :)


    --
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], May 13, 2009
    #25
  6. You were right!

    As soon as I changed the network VLAN, the problem goes away.

    Now since this setting is not coming from of the DHCP server, I transferred
    this case to the network team.

    NOTE: This is solving another problem at the same time, a lot of
    workstations were having difficulties to connect to the Internet -- IE is
    configured by default to "Autodetect" network settings...

    Thanks, your help was very appreciated!!!
     
    Claude Lachapelle, May 14, 2009
    #26
  7. Finally that was related to the "Automatically detect settings" of Internet
    Explorer, since when I change the server VLAN to another, it is working
    correctly.

    Now I have to find out which device is providing wrong WPAD configuration.
    This is not the DNS neither the DHCP. Now, how I could query and find which
    device which is giving this information? Next step...

    Thanks a lot for your help!
     
    Claude Lachapelle, May 14, 2009
    #27
  8. Beats the heck out of me then. I thought DNS was the only way this could happen.
    I'd suggest you start by seeing if you can reproduce the same issue in IE. That
    is, on a machine on the affected VLAN, configure IE to autodetect proxy settings
    and see if it tries to use the old proxy.

    If this does happen, then the IE newsgroup is probably your best next stop.
    You're most welcome.

    Harry.
     
    Harry Johnston [MVP], May 14, 2009
    #28
    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.