locked
WSUS Clients Not Reporting or Receiving Updates: Error Code 80244008 & CookieExpired RRS feed

  • Question

  • We have started having issues with WSUS clients receiving updates and reporting status to our WSUS server. Our WSUS environment has been working for years without issue prior to this problem, so this is not a new install or environment.  I am seeing consistent Cookie errors on the clients in the windowsupdate.log, and on the WSUS server in the softwaredistribution.log.

    This all seems to have started happening about eight days ago. According to the WSUS admin console a majority of my clients have not reported in eight days or more. No updates were pushed just prior to this issue, and as far as I know no major changes in our environment has occurred.

    Following are details from each log:

    ----------------------------------------------
    ----------------------------------------------

    Clients windowsupdate.log:

    932 948 PT +++++++++++ PT: Synchronizing server updates +++++++++++
    932 948 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://rcwinupdate.%domain%.com/Clie...ce/client.asmx


    932 948 PT WARNING: Cached cookie has expired or new PID is available
    932 948 PT Initializing simple targeting cookie, clientId = 091fde7d-75af-44b1-b0a5-fce8e74d64a2, target group = WsusSrvAutoStage1, DNS name = testsitesrv02.rescare.ad


    932 948 PT Server URL = http://rcwinupdate.%domain%.com/Simp...impleAuth.asmx
    932 948 PT WARNING: GetAuthorizationCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200


    932 948 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244008
    932 948 PT WARNING: PopulateAuthCookies failed: 0x80244008
    932 948 PT WARNING: RefreshCookie failed: 0x80244008
    932 948 PT WARNING: RefreshPTState failed: 0x80244008
    932 948 PT WARNING: Sync of Updates: 0x80244008
    932 948 PT WARNING: SyncServerUpdatesInternal failed: 0x80244008
    932 948 Agent * WARNING: Failed to synchronize, error = 0x80244008
    932 948 Agent * WARNING: Exit code = 0x80244008
    932 948 Agent *********
    932 948 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
    932 948 Agent *************
    932 948 Agent WARNING: WU client failed Searching for update with error 0x80244008
    932 11e8 AU >>## RESUMED ## AU: Search for updates [CallId = {768E50D3-6A6A-40F7-B945-C1D4830929B4}]
    932 11e8 AU # WARNING: Search callback failed, result = 0x80244008
    932 11e8 AU # WARNING: Failed to find updates with error code 80244008
    932 11e8 AU #########
    932 11e8 AU ## END ## AU: Search for updates [CallId = {768E50D3-6A6A-40F7-B945-C1D4830929B4}]
    932 11e8 AU #############
    932 11e8 AU AU setting next detection timeout to 2011-04-15 15:20:11
    932 11e8 AU Setting AU scheduled install time to 2011-04-16 05:00:00


    932 948 Report REPORT EVENT: {0AB8BEF5-A8E2-49DA-AC3B-90CD4BBB943E} 2011-04-15 10:28:47:193-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244008 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244008.

    ----------------------------------------------
    ----------------------------------------------

    WSUS Servers softwaredistribution log:


    2011-04-15 14:07:55.832 UTC Info w3wp.11 ThreadEntry ISAPIRuntime.ProcessRequest

    2011-04-15 14:07:55.832 UTC Warning w3wp.11 SoapUtilities.CreateException ThrowException: actor = http://winupdate.%domain%.com/Client...ce/client.asmx, ID=dbd6a9d8-620d-47b7-b8bf-e518f150c1b5, ErrorCode=CookieExpired, Message=, Client=5d4fd2ed-8eae-4f99-a8e5-bc6f52e8551b

    ----------------------------------------------
    ----------------------------------------------

    I've done research on this, but can't seem to find anyone who has had this issue and received an answer for the resolution.  If more detail is needed please let me know,  would be happy to provide more informaiton.  Any help from the community would be greatly appreciated.
    Friday, April 15, 2011 5:44 PM

Answers

  • Just a quick update.  We found the cause of the issue.  One of our down stream WSUS servers had a full disk.  This server services most of our cients, and as a result was causing the problem for a majority of our clients.  The disk space was being taken by IIS logs.  We cleaned the disk up and rebooted the server.  Shortly after that WSUS was working normally. 
    • Marked as answer by Vincent Hu Tuesday, April 26, 2011 8:35 AM
    Tuesday, April 19, 2011 4:57 PM

