Same proxy but WU does work on one server but does not on the othe

Discussion in 'Windows Update' started by The Prutser, Jun 9, 2006.

  1. The Prutser

    The Prutser Guest

    Hi,

    I am experiencing a rather peculiar windows update problem.
    * When I use WU to update SVR01 through a proxy server I get the error:
    Error number: 0x80244021
    * When I use WU to update SVR02 through the same proxy server all goes well.

    Both servers are:
    * ....running Windows 2000 Adv Server SP4
    * ....cluster nodes (different cluster)
    * ....using same proxy server (ISA Server 2000)
    * ....member of same domain

    Things I tried for SVR01 but without result:
    * re-register wu DLL's
    * installed IE6.0 SP1 roll up package (KB 871260)
    * configured ISA 2000 for specific WU use

    Anybody any ideas on this issue?

    In forward thanx!

    windowsupdate.log since last try for SVR01:
    2006-06-09 10:09:30 2556 a04 Misc =========== Logging initialized (build:
    5.8.0.2469, tz: +0200) ===========
    2006-06-09 10:09:30 2556 a04 Misc = Process: C:\Program Files\Internet
    Explorer\iexplore.exe
    2006-06-09 10:09:30 2556 a04 Misc = Module: C:\WINNT\system32\wuapi.dll
    2006-06-09 10:09:30 2556 a04 COMAPI ----------- COMAPI:
    IUpdateServiceManager::AddService -----------
    2006-06-09 10:09:30 2556 a04 COMAPI - ServiceId =
    {7971f918-a847-4430-9279-4a52d1efe18d}
    2006-06-09 10:09:30 2556 a04 COMAPI - AuthorizationCabPath =
    C:\WINNT\SoftwareDistribution\AuthCabs\muauth.cab
    2006-06-09 10:09:30 1620 7e4 DtaStor Update service properties: service
    registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
    2006-06-09 10:09:30 2556 a04 COMAPI - Added service, URL =
    http://update.microsoft.com/microsoftupdate/
    2006-06-09 10:09:30 2556 a04 COMAPI ----------- COMAPI:
    IUpdateServiceManager::RegisterServiceWithAU -----------
    2006-06-09 10:09:30 2556 a04 COMAPI - ServiceId =
    {7971f918-a847-4430-9279-4a52d1efe18d}
    2006-06-09 10:09:32 2556 a04 Misc =========== Logging initialized (build:
    5.8.0.2469, tz: +0200) ===========
    2006-06-09 10:09:32 2556 a04 Misc = Process: C:\Program Files\Internet
    Explorer\iexplore.exe
    2006-06-09 10:09:32 2556 a04 Misc = Module: C:\WINNT\system32\muweb.dll
    2006-06-09 10:09:32 2556 a04 Setup *********** Setup: Checking whether
    self-update is required ***********
    2006-06-09 10:09:32 2556 a04 Setup * Inf file:
    C:\WINNT\SoftwareDistribution\WebSetup\wusetup.inf
    2006-06-09 10:09:32 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wuweb.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469
    2006-06-09 10:09:32 2556 a04 Setup * IsUpdateRequired = No
    2006-06-09 10:09:33 2556 a04 Misc =========== Logging initialized (build:
    5.8.0.2469, tz: +0200) ===========
    2006-06-09 10:09:33 2556 a04 Misc = Process: C:\Program Files\Internet
    Explorer\iexplore.exe
    2006-06-09 10:09:33 2556 a04 Misc = Module: C:\WINNT\system32\wuweb.dll
    2006-06-09 10:09:33 2556 a04 Setup *********** Setup: Checking whether
    self-update is required ***********
    2006-06-09 10:09:33 2556 a04 Setup * Inf file:
    C:\WINNT\SoftwareDistribution\WebSetup\wusetup.inf
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\cdm.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\iuengine.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wuapi.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wuauclt.exe: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wuauclt1.exe: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wuaucpl.cpl: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wuaueng.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wuaueng1.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wucltui.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wups.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup Update NOT required for
    C:\WINNT\system32\wups2.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469
    2006-06-09 10:09:33 2556 a04 Setup * IsUpdateRequired = No
    2006-06-09 10:09:41 2556 a04 COMAPI -------------
    2006-06-09 10:09:41 2556 a04 COMAPI -- START -- COMAPI: Search [ClientId =
    MicrosoftUpdate]
    2006-06-09 10:09:41 2556 a04 COMAPI ---------
    2006-06-09 10:09:41 2556 a04 COMAPI - Online = Yes; Ignore download
    priority = No
    2006-06-09 10:09:41 2556 a04 COMAPI - Criteria = "IsInstalled=0 and
    IsHidden=1"
    2006-06-09 10:09:41 2556 a04 COMAPI - ServiceID =
    {7971F918-A847-4430-9279-4A52D1EFE18D}
    2006-06-09 10:09:41 1620 8b8 Agent *************
    2006-06-09 10:09:41 1620 8b8 Agent ** START ** Agent: Finding updates
    [CallerId = MicrosoftUpdate]
    2006-06-09 10:09:41 2556 a04 COMAPI <<-- SUBMITTED -- COMAPI: Search
    [ClientId = MicrosoftUpdate]
    2006-06-09 10:09:41 1620 8b8 Agent *********
    2006-06-09 10:09:42 1620 8b8 PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2006-06-09 10:09:42 1620 8b8 PT + ServiceId =
    {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
    https://update.microsoft.com/v6/ClientWebService/client.asmx
    2006-06-09 10:09:42 1620 8b8 PT WARNING: GetConfig failure, error =
    0x80244021, soap client error = 10, soap error code = 0, HTTP status code =
    502
    2006-06-09 10:09:42 1620 8b8 PT WARNING: Sync of Updates: 0x80244021
    2006-06-09 10:09:42 1620 8b8 Agent * WARNING: Failed to synchronize, error
    = 0x80244021
    2006-06-09 10:09:42 1620 8b8 Agent * WARNING: Exit code = 0x80244021
    2006-06-09 10:09:42 1620 8b8 Agent *********
    2006-06-09 10:09:42 1620 8b8 Agent ** END ** Agent: Finding updates
    [CallerId = MicrosoftUpdate]
    2006-06-09 10:09:42 1620 8b8 Agent *************
    2006-06-09 10:09:42 1620 8b8 Agent WARNING: WU client failed Searching for
    update with error 0x80244021
    2006-06-09 10:09:42 2556 9ac COMAPI >>-- RESUMED -- COMAPI: Search
    [ClientId = MicrosoftUpdate]
    2006-06-09 10:09:42 2556 9ac COMAPI - Updates found = 0
    2006-06-09 10:09:42 2556 9ac COMAPI - WARNING: Exit code = 0x00000000,
    Result code = 0x80244021
    2006-06-09 10:09:42 2556 9ac COMAPI ---------
    2006-06-09 10:09:42 2556 9ac COMAPI -- END -- COMAPI: Search [ClientId =
    MicrosoftUpdate]
    2006-06-09 10:09:42 2556 9ac COMAPI -------------
    2006-06-09 10:09:42 2556 a04 COMAPI WARNING: Operation failed due to earlier
    error, hr=80244021
    2006-06-09 10:09:42 2556 a04 COMAPI FATAL: Unable to complete asynchronous
    search. (hr=80244021)
    2006-06-09 10:09:47 1620 8b8 Report REPORT EVENT:
    {5DB6F0BB-375C-4610-9C44-55BC6FAF48B2} 2006-06-09
    10:09:42+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244021 MicrosoftUpdate Failure Software
    Synchronization Error: Agent failed detecting with reason: 0x80244021
     
    The Prutser, Jun 9, 2006
    #1
    1. Advertisements

  2. The Prutser

    The Prutser Guest

    Now both servers cannot access WU any longer. After I updated SVR02 and
    started WU to look for additional updates I now get the error: 0x80072F78

    To summarize:
    * When I start WU on SVR01 and click either express or custom I get the
    error: 0x80244021
    * When I start WU on SVR02 and even before I can click either express or
    custom I get the error: 0x80072F78

    Important note:
    The error on SVR02 occurred after I had successfully updated the server.

     
    The Prutser, Jun 9, 2006
    #2
    1. Advertisements

  3. On both servers: open a command prompt window, and type the command

    proxycfg

    Copy and paste the output from both into a follow-up in this thread.
     
    Robin Walker [MVP], Jun 9, 2006
    #3
  4. The Prutser

    The Prutser Guest

    I do not think this is what you hope for:
    C:\>proxycfg
    'proxycfg' is not recognized as an internal or external command,
    operable program or batch file.

    On the other hand I have solved the errror 0x80072F78 on SVR02. I stopped
    the BITS and WUAUSERV services, renamed the softwaredistribution folder,
    started windows update.

    Only as soon as I want to use the new improved (????) 'Microsoft Update' I
    get the same error 0x80072F78. So I am sticking to the plain old Windows
    Update for this server. Microsoft Update does not seems to be capable of
    running through proxy servers.

    This procedure does not fix the 0x80244021 error on SVR01 by the way.
     
    The Prutser, Jun 9, 2006
    #4
  5. Problem solved:
    1. stopped BITS and WU services, renamed softwaredistribution folder
    2. followed kb897225
    3. installed: kb 87337, kb883939, kb889293, kb889669, kb896688, kb896727
    4. installed BITS update KB842773 and Windows Installer 3.1

    Still I find it very strange I have to perform some manually steps on one
    server and on the other server everthing goes well. Although on both server I
    am not able to use the new and improved 'Microsoft Update', because that will
    result in error 0x80072F78
     
    Erik Nettekoven [MCSE], Jun 9, 2006
    #5
    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.