WSUS clients fail synchronization with 0x80244015 and 0x8024400D errors

WSUS clients fail synchronization with 0x80244015 and 0x8024400D errors

  • Comments 4
  • Likes

Here's a good WSUS tip from Joe Tindale, one of the top Senior Support Escalation Engineer in our WSUS support group.  If you're seeing 0x80244015 and 0x8024400D errors and are using a load balancer with your WSUS servers then this may be your issue:

========

Issue: WSUS clients may fail during synchronization and log the following errors:

2008-09-11 07:13:19:956 892 c0c PT WARNING: Cached cookie has expired or new PID is available
2008-09-11 07:13:19:956 892 c0c PT Initializing simple targeting cookie, clientId = 1a7399bc-3887-44d3-a1bb-09df5f4c93b6, target group = <servers>, DNS name = <ServerFQDN>
2008-09-11 07:13:19:956 892 c0c PT Server URL =
/SimpleAuthWebService/SimpleAuth.asmx">/SimpleAuthWebService/SimpleAuth.asmx">http://<serverName>/SimpleAuthWebService/SimpleAuth.asmx
2008-09-11 07:13:20:222 892 c0c PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2008-09-11 07:13:20:222 892 c0c PT WARNING: SOAP Fault: 0x00012c
2008-09-11 07:13:20:222 892 c0c PT WARNING: faultstring:Fault occurred
2008-09-11 07:13:20:222 892 c0c PT WARNING: ErrorCode:InvalidCookie(1)
2008-09-11 07:13:20:222 892 c0c PT WARNING: Message:(null)
2008-09-11 07:13:20:222 892 c0c PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2008-09-11 07:13:20:222 892 c0c PT WARNING: ID:aea005ee-5554-40f4-a545-9504248ec0ba
2008-09-11 07:13:20:222 892 c0c PT WARNING: PTError: 0x80244015
2008-09-11 07:13:20:222 892 c0c PT WARNING: GetCookie_WithRecovery failed : 0x80244015
2008-09-11 07:13:20:222 892 c0c PT WARNING: RefreshCookie failed: 0x80244015
2008-09-11 07:13:20:222 892 c0c PT WARNING: RefreshPTState failed: 0x80244015
2008-09-11 07:13:20:800 892 c0c PT WARNING: Cached cookie has expired or new PID is available
2008-09-11 07:13:20:800 892 c0c PT Initializing simple targeting cookie, clientId = 1a7399bc-3887-44d3-a1bb-09df5f4c93b6, target group = <servers>, DNS name = <ServerFQDN>
2008-09-11 07:13:20:800 892 c0c PT Server URL =
/SimpleAuthWebService/SimpleAuth.asmx">/SimpleAuthWebService/SimpleAuth.asmx">http://<serverName>/SimpleAuthWebService/SimpleAuth.asmx
2008-09-11 07:13:20:815 892 c0c PT WARNING: RefreshCache failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
2008-09-11 07:13:20:815 892 c0c PT WARNING: SOAP Fault: 0x000190
2008-09-11 07:13:20:815 892 c0c PT WARNING: faultstring:Fault occurred
2008-09-11 07:13:20:815 892 c0c PT WARNING: ErrorCode:InternalServerError(5)
2008-09-11 07:13:20:815 892 c0c PT WARNING: Message:(null)
2008-09-11 07:13:20:815 892 c0c PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/RefreshCache"
2008-09-11 07:13:20:815 892 c0c PT WARNING: ID:e501ca1b-2ff1-43b2-84aa-016015cf9dc9
2008-09-11 07:13:20:815 892 c0c PT WARNING: PTError: 0x8024400e
2008-09-11 07:13:20:815 892 c0c PT WARNING: RefreshCache_WithRecovery failed: 0x8024400e
2008-09-11 07:13:20:815 892 c0c PT WARNING: SyncCache: Emergency cleanup of the ServerUpdateInfo due to failure in RefreshCache
2008-09-11 07:13:23:175 892 c0c PT WARNING: PTError: 0x8024400e
2008-09-11 07:13:23:175 892 c0c Report WARNING: Reporter failed to upload events with hr = 8024400e.

Cause: This can occur if you group two or more WSUS servers together using a load balancer and each of the servers has a local Windows Internal Database.  In this scenario, each time a client connects to WSUS it's possible to hit a different server and get in a state where the client needs to renew the cookie and refresh cache.

Resolution: Our deployment guide states if your going to cluster WSUS you need to have a shared SQL backend to avoid this issue:

Appendix C: Configure WSUS for Network Load Balancing

It may have been possible to work around this issue with some sort of client affinity on the load balancer but still our supported scenario contains a shared SQL backend.

========

Thanks Joe!

J.C. Hornbeck | Manageability Knowledge Engineer

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • PingBack from http://mstechnews.info/2008/10/wsus-clients-fail-synchronization-with-0x80244015-and-0x8024400d-errors/

  • I get this error....only have one sus?  can you help

  • Solved the issue.  This will also occur when the client Sus ID  value is messed up in the Registry, under HKLM....update service.  Delete the whole key, re-install, restart.  Appears to fix all that up.

  • Confirmed - this worked to resolve "WARNING: Failes to synchronize, error = 0x80244015"

    1) Place the following lines in a .REG file and merge it at the WSUS client:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate]

    "AccountDomainSid"=-

    "PingID"=-

    "SusClientId"=-

    "SusClientIdValidation"=-

    2) Perform the following in CMD prompt:

    WUAUCLT /resetauthorization  /detectnow

    WUAUCLT /r  /reportnow

    3) Monitor  %windir%\windowsupdate.log   for additional issues ... but this should correct the issue discussed in this post.