locked
WSUS Server Broke By a Patch, Now fixing clients RRS feed

  • Question

  • After fixing our windows update server console this morning, the clients are still not able to connect to the WSUS server. Port 80 is still open from the clients to the WSUS server and a successful synch is completed, the console was entirely unusable earlier..  80244008 is the error from the clients. I rebooted a client to test, but still the same error. Any assistance is appreciated.
    Friday, May 20, 2016 5:29 PM

Answers

  • I fixed everything. Only part I am waiting for or trying to force is the updates that are waiting in the console to be pushed to the clients.  I ran a wuauclt.exe /resetauthorization /detectnow a few times. Giving ample enough time to have them pushed.  But still no updates are downloading.  The windowsupdate.log is clean, no errors.  This is the part I don't fully understand.  Why cant I force the updates to download?  I have verified the patches in the WSUS console are in fact not installed to the client yet.

    Friday, May 27, 2016 6:19 PM

All replies

  • 0x80244008  at the WU client can be due to a number of different causes; some examples:

    https://social.technet.microsoft.com/Forums/en-US/c74df64d-665d-49b1-99ce-b4a532d4706f/still-having-problems-after-installing-3159706?forum=winserverwsus

    https://social.technet.microsoft.com/Forums/en-US/9b71aad9-8746-4e17-a137-6ffc19a3a987/wsus-clients-not-reporting-or-receiving-updates-error-code-80244008-cookieexpired?forum=winserverwsus

    Can you confirm the health of the WSUS itself? any errors or warnings occurring in the WSUS event logs?

    If the issue you repaired/resolved was related to KB3148812 / KB3159706, did you perform the postinstall manual steps after applying KB3159706 ?

    Can you share a client windowsupdate.log here?


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Sunday, May 22, 2016 6:19 AM
  • We have the same issue after deploying first KB3148812 and then KB3159706 and performing the postinstall manual steps.

    2016-05-23 07:27:21:376 964 80c AU Triggering AU detection through DetectNow API
    2016-05-23 07:27:21:376 964 80c AU Triggering Online detection (interactive)
    2016-05-23 07:27:21:376 964 177c AU #############
    2016-05-23 07:27:21:376 964 177c AU ## START ## AU: Search for updates
    2016-05-23 07:27:21:376 964 177c AU #########
    2016-05-23 07:27:21:376 964 177c AU <<## SUBMITTED ## AU: Search for updates [CallId = {4F123B3A-EE80-4F14-A016-A1EA41374D2D}]
    2016-05-23 07:27:21:376 964 574 Agent *************
    2016-05-23 07:27:21:376 964 574 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-05-23 07:27:21:376 964 574 Agent *********
    2016-05-23 07:27:21:376 964 574 Agent * Online = Yes; Ignore download priority = No
    2016-05-23 07:27:21:376 964 574 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2016-05-23 07:27:21:376 964 574 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-05-23 07:27:21:376 964 574 Agent * Search Scope = {Machine}
    2016-05-23 07:27:21:376 964 574 Setup Checking for agent SelfUpdate
    2016-05-23 07:27:21:376 964 574 Setup Client version: Core: 7.6.7601.19161 Aux: 7.6.7601.19161
    2016-05-23 07:27:21:392 964 574 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-05-23 07:27:21:392 964 574 Misc Microsoft signed: NA
    2016-05-23 07:27:21:392 964 574 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP201B.tmp with dwProvFlags 0x00000080:
    2016-05-23 07:27:21:392 964 574 Misc Microsoft signed: NA
    2016-05-23 07:27:21:392 964 574 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-05-23 07:27:21:408 964 574 Misc Microsoft signed: NA
    2016-05-23 07:27:21:408 964 574 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-05-23 07:27:21:408 964 574 Misc Microsoft signed: NA
    2016-05-23 07:27:21:423 964 574 Setup Determining whether a new setup handler needs to be downloaded
    2016-05-23 07:27:21:423 964 574 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe with dwProvFlags 0x00000080:
    2016-05-23 07:27:21:423 964 574 Misc Microsoft signed: NA
    2016-05-23 07:27:21:423 964 574 Setup SelfUpdate handler update NOT required: Current version: 7.6.7600.320, required version: 7.6.7600.320
    2016-05-23 07:27:21:423 964 574 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-05-23 07:27:21:423 964 574 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-05-23 07:27:21:423 964 574 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-05-23 07:27:21:439 964 574 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-05-23 07:27:21:439 964 574 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-05-23 07:27:21:454 964 574 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-05-23 07:27:21:454 964 574 Setup SelfUpdate check completed. SelfUpdate is NOT required.
    2016-05-23 07:27:21:579 964 574 PT +++++++++++ PT: Synchronizing server updates +++++++++++
    2016-05-23 07:27:21:579 964 574 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://servername.domain.local:8530/ClientWebService/client.asmx
    2016-05-23 07:27:21:595 964 574 PT WARNING: Cached cookie has expired or new PID is available
    2016-05-23 07:27:21:595 964 574 PT Initializing simple targeting cookie, clientId = fdc6d506-e81d-471e-998a-d3ff9ecdedf1, target group = , DNS name = computername.domain.local
    2016-05-23 07:27:21:595 964 574 PT Server URL = http://servername.domain.local:8530/SimpleAuthWebService/SimpleAuth.asmx
    2016-05-23 07:27:21:626 964 574 PT WARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
    2016-05-23 07:27:21:626 964 574 PT WARNING: PTError: 0x80244008
    2016-05-23 07:27:21:626 964 574 PT WARNING: GetCookie_WithRecovery failed : 0x80244008
    2016-05-23 07:27:21:626 964 574 PT WARNING: RefreshCookie failed: 0x80244008
    2016-05-23 07:27:21:626 964 574 PT WARNING: RefreshPTState failed: 0x80244008
    2016-05-23 07:27:21:626 964 574 PT WARNING: Sync of Updates: 0x80244008
    2016-05-23 07:27:21:626 964 574 PT WARNING: SyncServerUpdatesInternal failed: 0x80244008
    2016-05-23 07:27:21:626 964 574 Agent * WARNING: Failed to synchronize, error = 0x80244008
    2016-05-23 07:27:21:626 964 574 Agent * WARNING: Exit code = 0x80244008
    2016-05-23 07:27:21:626 964 574 Agent *********
    2016-05-23 07:27:21:626 964 574 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-05-23 07:27:21:626 964 574 Agent *************
    2016-05-23 07:27:21:626 964 574 Agent WARNING: WU client failed Searching for update with error 0x80244008
    2016-05-23 07:27:21:626 964 1bbc AU >>## RESUMED ## AU: Search for updates [CallId = {4F123B3A-EE80-4F14-A016-A1EA41374D2D}]
    2016-05-23 07:27:21:626 964 1bbc AU # WARNING: Search callback failed, result = 0x80244008
    2016-05-23 07:27:21:626 964 1bbc AU # WARNING: Failed to find updates with error code 80244008
    2016-05-23 07:27:21:626 964 1bbc AU #########
    2016-05-23 07:27:21:626 964 1bbc AU ## END ## AU: Search for updates [CallId = {4F123B3A-EE80-4F14-A016-A1EA41374D2D}]
    2016-05-23 07:27:21:626 964 1bbc AU #############
    2016-05-23 07:27:21:626 964 1bbc AU Successfully wrote event for AU health state:0
    2016-05-23 07:27:21:626 964 1bbc AU AU setting next detection timeout to 2016-05-23 09:12:24
    2016-05-23 07:27:21:626 964 1bbc AU Setting AU scheduled install time to 2016-05-23 23:00:00
    2016-05-23 07:27:21:626 964 1bbc AU Successfully wrote event for AU health state:0
    2016-05-23 07:27:21:626 964 1bbc AU Successfully wrote event for AU health state:0
    2016-05-23 07:27:26:626 964 574 Report REPORT EVENT: {67065087-133E-4D78-9992-EEB1B25CCF25} 2016-05-23 07:27:21:626+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244008 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244008.
    2016-05-23 07:27:26:642 964 574 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-05-23 07:27:26:642 964 574 Report WER Report sent: 7.6.7601.19161 0x80244008(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    

    Monday, May 23, 2016 5:30 AM
  • Hi JSB_1975,

    >Port 80 is still open from the clients to the WSUS server and a successful synch is completed, the console was entirely unusable earlier..

    1. What is the version of your WSUS server, is it WSUS 3.0? If yes, check if you have upgrade it to the latest version 3.2.7600.274, if not, install KB2938066 to upgrade your WSUS server. If your WSUS server is 4.0, then check if you have installed KB3159706 as DonPick has mentioned.

    2. We may do some general troubleshooting steps. On client, reset windows update component; On WSUS server, run server cleanup wizard and re-index WSUS database.

    Reset windows update component:

    https://support.microsoft.com/en-us/kb/971058

    Re-index WSUS database:

    https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61

    Best Regards,

    Anne

      


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, May 23, 2016 5:35 AM
  • Hi svhelden,

    Try reindex WSUS database, check if it could help.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, May 23, 2016 5:37 AM
  •  

    Try reindex WSUS database, check if it could help.

    Did not.

    Btw, in WSUS log I have these entrie:

    2016-05-23 05:50:05.021 UTC	Info	w3wp.365	ThreadEntry	ThreadPoolWorkQueue.Dispatch
    2016-05-23 05:50:05.021 UTC	Warning	w3wp.365	UnencryptedCookieData.Deserialize	Argument exceptioninvalid header
    Parameter name: bytes
    2016-05-23 05:50:05.021 UTC	Warning	w3wp.365	EncryptionHelper.DecryptData	Argument exceptionMicrosoft.UpdateServices.Internal.Authorization.LoggedArgumentException: invalid header
    Parameter name: bytes
       at Microsoft.UpdateServices.Internal.Authorization.UnencryptedCookieData.Deserialize(Byte[] bytes)
       at Microsoft.UpdateServices.Internal.Authorization.EncryptionHelper.DecryptData(Byte[] cookieData)
    Parameter name: cookieData
    2016-05-23 05:50:05.021 UTC	Warning	w3wp.365	SoapUtilities.CreateException	ThrowException: actor = http://servername.company.local:8530/ClientWebService/client.asmx, ID=b7c9b1a9-cbe0-42ea-a15d-e091bfd095f1, ErrorCode=InvalidCookie, Message=, Client=?
    

    Monday, May 23, 2016 5:50 AM
  • Oops .. just found that KB3159706 had not installed correctly. No wonder it does not work.

    Reinstalling now.

    Monday, May 23, 2016 5:55 AM
  • Now after I reinstalled KB3159706, everything is working again. So sorry for bothering here.
    • Proposed as answer by DonPick Monday, May 23, 2016 8:31 AM
    Monday, May 23, 2016 6:33 AM
  • Hi svhelden,

    Not at all! Glad to hear it.

    If you have other questions later, just open a new case for yourself, so that you may get better help :)

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, May 23, 2016 6:37 AM
  • Still working on my clients. Our SUS DB was corrupted too which I didn't know when I first posted the issue.

    The Server version is 2012 R2 and I had to remove the WSUS Role and IIS Role, and remove the internal database. Everything has been rebuilt except for the OS.

    Now the clients are exhibiting 80244019 error.  I believe if I decline and re-approve the updates in the console, this will force a re-synch. Any thought?

    Tuesday, May 24, 2016 3:47 PM
  • Still working on my clients. Our SUS DB was corrupted too which I didn't know when I first posted the issue.

    The Server version is 2012 R2 and I had to remove the WSUS Role and IIS Role, and remove the internal database. Everything has been rebuilt except for the OS.

    Now the clients are exhibiting 80244019 error.  I believe if I decline and re-approve the updates in the console, this will force a re-synch. Any thought?


    80244019:
    Same as HTTP status 404 - the server cannot find the requested URI (Uniform Resource Identifier).

    Source: Windows Update Agent
    -----

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Tuesday, May 24, 2016 8:42 PM
  • I fixed everything. Only part I am waiting for or trying to force is the updates that are waiting in the console to be pushed to the clients.  I ran a wuauclt.exe /resetauthorization /detectnow a few times. Giving ample enough time to have them pushed.  But still no updates are downloading.  The windowsupdate.log is clean, no errors.  This is the part I don't fully understand.  Why cant I force the updates to download?  I have verified the patches in the WSUS console are in fact not installed to the client yet.

    Friday, May 27, 2016 6:19 PM
  • I fixed everything. Only part I am waiting for or trying to force is the updates that are waiting in the console to be pushed to the clients.  I ran a wuauclt.exe /resetauthorization /detectnow a few times. Giving ample enough time to have them pushed.  But still no updates are downloading.  The windowsupdate.log is clean, no errors.  This is the part I don't fully understand.  Why cant I force the updates to download?  I have verified the patches in the WSUS console are in fact not installed to the client yet.

    Are the client showing in the WSUS console, with date and time and Needed/NotRequired counters now?

    Is the WSUS log on the server showing successful client contact?

    Is the windowsupdate.log on the client showing successful updates detected (number of updates) etc?


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Saturday, May 28, 2016 9:07 AM
  • Hi JSB_1975,

    And are the updates approved for install on WSUS?

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, May 30, 2016 9:32 AM