Error: Agent failed detecting with reason: 0x8024400a

Discussion in 'Update Services' started by Magnus Tengmo, Aug 2, 2005.

  1. Hi!

    I got this error in status window on my clients.
    Error: Agent failed detecting with reason: 0x8024400a
    Anyone know how to solve this problem?

    Best Regards, Magnus Tengmo
     
    Magnus Tengmo, Aug 2, 2005
    #1
    1. Advertisements

  2. Hi,

    WSUS on a Microsoft Windows Server 2003 I assume?

    This is caused by a known issue in with Windows Server 2003
    http.sys and IIS.

    Call Microsoft for this hotfix (you will not be charged as long as
    you ask for the hotfix and nothing else):

    http://support.microsoft.com/?id=898708


    Note that you must have Microsoft Windows Server 2003 Service Pack 1
    installed to apply this hotfix.


    More about this issue here:

    http://www.wsuswiki.com/ClientFAQ

    See the section "Known Client Issues:", first entry.
     
    Torgeir Bakken \(MVP\), Aug 2, 2005
    #2
    1. Advertisements

  3. Thanks, do you know what happens with the clients that haven´t reported yet ?
    I have still 19 computers that haven´t report with this error.

    Best Regards, Magnus.
     
    Magnus Tengmo, Aug 5, 2005
    #3
  4. Magnus, once you apply the hotfix, the next detection cycle by the client
    should result in a normal/successful connection with the server.

    If, after 24 hours, you still don't have all clients, go back to the
    client(s) and troubleshoot it as a client-side problem.
     
    Lawrence Garvin, Aug 5, 2005
    #4
  5. My /best/ idea if you've applied a PSS-provided hotfix that doesn't 'fix'
    the problem it's designed to fix is to call PSS back, and invest the $250 --
    because this may be the /first/ incident that this hotfix is not the right
    fix for an 0x8024400A error.

     
    Lawrence Garvin, Aug 24, 2005
    #5
  6. Doncha just know that when all else fails.... a reboot will fix everything.
    :)

    The patch is definitely needed for the 0x8024400a errors... but there could
    have also been a concurrent contributing issue at the client that was reset
    as a result of the reboot.

    I haven't looked into exactly what the hotfix fixes... but it could be that
    the client had something cached that was cleared as a result of the reboot.

     
    Lawrence Garvin, Aug 25, 2005
    #6
    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.