All replies

  • Our WSUS environment has been working for years without issue prior to this problem, so this is not a new install or environment.

    So the very first question in my mind, without reading any further in the message is this: Who changed what?

    No doubt, somebody changed something. That's the only reason that working things just quit working.

    I am seeing consistent Cookie errors on the clients in the windowsupdate.log, and on the WSUS server in the softwaredistribution.log.

    This all seems to have started happening about eight days ago. According to the WSUS admin console a majority of my clients have not reported in eight days or more.
    So, the good news is you know WHEN it was changed, now you just have to find the WHO and WHAT.
    as far as I know no major changes in our environment has occurred.

    The key words here being "as far as I know". Sadly, these type of changes that break things are almost always equally associated with the changer failing to tell the organization that such changes were being made, which is often combined with a gross lack of awareness on the part of the changer of the far-reaching implications of such changes -- that being a direct outgrowth of failing to **TEST** such changes before implementing them enterprise-wide.

    932 948 PT WARNING: GetAuthorizationCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
    932 948 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244008
    932 948 PT WARNING: PopulateAuthCookies failed: 0x80244008
    932 948 PT WARNING: RefreshCookie failed: 0x80244008
    932 948 PT WARNING: RefreshPTState failed: 0x80244008
    932 948 PT WARNING: Sync of Updates: 0x80244008
    932 948 PT WARNING: SyncServerUpdatesInternal failed: 0x80244008
    932 948 Agent * WARNING: Failed to synchronize, error = 0x80244008
    932 948 Agent * WARNING: Exit code = 0x80244008
    0x80244028 -2145107928 SUS_E_PT_NO_AUTH_COOKIES_CREATED The client was unable to create any valid auth cookies

    This is a client-side issue. Since it appears to be occuring on "a majority of [the] clients", the logical assumption from there is that somebody implemented a new Group Policy Object -- probably security related. Either somebody imposed a Security Template on all systems, or somebody imposed an ACL change that is breaking the functionality of the Windows Update Agent, by blocking it's ability to create the targeting cookie.

    One diagnostic step you might take is to evaluate any differences between the clients that are not reporting and those that are. Do they have common domain or workgroup memberships? Do they have common OrgUnit memberships? Those that are still reporting would indicate machines that were not impacted by whatever change was made 8 days ago.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, April 15, 2011 7:46 PM
  • Lawrence,

    Thanks for the reply.  I've been trying to run down any changes in the environment, but as of now I can't find any that coincide with the timeframe needed (7 or 8 days ago).  Is there any way this could be a WSUS server issue?  I know this is a long shot, but possibly a database issue causing clients to not update or report.  We have had problems with our database in the past, and currently have to run maintenance on a daily basis just to access the admin console.

    John

    Friday, April 15, 2011 8:12 PM
  • Is there any way this could be a WSUS server issue?

    While it's possible, the current observations suggest not.

    Since you do have some machines working perfectly, that suggests against a server-side issue.

    A better evaluation could be made if you can compare those that are working with those that are not and identify any common attributes.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, April 15, 2011 9:03 PM
  • Just a quick update.  We found the cause of the issue.  One of our down stream WSUS servers had a full disk.  This server services most of our cients, and as a result was causing the problem for a majority of our clients.  The disk space was being taken by IIS logs.  We cleaned the disk up and rebooted the server.  Shortly after that WSUS was working normally. 
    • Marked as answer by Vincent Hu Tuesday, April 26, 2011 8:35 AM
    Tuesday, April 19, 2011 4:57 PM
  • Just a quick update.  We found the cause of the issue.  One of our down stream WSUS servers had a full disk.  This server services most of our cients, and as a result was causing the problem for a majority of our clients.  The disk space was being taken by IIS logs.  We cleaned the disk up and rebooted the server.  Shortly after that WSUS was working normally. 


    Thank you for the feedback.

    So the "common attribute" was that the clients were all assigned to the same WSUS server. :-)

    Typically these scenarios are discovered when the database engine crashes, or a server content download gripes in the Event Log, and the client logs generally never have come into play. It is, however, exceptionally useful to know that an out-of-disk error on a WSUS server will manifest as a client-side 0x80244008 error code, trying to create a cookie.

     


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, April 19, 2011 6:47 PM