WSUS Client Error 0x8024400A

Discussion in 'Update Services' started by Thomas Hermanns, Jul 19, 2005.

  1. I updated SUS to WSUS and all works fine. The clients are contacting
    periodically the WSUS and receive the updates, the status is ok.

    One client only contacts the WSUS, and at the first contact it hat created a
    status, but now it will not actualize it, and will not download nessesary
    updates.

    The WindowsUpdate.log reports an error WARNING: GetCookie failure, error =
    0x8024400A

    I have no idea

    This is the WindowsUpdate.log
    2005-07-19 09:00:29 208 5c0 AU #############
    2005-07-19 09:00:29 208 5c0 AU ## START ## AU: Search for updates
    2005-07-19 09:00:29 208 5c0 AU #########
    2005-07-19 09:00:29 208 5c0 AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {AD1DB1A6-58E9-4F0D-A9FE-095AC96A71BE}]
    2005-07-19 09:00:29 208 d8 Agent *************
    2005-07-19 09:00:29 208 d8 Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2005-07-19 09:00:29 208 d8 Agent *********
    2005-07-19 09:00:29 208 d8 Setup *********** Setup: Checking whether
    self-update is required ***********
    2005-07-19 09:00:29 208 d8 Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup Update NOT required for
    C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2005-07-19 09:00:29 208 d8 Setup * IsUpdateRequired = No
    2005-07-19 09:00:31 208 d8 PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2005-07-19 09:00:31 208 d8 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://Hegge-9/ClientWebService/client.asmx
    2005-07-19 09:00:31 208 d8 PT Initializing simple targeting cookie,
    clientId = 19b4b1e0-ca1c-4e10-9721-6b49feb54726, target group = , DNS name =
    hegge-tz
    2005-07-19 09:00:31 208 d8 PT Server URL =
    http://Hegge-9/SimpleAuthWebService/SimpleAuth.asmx
    2005-07-19 09:00:31 208 d8 PT WARNING: GetCookie failure, error =
    0x8024400A, soap client error = 10, soap error code = 0, HTTP status code =
    200
    2005-07-19 09:00:31 208 d8 PT WARNING: Sync of Updates: 0x8024400a
    2005-07-19 09:00:31 208 d8 Agent * WARNING: Failed to synchronize, error
    = 0x8024400A
    2005-07-19 09:00:31 208 d8 Agent * WARNING: Exit code = 0x8024400A
    2005-07-19 09:00:31 208 d8 Agent *********
    2005-07-19 09:00:31 208 d8 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2005-07-19 09:00:31 208 d8 Agent *************
    2005-07-19 09:00:31 208 d8 Agent WARNING: WU client failed Searching for
    update with error 0x8024400a
    2005-07-19 09:00:31 208 d8 AU >>## RESUMED ## AU: Search for updates
    [CallId = {AD1DB1A6-58E9-4F0D-A9FE-095AC96A71BE}]
    2005-07-19 09:00:31 208 d8 AU # WARNING: Search callback failed, result
    = 0x8024400A
    2005-07-19 09:00:31 208 d8 AU #########
    2005-07-19 09:00:31 208 d8 AU ## END ## AU: Search for updates [CallId
    = {AD1DB1A6-58E9-4F0D-A9FE-095AC96A71BE}]
    2005-07-19 09:00:31 208 d8 AU #############
    2005-07-19 09:00:31 208 d8 AU AU setting next detection timeout to
    2005-07-19 07:55:54
    2005-07-19 09:00:36 208 d8 Report REPORT EVENT:
    {7F1E1C0A-D193-4A0D-877E-A2E4236C20B2} 2005-07-19 09:00:31+0200 1 148 101
    {00000000-0000-0000-0000-000000000000} 0 8024400a AutomaticUpdates Failure
    Software Synchronization Error: Agent failed detecting with reason:
    0x8024400a
    2005-07-19 09:02:28 208 528 PT Initializing simple targeting cookie,
    clientId = 19b4b1e0-ca1c-4e10-9721-6b49feb54726, target group = , DNS name =
    hegge-tz
    2005-07-19 09:02:28 208 528 PT Server URL =
    http://Hegge-9/SimpleAuthWebService/SimpleAuth.asmx
    2005-07-19 09:02:28 208 528 PT WARNING: GetCookie failure, error =
    0x8024400A, soap client error = 10, soap error code = 0, HTTP status code =
    200
    2005-07-19 09:02:28 208 528 Report WARNING: Reporter failed to upload
    events with hr = 8024400a.
    c
     
    Thomas Hermanns, Jul 19, 2005
    #1
    1. Advertisements

  2. Thomas, this 8024400A error is most likely rectified by a hotfix that has
    been made available for Windows Server 2003 SP1 systems. The scenario and
    fix are discussed in the summary article posted by Bobbie Harder on Friday
    7/16. Here is the extract that I believe may be applicable to your
    situation:

    "Some clients have been impacted by a known issue in with Windows Server
    2003 http.sys and IIS. In some cases, this transient issue will appear to
    prevent clients from checking in, because they receive invalid responses
    from the server after some attempts. It was previously believed to be an
    issue with IIS compression and there was a workaround suggested to disable
    compression, and then rename the
    %windir%\system32\inetsrv\suscomp.dll file and restart the IIS, and the
    Update Services service.

    Further Investigation shows the problem source to be a known condition with
    IIS and http.sys, which is not related to compression, and for which there
    is an available hotfix. It is not recommended to disable compression as
    this will not impact the problem source, and possibly increase network
    traffic & server load, while reducing the number of clients you can
    effectively serve. Further information about the issue and obtaining the
    hotfix can be found: http://support.microsoft.com/?id=898708 ."


     
    Lawrence Garvin, Jul 20, 2005
    #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.