0x8024400D

Discussion in 'Update Services' started by Stephen Hughes, Jun 30, 2005.

  1. I realize there is a common issue with the 0x8024400, but I just wanted to
    check on my case with the 0x8024400D. I don't know if the 'D' makes that
    much of a difference. It's pretty much the same case. Twenty percent of my
    clients are not reporting. I also get the same error following:

    -------
    2005-06-29 17:42:18 1172 5a8 PT WARNING: GetCookie failure, error =
    0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
    200
    2005-06-29 17:42:18 1172 5a8 PT WARNING: SOAP Fault: 0x00012c
    2005-06-29 17:42:18 1172 5a8 PT WARNING: faultstring:Fault occurred
    2005-06-29 17:42:18 1172 5a8 PT WARNING: ErrorCode:ConfigChanged(2)
    2005-06-29 17:42:18 1172 5a8 PT WARNING: Message:

    2005-06-29 17:42:18 1172 5a8 PT WARNING:

    ------

    I'm not familiar with the "soap" error. I'm running WSUS on a W2K3 Server
    SP1. The clients are all XP SP2. Eighty percent reported in the first and
    second day. That's all I've had.

    Stephen
     
    Stephen Hughes, Jun 30, 2005
    #1
    1. Advertisements

  2. Stephen Hughes

    Jason Ede Guest

    I'm getting the same error on some workstations that are XP SP1. Have
    you managed to sort it yet?

    Jason
     
    Jason Ede, Jul 5, 2005
    #2
    1. Advertisements

  3. Hi

    Can you send the complete log?

    Thanks,

    --
    Oscar Lee (MSFT)
    Microsoft Corporation
    WSUS

    (Communication using the newsgroup is preferred. Thanks!)

    =====================
    This posting is provided "AS IS" with no warranties, and confers no rights.
    =====================
     
    Oscar Lee \(MS\), Jul 6, 2005
    #3
  4. Stephen Hughes

    PTH Guest

    I received the same error and cannot update windows now. What's going on.

    Paul
     
    PTH, Jul 13, 2005
    #4
  5. I've got it working now. This is what worked for me and it didn't involve in
    serious modifications.

    1. visit http://update.microsoft.com/microsoftupdate
    2. stop the AU service
    3. delete the SusClientID from:
    \Local_Machine\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
    4. restart AU service
    5. run wuauclt.exe /detectnow (this will recreate the SusClientID)

    I did it on each client and haven't had a problem since.
     
    Stephen Hughes, Jul 15, 2005
    #5
  6. Stephen Hughes

    Jeraiko Guest

    Vielen, Dank, das war in der Tat die lang gesuchte Lösung!
     
    Jeraiko, Jul 20, 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.