Results 1 to 5 of 5

Thread: WSUS Server 3.0 SP1 Cookie Expired Issue

  1. #1
    Join Date
    Apr 2011
    Posts
    3

    WSUS Server 3.0 SP1 Cookie Expired Issue

    We have started having issues with WSUS clients receiving updates and reporting status to our WSUS server. I am seeing consistent Cookie errors on the clietnts 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:

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

    Client's 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. Any help from the community would be greatly appreciated.

  2. #2
    Join Date
    Jan 2006
    Posts
    4,224

    Re: WSUS Server 3.0 SP1 Cookie Expired Issue

    Did you make sure that AU service is started on the pc in question? Have you tried renaming the softwareDistribution folder in "c:\windows"? Have you tried deleting the pc from WSUS and see if it will connect to it again?Since it's talking about an expired cookie have you tried "wuauclt.exe /resetauthorization /detectnow"?

  3. #3
    Join Date
    Apr 2011
    Posts
    3

    Re: WSUS Server 3.0 SP1 Cookie Expired Issue

    Zachary,

    Thanks for the response.

    "wuauclt.exe /resetauthorization /detectnow" -- Yes I have ran that several times on two of our clients, no change. The errors remain consistent on both ends.

    We have well over 4000 clients, all of which are displaying this same issue. I believe is an issue on the server due to the amount of clients experiencing the problem. Or possibly an enterprise wide change that I was unaware of, but that's probably not the case as I have been unable to find any changes that coincide with the timeframe needed (7 or 8 days ago).

    John

  4. #4
    Join Date
    Jan 2006
    Posts
    4,224

    Re: WSUS Server 3.0 SP1 Cookie Expired Issue

    You will need to check the IIS for the virtual directory "selfupdate" under WSUS Adminitrator website. If it did not exists, please manually create the vitural directory(the default local path should be C:\Program Files\Update Services\Selfupdate) in IIS and giving it anonymous access. Then restart the Windows Update Service.

  5. #5
    Join Date
    Apr 2011
    Posts
    3

    Re: WSUS Server 3.0 SP1 Cookie Expired Issue

    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.

Similar Threads

  1. WARNING: Cached cookie has expired or new PID is available
    By Q Jones in forum Server Update Service
    Replies: 1
    Last Post: 24-07-2009, 02:16 AM
  2. wsus clients not contact wsus server error = 0x80244023 and 0x8019
    By Dilbert in forum Server Update Service
    Replies: 3
    Last Post: 06-03-2009, 10:47 PM
  3. Replies: 2
    Last Post: 15-08-2008, 12:18 AM
  4. WSUS Event ID 421 Reason=Timeout expired
    By samit in forum Server Update Service
    Replies: 4
    Last Post: 13-12-2007, 05:58 PM
  5. WSUS client unable to connect WSUS server
    By BoanHed in forum Server Update Service
    Replies: 3
    Last Post: 28-10-2007, 03:29 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •