none
Windows Update Client failed to detect with error 0x8024400d RRS feed

  • Question

  • Hello All,

    All of a sudden i am getting this error on all the clients. I have a internal wsus server, which my clients will connect and get the updates. Its working till Dec 3rd, i didnt made any changes.. but it stopped working.

    Please help me

    2015-01-05    18:54:13:281    1064    ae8    AU    Triggering AU detection through DetectNow API
    2015-01-05    18:54:13:281    1064    ae8    AU    Triggering Online detection (interactive)
    2015-01-05    18:54:13:281    1064    15f4    AU    #############
    2015-01-05    18:54:13:281    1064    15f4    AU    ## START ##  AU: Search for updates
    2015-01-05    18:54:13:281    1064    15f4    AU    #########
    2015-01-05    18:54:13:283    1064    15f4    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
    2015-01-05    18:54:13:283    1064    1430    Agent    *************
    2015-01-05    18:54:13:283    1064    1430    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-01-05    18:54:13:283    1064    1430    Agent    *********
    2015-01-05    18:54:13:283    1064    1430    Agent      * Online = Yes; Ignore download priority = No
    2015-01-05    18:54:13:283    1064    1430    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"
    2015-01-05    18:54:13:283    1064    1430    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2015-01-05    18:54:13:283    1064    1430    Agent      * Search Scope = {Machine}
    2015-01-05    18:54:13:283    1064    1430    Setup    Checking for agent SelfUpdate
    2015-01-05    18:54:13:284    1064    1430    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2015-01-05    18:55:24:178    1064    1430    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2015-01-05    18:55:24:186    1064    1430    Misc     Microsoft signed: Yes
    2015-01-05    18:55:24:257    1064    1430    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2015-01-05    18:55:24:261    1064    1430    Misc     Microsoft signed: Yes
    2015-01-05    18:55:24:297    1064    1430    Setup    Determining whether a new setup handler needs to be downloaded
    2015-01-05    18:55:24:297    1064    1430    Setup    SelfUpdate handler is not found.  It will be downloaded
    2015-01-05    18:55:24:297    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-05    18:55:24:299    1064    1430    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-05    18:55:24:300    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-05    18:55:24:314    1064    1430    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-05    18:55:24:314    1064    1430    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-05    18:55:24:336    1064    1430    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-05    18:55:24:336    1064    1430    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2015-01-05    18:55:25:375    1064    1430    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2015-01-05    18:55:25:375    1064    1430    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://abcd.mydomain.com:8530/ClientWebService/client.asmx
    2015-01-05    18:55:25:417    1064    1430    PT    WARNING: Cached cookie has expired or new PID is available
    2015-01-05    18:55:25:417    1064    1430    PT    Initializing simple targeting cookie, clientId = a788c530-2b29-4113-81e6-381a1751ada9, target group = , DNS name = a12300.mydomain.com
    2015-01-05    18:55:25:417    1064    1430    PT      Server URL = http://abcd.mydomain.com:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SOAP Fault: 0x00012c
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     faultstring:Fault occurred
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     ErrorCode:InvalidParameters(7)
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     Message:parameters.OtherCachedUpdateIDs
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     ID:fd13335d-34d0-49b6-b065-aefab8b836f8
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: PTError: 0x8024400d
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: Sync of Updates: 0x8024400d
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncServerUpdatesInternal failed: 0x8024400d
    2015-01-05    18:55:28:432    1064    1430    Agent      * WARNING: Failed to synchronize, error = 0x8024400D
    2015-01-05    18:55:28:433    1064    1430    Agent      * WARNING: Exit code = 0x8024400D
    2015-01-05    18:55:28:433    1064    1430    Agent    *********
    2015-01-05    18:55:28:433    1064    1430    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-01-05    18:55:28:433    1064    1430    Agent    *************
    2015-01-05    18:55:28:433    1064    1430    Agent    WARNING: WU client failed Searching for update with error 0x8024400d
    2015-01-05    18:55:28:496    1064    15cc    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
    2015-01-05    18:55:28:496    1064    15cc    AU      # WARNING: Search callback failed, result = 0x8024400D
    2015-01-05    18:55:28:496    1064    15cc    AU      # WARNING: Failed to find updates with error code 8024400D
    2015-01-05    18:55:28:496    1064    15cc    AU    #########
    2015-01-05    18:55:28:496    1064    15cc    AU    ##  END  ##  AU: Search for updates [CallId = {8995B9F5-4001-4F07-97E6-3CEFBDC15D6A}]
    2015-01-05    18:55:28:496    1064    15cc    AU    #############
    2015-01-05    18:55:28:498    1064    15cc    AU    Successfully wrote event for AU health state:0
    2015-01-05    18:55:28:500    1064    15cc    AU    AU setting next detection timeout to 2015-01-05 18:25:28
    2015-01-05    18:55:28:500    1064    15cc    AU    Setting AU scheduled install time to 2015-01-06 05:30:00
    2015-01-05    18:55:28:501    1064    15cc    AU    Successfully wrote event for AU health state:0
    2015-01-05    18:55:28:502    1064    15cc    AU    Successfully wrote event for AU health state:0
    2015-01-05    18:55:33:432    1064    1430    Report    REPORT EVENT: {633AB594-B0B7-426A-A49F-6F508897E1BA}    2015-01-05 18:55:28:433+0530    1    148    101    {00000000-0000-0000-0000-000000000000}    0    8024400d    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x8024400d.

    Monday, January 5, 2015 4:46 PM

Answers

All replies

  • All of a sudden i am getting this error on all the clients. I have a internal wsus server, which my clients will connect and get the updates. Its working till Dec 3rd, i didnt made any changes.. but it stopped working.

    Which suggests that something DID change. It's just unknown what changed. This would be a key thing to investigate.

    2015-01-05    18:55:25:417    1064    1430    PT      Server URL = http://abcd.mydomain.com:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SOAP Fault: 0x00012c
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     faultstring:Fault occurred
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     ErrorCode:InvalidParameters(7)
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     Message:parameters.OtherCachedUpdateIDs
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING:     ID:fd13335d-34d0-49b6-b065-aefab8b836f8
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: PTError: 0x8024400d
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: Sync of Updates: 0x8024400d
    2015-01-05    18:55:28:432    1064    1430    PT    WARNING: SyncServerUpdatesInternal failed: 0x8024400d
    2015-01-05    18:55:28:432    1064    1430    Agent      * WARNING: Failed to synchronize, error = 0x8024400D
    2015-01-05    18:55:28:433    1064    1430    Agent      * WARNING: Exit code = 0x8024400D

    The boldfaced portions above are the key items of note.

    It looks like you've got a bad update in the WSUS database. Unfortunately I don't have a current working SQL Query interface to a WSUS database, so I cannot do the lookup.

    If you're confident of the Dec 3rd date, I would start there, either an update that arrived on 12/3, or an update that was expired on 12/3. My educated guess would be that this is an expired update that still has an active approval and just needs to be declined. I'm also making an educated guess that the "ID" value in the logfile is the UpdateID causing the problem.

    You can use the WSUS PUBLIC_VIEWS to search the database on the UpdateID using PUBLIC_VIEWS.vUpdate.

    SELECT FROM PUBLIC_VIEWS.vUpdate WHERE UpdateID = 'fd13335d-34d0-49b6-b065-aefab8b836f8'


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Proposed as answer by Hector Bryan Saturday, November 25, 2017 5:43 AM
    Monday, January 5, 2015 7:27 PM
    Moderator
  • Hi Lawrence,

    Thanks for your reply.

    I am not able to find that update in the database.

    One more thing, when i try to check for updates this time it gave me different ID in the error.

    Unfortunately i am unable to find that error too.

    2015-01-06    10:58:55:194    1060    12f0    AU    Triggering AU detection through DetectNow API
    2015-01-06    10:58:55:194    1060    12f0    AU    Triggering Online detection (interactive)
    2015-01-06    10:58:55:195    1060    77c    AU    #############
    2015-01-06    10:58:55:195    1060    77c    AU    ## START ##  AU: Search for updates
    2015-01-06    10:58:55:195    1060    77c    AU    #########
    2015-01-06    10:58:55:196    1060    77c    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {DD87B2A6-D0E1-4EED-8074-72913BCE30F6}]
    2015-01-06    10:58:55:197    1060    1748    Agent    *************
    2015-01-06    10:58:55:197    1060    1748    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-01-06    10:58:55:197    1060    1748    Agent    *********
    2015-01-06    10:58:55:197    1060    1748    Agent      * Online = Yes; Ignore download priority = No
    2015-01-06    10:58:55:197    1060    1748    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"
    2015-01-06    10:58:55:197    1060    1748    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2015-01-06    10:58:55:197    1060    1748    Agent      * Search Scope = {Machine}
    2015-01-06    10:58:55:254    1060    1748    Setup    Checking for agent SelfUpdate
    2015-01-06    10:58:55:254    1060    1748    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2015-01-06    10:58:55:254    1060    1748    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2015-01-06    10:58:55:259    1060    1748    Misc     Microsoft signed: Yes
    2015-01-06    10:58:55:285    1060    1748    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2015-01-06    10:58:55:288    1060    1748    Misc     Microsoft signed: Yes
    2015-01-06    10:58:55:291    1060    1748    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2015-01-06    10:58:55:294    1060    1748    Misc     Microsoft signed: Yes
    2015-01-06    10:58:55:315    1060    1748    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2015-01-06    10:58:55:318    1060    1748    Misc     Microsoft signed: Yes
    2015-01-06    10:58:55:349    1060    1748    Setup    Determining whether a new setup handler needs to be downloaded
    2015-01-06    10:58:55:349    1060    1748    Setup    SelfUpdate handler is not found.  It will be downloaded
    2015-01-06    10:58:55:349    1060    1748    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-06    10:58:56:214    1060    1748    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-06    10:58:56:215    1060    1748    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-06    10:58:56:240    1060    1748    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-06    10:58:56:241    1060    1748    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-06    10:58:56:261    1060    1748    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-06    10:58:56:261    1060    1748    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2015-01-06    10:59:09:980    1060    1748    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2015-01-06    10:59:09:980    1060    1748    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://abcd.mydomain.com:8530/ClientWebService/client.asmx
    2015-01-06    10:59:10:224    1060    1748    PT    WARNING: Cached cookie has expired or new PID is available
    2015-01-06    10:59:10:224    1060    1748    PT    Initializing simple targeting cookie, clientId = a788c530-2b29-4113-81e6-381a1751ada9, target group = , DNS name = a12300.mydomain.com
    2015-01-06    10:59:10:224    1060    1748    PT      Server URL = http://abcd.mydomain.com:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-01-06    11:00:10:002    1060    77c    AU    Forced install timer expired for scheduled install
    2015-01-06    11:00:10:002    1060    77c    AU    UpdateDownloadProperties: 0 download(s) are still in progress.
    2015-01-06    11:00:10:031    1060    77c    AU    Setting AU scheduled install time to 2015-01-07 05:30:00
    2015-01-06    11:00:10:031    1060    77c    AU    Successfully wrote event for AU health state:0
    2015-01-06    11:00:55:817    1060    1748    PT    WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2015-01-06    11:00:55:818    1060    1748    PT    WARNING: SOAP Fault: 0x00012c
    2015-01-06    11:00:55:818    1060    1748    PT    WARNING:     faultstring:Fault occurred
    2015-01-06    11:00:55:818    1060    1748    PT    WARNING:     ErrorCode:ConfigChanged(2)
    2015-01-06    11:00:55:818    1060    1748    PT    WARNING:     Message:(null)
    2015-01-06    11:00:55:818    1060    1748    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2015-01-06    11:00:55:818    1060    1748    PT    WARNING:     ID:613a8761-a36c-4060-aaab-6546876b89b9
    2015-01-06    11:00:55:927    1060    1748    PT    WARNING: Cached cookie has expired or new PID is available
    2015-01-06    11:00:55:928    1060    1748    PT    Initializing simple targeting cookie, clientId = a788c530-2b29-4113-81e6-381a1751ada9, target group = , DNS name = a12300.mydomain.com
    2015-01-06    11:00:55:928    1060    1748    PT      Server URL = http://abcd.mydomain.com:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING: SOAP Fault: 0x00012c
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING:     faultstring:Fault occurred
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING:     ErrorCode:InvalidParameters(7)
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING:     Message:parameters.OtherCachedUpdateIDs
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING:     ID:419be3b9-9d9d-4ae4-96a5-8474e8f20149
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING: PTError: 0x8024400d
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING: Sync of Updates: 0x8024400d
    2015-01-06    11:00:56:596    1060    1748    PT    WARNING: SyncServerUpdatesInternal failed: 0x8024400d
    2015-01-06    11:00:56:596    1060    1748    Agent      * WARNING: Failed to synchronize, error = 0x8024400D
    2015-01-06    11:00:56:641    1060    1748    Agent      * WARNING: Exit code = 0x8024400D
    2015-01-06    11:00:56:641    1060    1748    Agent    *********
    2015-01-06    11:00:56:641    1060    1748    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-01-06    11:00:56:641    1060    1748    Agent    *************
    2015-01-06    11:00:56:641    1060    1748    Agent    WARNING: WU client failed Searching for update with error 0x8024400d
    2015-01-06    11:00:56:716    1060    13a8    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {DD87B2A6-D0E1-4EED-8074-72913BCE30F6}]
    2015-01-06    11:00:56:716    1060    13a8    AU      # WARNING: Search callback failed, result = 0x8024400D
    2015-01-06    11:00:56:716    1060    13a8    AU      # WARNING: Failed to find updates with error code 8024400D
    2015-01-06    11:00:56:716    1060    13a8    AU    #########
    2015-01-06    11:00:56:716    1060    13a8    AU    ##  END  ##  AU: Search for updates [CallId = {DD87B2A6-D0E1-4EED-8074-72913BCE30F6}]
    2015-01-06    11:00:56:716    1060    13a8    AU    #############
    2015-01-06    11:00:56:716    1060    1748    Report    CWERReporter finishing event handling. (00000000)
    2015-01-06    11:00:56:716    1060    13a8    AU    Successfully wrote event for AU health state:0
    2015-01-06    11:00:56:716    1060    13a8    AU    AU setting next detection timeout to 2015-01-06 10:30:56
    2015-01-06    11:00:56:716    1060    13a8    AU    Setting AU scheduled install time to 2015-01-07 05:30:00
    2015-01-06    11:00:56:716    1060    13a8    AU    Successfully wrote event for AU health state:0
    2015-01-06    11:00:56:729    1060    13a8    AU    Successfully wrote event for AU health state:0
    2015-01-06    11:01:01:641    1060    1748    Report    REPORT EVENT: {8F123F5A-55F5-4C8C-AB4A-6F1D31C2C794}    2015-01-06 11:00:56:641+0530    1    148    101    {00000000-0000-0000-0000-000000000000}    0    8024400d    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x8024400d.
    2015-01-06    11:01:01:655    1060    1748    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2015-01-06    11:01:01:655    1060    1748    Report    WER Report sent: 7.6.7600.256 0x8024400d 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2015-01-06    11:01:01:656    1060    1748    Report    CWERReporter finishing event handling. (00000000)

    I would like to add few more details about the issue. Among 150 clients 6 clients are reporting properly, few reported on Dec 25th, and few on Dec 3rd. So the issue might be complicated..

    i have 3sites, i noticed this issue on two sites( i mean pc's reporting to that site downstream servers) are got effected..

    Please help me :(



    • Edited by Naresh_TIS Tuesday, January 6, 2015 7:49 AM
    Tuesday, January 6, 2015 5:44 AM
    • Proposed as answer by Umesh S K Tuesday, January 6, 2015 6:06 AM
    • Unproposed as answer by Umesh S K Tuesday, January 6, 2015 11:53 AM
    Tuesday, January 6, 2015 6:00 AM
  • Hi Naresh,

    In addition, I can also see WARNING: SOAP Fault: 0x00012c in your log. Please perform the below steps in client machine and see if it helps.

    1) Stop WMI service.

    2)Rename "repository" folder in C:\windows\system32\wbem to "repository.old"

    3)Start WMI service.

    4)WUAUCLT /resetauthorization  /detectnow

    Thanks,

    Umesh.S.K

    • Proposed as answer by Umesh S K Tuesday, January 6, 2015 6:06 AM
    • Unproposed as answer by Umesh S K Tuesday, January 6, 2015 11:53 AM
    Tuesday, January 6, 2015 6:06 AM
  • No Luck Umesh, i already tried this :(
    • Edited by Naresh_TIS Tuesday, January 6, 2015 7:23 AM
    Tuesday, January 6, 2015 6:32 AM
  • There is no chance of reporting the client to a different server as we inject the reporting server address in the registry
    Tuesday, January 6, 2015 6:44 AM
  • Hi Naresh,

    Winerror for  0x00012c refers to "ERROR_OPLOCK_NOT_GRANTED The oplock request is denied". Can you perform the below action on one of the clinet machine and see if it helps?

    https://support.microsoft.com/kb/903262?wa=wsignin1.0

    1. delete the SusClientID and SusClientIDValidation registry values from a test computer,
    2. run the command wuauclt /resetauthorization /detectnow,
    3. wait 15 minutes,
    4. and then review the new entries in the WindowsUpdate.log

    Also.. you need to go back and re-evaluate the changes you made to IIS attempting to troubleshoot the previous problem and ensure that IIS is, in fact, properly configured.

    First, we need to verify that the IIS Authentication configuration is correctly set. The correct Authentication Settings are documented in the WSUS Technical Reference Guide in the link http://technet.microsoft.com/en-us/library/dd939903(v=ws.10).aspx (the settings are identical for WSUS v6).

    Thanks,

    Umesh.S.K

    • Proposed as answer by Umesh S K Tuesday, January 6, 2015 9:08 AM
    • Unproposed as answer by Umesh S K Tuesday, January 6, 2015 11:53 AM
    Tuesday, January 6, 2015 9:07 AM
  • Hi Umesh,

    I tried this one too.. i have a batch file which i use regularly.

    And i have gone through the IIS settings too.. but sill the same :(

    REG Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId  /f
    REG Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIdValidation  /f
    REG Add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v WUServer /t REG_SZ /d http://abcd.mydomain.com:8530 /F
    REG Add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v WUStatusServer /t REG_SZ /d http://abcd.mydomain.com:8530 /F


    gpupdate
    net stop wuauserv /y
    net stop BITS /y
    rd C:\WINDOWS\SoftwareDistribution /s /Q
    del "c:\windows\windowsupdate.log"
    regsvr32 WUAPI.DLL /s
    regsvr32 WUAUENG.DLL /s
    regsvr32 WUAUENG1.DLL /s
    regsvr32 ATL.DLL /s
    regsvr32 WUCLTUI.DLL /s
    regsvr32 WUPS.DLL /s
    regsvr32 WUPS2.DLL /s
    regsvr32 WUWEB.DLL /s
    regsvr32 msxml3.dll /s
    regsvr32 initpki.dll /s
    regsvr32 softpub.dll /s
    net start wuauserv /y
    wuauclt.exe /resetauthorization /detectnow
    reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
    REG add HKLM\SYSTEM\CurrentControlSet\services\BITS /v Start /t REG_DWORD /d 2 /f
    net start BITS /y
    wuauclt /reportnow


    • Edited by Naresh_TIS Tuesday, January 6, 2015 11:39 AM
    Tuesday, January 6, 2015 11:39 AM
  • Hi Naresh,

    How about installing windows updates directly from Microsoft repository instead of WSUS server on client machine? Do you see the same problem? Is windows firewall on client is turned ON ?

    Thanks,

    Umesh.S.K

    Tuesday, January 6, 2015 11:52 AM
  • i didnt try that, but will it help in resolving the issue ?
    Tuesday, January 6, 2015 12:06 PM
  • Hi Naresh,

    Please give a try. Also, please let us know if WSUS server is successfully sychronizing with Microsoft repository.

    Thanks,

    Umesh.S.K

    Tuesday, January 6, 2015 12:33 PM
  • From MS, client able get the updates..

    They is no sync issues between WSUS server and MS repo...


    • Edited by Naresh_TIS Tuesday, January 6, 2015 1:20 PM
    Tuesday, January 6, 2015 1:15 PM
  • Hi Naresh,

    I did some research for the error code 0x8024400d. As per http://support.microsoft.com/kb/938205

    WU_E_PT_SOAP_CLIENT --  SOAP_E_CLIENT - SOAP client found the message was malformed; fix before resending.

    SOAP protocol helps allowing the communication between server and client application over HTTP ( or any other protocol infact.). It looks like, there is a issue with this communication. As there are many clients having problem communicating with WSUS server, I suspect problem is with WSUS server.  I would ask you ask you to perform the below actions on WSUS server. 

    1)Restart WSUS website in IIS.

    2)Install latest WSUS service pack.

    2) wsusutil checkhealth. Check in event log for any errors or warnings.

    4)Restart WSUS server.

    After performing the above actions, please run

    wuauclt /resetauthorization /detectnow on client pc and see if it helps.

    Thanks,

    Umesh.S.K


    • Edited by Umesh S K Wednesday, January 7, 2015 5:57 AM
    Tuesday, January 6, 2015 3:25 PM
  • I am getting only this error in the event log

    Many client computers have not reported back to the server in the last 30 days. 66 have been detected so far.

    • Edited by Naresh_TIS Tuesday, January 6, 2015 4:31 PM
    Tuesday, January 6, 2015 4:03 PM
  • One more thing, when i try to check for updates this time it gave me different ID in the error.

    Okay. Then I'm going to shift my presumption that the GUID is not an UpdateID, and we'll abandon that line of thought.

    Returning to basics.... the 0x8024400D error is most often encountered with duplicate SusClientIDs, but in such cases, the WARNING associated with that condition is not an "Invalid Parameters" exception, but rather a "ConfigChanged" exception.

    Nonetheless, we should definitely rule out duplicate SusClientIDs.

    Among 150 clients 6 clients are reporting properly, few reported on Dec 25th, and few on Dec 3rd

    And always these same six clients?

    What is *different* or *special* about these six clients???

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, January 6, 2015 4:46 PM
    Moderator
  • Yes always those 6 machines.. And there is nothing different in those machine.. Operating system is same, they are in the same AD container, so same group policies will apply with other machines.. Thats why the issue looks to be bit complicated .. i am not able to come to the conclusion, whether server or client issue ... :(

    If you are ok, i will share my screen.. So that you can have a look

    • Edited by Naresh_TIS Tuesday, January 6, 2015 5:02 PM
    Tuesday, January 6, 2015 5:00 PM
  • These are recent sql error logs..

    2015-01-05 13:16:07.89 Server      Microsoft SQL Server 2005 - 9.00.5000.00 (X64)
        Dec 10 2010 10:38:40
        Copyright (c) 1988-2005 Microsoft Corporation
        Windows Internal Database (64-bit) on Windows NT 6.0 (Build 6002: Service Pack 2)

    2015-01-05 13:16:07.90 Server      (c) 2005 Microsoft Corporation.
    2015-01-05 13:16:07.90 Server      All rights reserved.
    2015-01-05 13:16:07.90 Server      Server process ID is 1588.
    2015-01-05 13:16:07.90 Server      Authentication mode is WINDOWS-ONLY.
    2015-01-05 13:16:07.90 Server      Logging SQL Server messages in file 'C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG'.
    2015-01-05 13:16:07.90 Server      This instance of SQL Server last reported using a process ID of 1624 at 1/5/2015 1:14:35 PM (local) 1/5/2015 7:44:35 AM (UTC). This is an informational message only; no user action is required.
    2015-01-05 13:16:07.90 Server      Registry startup parameters:
    2015-01-05 13:16:07.92 Server           -d C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf
    2015-01-05 13:16:07.92 Server           -e C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG
    2015-01-05 13:16:07.92 Server           -l C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf
    2015-01-05 13:16:07.96 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2015-01-05 13:16:07.96 Server      Detected 2 CPUs. This is an informational message; no user action is required.
    2015-01-05 13:16:09.59 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2015-01-05 13:16:10.34 Server      Database mirroring has been enabled on this instance of SQL Server.
    2015-01-05 13:16:10.42 spid5s      Starting up database 'master'.
    2015-01-05 13:16:10.70 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2015-01-05 13:16:10.84 spid5s      SQL Trace ID 1 was started by login "sa".
    2015-01-05 13:16:10.85 spid5s      Starting up database 'mssqlsystemresource'.
    2015-01-05 13:16:10.90 spid5s      The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
    2015-01-05 13:16:12.65 spid8s      Starting up database 'model'.
    2015-01-05 13:16:12.67 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query ].
    2015-01-05 13:16:12.67 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
    2015-01-05 13:16:12.68 spid5s      Server name is 'abcd\MICROSOFT##SSEE'. This is an informational message only. No user action is required.
    2015-01-05 13:16:12.68 spid5s      Starting up database 'msdb'.
    2015-01-05 13:16:12.68 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2015-01-05 13:17:23.53 spid8s      Clearing tempdb database.
    2015-01-05 13:17:23.83 spid8s      Starting up database 'tempdb'.
    2015-01-05 13:17:23.89 spid5s      Recovery is complete. This is an informational message only. No user action is required.
    2015-01-05 13:17:23.99 spid11s     The Service Broker protocol transport is disabled or not configured.
    2015-01-05 13:17:23.99 spid11s     The Database Mirroring protocol transport is disabled or not configured.
    2015-01-05 13:17:24.11 spid11s     Service Broker manager has started.
    2015-01-05 13:19:01.45 spid51      Starting up database 'SUSDB'.
    2015-01-05 13:19:02.48 spid51      Recovery is writing a checkpoint in database 'SUSDB' (5). This is an informational message only. No user action is required.

    Tuesday, January 6, 2015 5:27 PM
  • Lawrence, Just now i saw your slides and interview, it was great :)

    http://www.slideshare.net/SolarWinds/common-wsus-errors-codes-decoded-and-resolved

    these are few iis logs, check if help full

    015-01-06 13:23:54 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 1468
    2015-01-06 13:23:54 ::1 POST /ApiRemoting30/WebService.asmx - 8530 INDIA\knkumar ::1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4253) 200 0 0 0
    2015-01-06 13:23:55 ::1 POST /ApiRemoting30/WebService.asmx - 8530 INDIA\knkumar ::1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4253) 200 0 0 0
    2015-01-06 13:23:55 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 1390
    2015-01-06 13:23:57 ::1 POST /ApiRemoting30/WebService.asmx - 8530 INDIA\knkumar ::1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4253) 200 0 0 0
    2015-01-06 13:23:57 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 1484
    2015-01-06 13:23:59 ::1 POST /ApiRemoting30/WebService.asmx - 8530 INDIA\knkumar ::1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4253) 200 0 0 0
    2015-01-06 13:24:01 ::1 POST /ApiRemoting30/WebService.asmx - 8530 INDIA\knkumar ::1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4253) 200 0 0 0
    2015-01-06 13:24:03 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 4390
    2015-01-06 13:24:04 ::1 POST /ApiRemoting30/WebService.asmx - 8530 INDIA\knkumar ::1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4253) 200 0 0 0
    2015-01-06 13:24:07 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 3781
    2015-01-06 13:24:09 ::1 POST /ApiRemoting30/WebService.asmx - 8530 INDIA\knkumar ::1 Mozilla/4.0+

    2015-01-06 13:26:31 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 5968
    2015-01-06 13:26:38 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 5765
    2015-01-06 13:26:42 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 3265
    2015-01-06 13:26:45 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 1531
    2015-01-06 13:26:47 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 1812
    2015-01-06 13:26:49 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 1562
    2015-01-06 13:26:54 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 4296
    2015-01-06 13:26:56 10.40.12.225 POST /ClientWebService/client.asmx - 8530 - 172.16.1.14 Windows-Update-Agent 200 0 0 1781


    • Edited by Naresh_TIS Tuesday, January 6, 2015 6:21 PM
    Tuesday, January 6, 2015 6:20 PM
  • Yes always those 6 machines.. And there is nothing different in those machine.. Operating system is same, they are in the same AD container, so same group policies will apply with other machines.. 

    Okay, Please do the following, once on one of the working machines, and once on one of the not-working machines, and then post both results in separate messages:

    1. Record the system time.
    2. Reboot the client. (If you cannot reboot it, restart the WindowsUpdate service.)
    3. Run this command from a Command Prompt: wuauclt /resetauthorization /detectnow.
    4. Wait =30= minutes.
    5. Starting with the first entry logged after the time recorded in Step #1, post ALL of the entries from the WindowsUpdate.log.

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, January 6, 2015 6:49 PM
    Moderator
  • Non-Working client

    2015-01-07    00:29:21:527    1048    121c    AU    ###########  AU: Uninitializing Automatic Updates  ###########
    2015-01-07    00:29:23:389    1048    121c    Agent    Sending shutdown notification to client
    2015-01-07    00:29:23:404    2060    15f4    COMAPI    WARNING: Received service shutdown/self-update notification.
    2015-01-07    00:29:23:486    1048    121c    Report    CWERReporter finishing event handling. (00000000)
    2015-01-07    00:29:23:796    1048    121c    Service    *********
    2015-01-07    00:29:23:796    1048    121c    Service    **  END  **  Service: Service exit [Exit code = 0x240001]
    2015-01-07    00:29:23:796    1048    121c    Service    *************
    2015-01-07    00:29:27:757    1048    570    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: +0530)  ===========
    2015-01-07    00:29:27:757    1048    570    Misc      = Process: C:\Windows\system32\svchost.exe
    2015-01-07    00:29:27:757    1048    570    Misc      = Module: c:\windows\system32\wuaueng.dll
    2015-01-07    00:29:27:757    1048    570    Service    *************
    2015-01-07    00:29:27:757    1048    570    Service    ** START **  Service: Service startup
    2015-01-07    00:29:27:757    1048    570    Service    *********
    2015-01-07    00:29:27:772    1048    570    Agent      * WU client version 7.6.7600.256
    2015-01-07    00:29:27:772    1048    570    Agent      * Base directory: C:\Windows\SoftwareDistribution
    2015-01-07    00:29:27:772    1048    570    Agent      * Access type: No proxy
    2015-01-07    00:29:27:772    1048    570    Agent      * Network state: Connected
    2015-01-07    00:29:30:628    1048    570    DtaStor    Default service for AU is {00000000-0000-0000-0000-000000000000}
    2015-01-07    00:29:30:639    1048    570    DtaStor    Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
    2015-01-07    00:29:30:643    1048    570    Agent    WARNING: Failed to read the service id for re-registration 0x80070002
    2015-01-07    00:29:30:643    1048    570    Agent    WARNING: Missing service entry in the backup data store; cleaning up
    2015-01-07    00:29:32:354    1048    a50    Report    CWERReporter::Init succeeded
    2015-01-07    00:29:32:354    1048    a50    Agent    ***********  Agent: Initializing Windows Update Agent  ***********
    2015-01-07    00:29:32:354    1048    a50    Agent    ***********  Agent: Initializing global settings cache  ***********
    2015-01-07    00:29:32:354    1048    a50    Agent      * WSUS server: http://abcd.mydomain.com:8530
    2015-01-07    00:29:32:354    1048    a50    Agent      * WSUS status server: http://abcd.mydomain.com:8530
    2015-01-07    00:29:32:354    1048    a50    Agent      * Target group: (Unassigned Computers)
    2015-01-07    00:29:32:354    1048    a50    Agent      * Windows Update access disabled: No
    2015-01-07    00:29:32:354    1048    a50    DnldMgr    Download manager restoring 0 downloads
    2015-01-07    00:29:32:355    1048    570    Agent    Created new random SusClientId ad09b39e-0c12-484b-83c5-972e92868426. Old Id: none.
    2015-01-07    00:29:32:355    1048    570    Report    ***********  Report: Initializing static reporting data  ***********
    2015-01-07    00:29:32:355    1048    570    Report      * OS Version = 6.1.7601.1.0.65792
    2015-01-07    00:29:32:355    1048    570    Report      * OS Product Type = 0x00000004
    2015-01-07    00:29:32:355    1048    a50    AU    ###########  AU: Initializing Automatic Updates  ###########
    2015-01-07    00:29:32:355    1048    a50    AU      # WSUS server: http://abcd.mydomain.com:8530
    2015-01-07    00:29:32:355    1048    a50    AU      # Detection frequency: 22
    2015-01-07    00:29:32:355    1048    a50    AU      # Approval type: Scheduled (Policy)
    2015-01-07    00:29:32:355    1048    a50    AU      # Scheduled install day/time: Every day at 11:00
    2015-01-07    00:29:32:355    1048    a50    AU      # Auto-install minor updates: Yes (Policy)
    2015-01-07    00:29:32:355    1048    a50    AU      # Will interact with non-admins (Non-admins are elevated (User preference))
    2015-01-07    00:29:32:356    1048    a50    AU    Setting AU scheduled install time to 2015-01-07 05:30:00
    2015-01-07    00:29:32:418    1048    570    Report      * Computer Brand = Dell Inc.
    2015-01-07    00:29:32:418    1048    570    Report      * Computer Model = Latitude E5430 non-vPro
    2015-01-07    00:29:32:419    1048    570    Report      * Bios Revision = A11
    2015-01-07    00:29:32:419    1048    570    Report      * Bios Name = BRCM MBA Slot 0C00 v15.0.12
    2015-01-07    00:29:32:420    1048    570    Report      * Bios Release Date = 2013-05-20T00:00:00
    2015-01-07    00:29:32:420    1048    570    Report      * Locale ID = 1033
    2015-01-07    00:29:32:432    1048    a50    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:29:32:433    1048    a50    AU    Initializing featured updates
    2015-01-07    00:29:32:433    1048    a50    AU    Found 0 cached featured updates
    2015-01-07    00:29:32:433    1048    a50    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:29:32:433    1048    a50    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:29:32:433    1048    a50    AU    AU finished delayed initialization
    2015-01-07    00:29:32:433    1048    a50    AU    Triggering AU detection through DetectNow API
    2015-01-07    00:29:32:433    1048    a50    AU    Triggering Online detection (non-interactive)
    2015-01-07    00:29:32:434    1048    570    AU    #############
    2015-01-07    00:29:32:434    1048    570    AU    ## START ##  AU: Search for updates
    2015-01-07    00:29:32:434    1048    570    AU    #########
    2015-01-07    00:29:32:496    1048    570    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {60F2E171-A5AD-43E0-ABCB-7558C3648A87}]
    2015-01-07    00:29:32:496    1048    62c    Agent    *************
    2015-01-07    00:29:32:496    1048    62c    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-01-07    00:29:32:505    1048    62c    Agent    *********
    2015-01-07    00:29:32:505    1048    62c    Agent      * Online = Yes; Ignore download priority = No
    2015-01-07    00:29:32:505    1048    62c    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"
    2015-01-07    00:29:32:505    1048    62c    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2015-01-07    00:29:32:505    1048    62c    Agent      * Search Scope = {Machine}
    2015-01-07    00:29:32:518    1048    62c    Setup    Checking for agent SelfUpdate
    2015-01-07    00:29:32:518    1048    62c    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2015-01-07    00:31:05:363    1048    62c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2015-01-07    00:31:05:372    1048    62c    Misc     Microsoft signed: Yes
    2015-01-07    00:31:05:619    1048    62c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2015-01-07    00:31:05:627    1048    62c    Misc     Microsoft signed: Yes
    2015-01-07    00:31:05:690    1048    62c    Setup    Determining whether a new setup handler needs to be downloaded
    2015-01-07    00:31:05:690    1048    62c    Setup    SelfUpdate handler is not found.  It will be downloaded
    2015-01-07    00:31:05:690    1048    62c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-07    00:31:05:702    1048    62c    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-07    00:31:05:702    1048    62c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-07    00:31:05:717    1048    62c    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-07    00:31:05:717    1048    62c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2015-01-07    00:31:05:739    1048    62c    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2015-01-07    00:31:05:739    1048    62c    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2015-01-07    00:31:05:817    1048    62c    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2015-01-07    00:31:05:817    1048    62c    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://abcd.mydomain.com:8530/ClientWebService/client.asmx
    2015-01-07    00:31:05:898    1048    62c    Agent    Switching to hardware-verified ClientId.
    2015-01-07    00:31:05:955    1048    62c    PT    WARNING: Cached cookie has expired or new PID is available
    2015-01-07    00:31:06:577    1048    62c    Agent    Created new random SusClientId 92e513eb-05da-47af-be7c-d981d08dec9b. Old Id: ad09b39e-0c12-484b-83c5-972e92868426.
    2015-01-07    00:31:06:577    1048    62c    PT    Initializing simple targeting cookie, clientId = 92e513eb-05da-47af-be7c-d981d08dec9b, target group = , DNS name = a12300.mydomain.com
    2015-01-07    00:31:06:577    1048    62c    PT      Server URL = http://abcd.mydomain.com:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-01-07    00:38:50:191    1048    62c    PT    WARNING: Exceeded max server round trips: 0x80244010
    2015-01-07    00:38:50:192    1048    62c    PT    WARNING: Sync of Updates: 0x80244010
    2015-01-07    00:38:50:192    1048    62c    PT    WARNING: SyncServerUpdatesInternal failed: 0x80244010
    2015-01-07    00:38:50:192    1048    62c    Agent      * WARNING: Failed to synchronize, error = 0x80244010
    2015-01-07    00:38:50:192    1048    62c    Agent      * WARNING: Exit code = 0x80244010
    2015-01-07    00:38:50:192    1048    62c    Agent    *********
    2015-01-07    00:38:50:192    1048    62c    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-01-07    00:38:50:192    1048    62c    Agent    *************
    2015-01-07    00:38:50:192    1048    62c    Agent    WARNING: WU client failed Searching for update with error 0x80244010
    2015-01-07    00:38:50:223    1048    b44    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {60F2E171-A5AD-43E0-ABCB-7558C3648A87}]
    2015-01-07    00:38:50:223    1048    b44    AU      # WARNING: Search callback failed, result = 0x80244010
    2015-01-07    00:38:50:223    1048    b44    AU      # WARNING: Failed to find updates with error code 80244010
    2015-01-07    00:38:50:223    1048    b44    AU    #########
    2015-01-07    00:38:50:223    1048    b44    AU    ##  END  ##  AU: Search for updates [CallId = {60F2E171-A5AD-43E0-ABCB-7558C3648A87}]
    2015-01-07    00:38:50:223    1048    b44    AU    #############
    2015-01-07    00:38:50:224    1048    b44    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:38:50:224    1048    b44    AU    AU setting next detection timeout to 2015-01-07 00:08:50
    2015-01-07    00:38:50:224    1048    b44    AU    Setting AU scheduled install time to 2015-01-07 05:30:00
    2015-01-07    00:38:50:224    1048    b44    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:38:50:225    1048    b44    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:38:50:757    1048    62c    Report    CWERReporter finishing event handling. (00000000)
    2015-01-07    00:38:50:758    1048    62c    Report    REPORT EVENT: {D4368135-CA4D-4A8D-BC91-D9EF2A12E138}    2015-01-07 00:38:50:192+0530    1    148    101    {00000000-0000-0000-0000-000000000000}    0    80244010    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80244010.
    2015-01-07    00:38:50:858    1048    62c    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2015-01-07    00:38:50:858    1048    62c    Report    WER Report sent: 7.6.7600.256 0x80244010 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2015-01-07    00:38:50:858    1048    62c    Report    CWERReporter finishing event handling. (00000000)
    2015-01-07    00:38:51:466    1048    62c    Report    Uploading 1 events using cached cookie, reporting URL = http://abcd.mydomain.com:8530/ReportingWebService/ReportingWebService.asmx
    2015-01-07    00:38:51:551    1048    62c    Report    Reporter successfully uploaded 1 events.
    2015-01-07    00:38:55:225    1048    62c    Report    CWERReporter finishing event handling. (00000000)


    • Edited by Naresh_TIS Tuesday, January 6, 2015 9:18 PM
    Tuesday, January 6, 2015 9:15 PM
  • Working client log

    2015-01-07    00:29:14:445     960    410    AU    ###########  AU: Uninitializing Automatic Updates  ###########
    2015-01-07    00:30:01:401    1304    558    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: +0530)  ===========
    2015-01-07    00:30:01:401    1304    558    Misc      = Process: c:\Program Files\Microsoft Forefront\Client Security\Client\SSA\FcsSas.exe
    2015-01-07    00:30:01:401    1304    558    Misc      = Module: C:\Windows\system32\wuapi.dll
    2015-01-07    00:30:01:370    1304    558    COMAPI    FATAL: Unable to connect to the service (hr=8007045B)
    2015-01-07    00:30:01:416    1304    558    COMAPI    WARNING: Unable to successfully terminate connection to the service, hr=8007045B
    2015-01-07    00:33:34:817     960    ad4    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: +0530)  ===========
    2015-01-07    00:33:34:833     960    ad4    Misc      = Process: C:\Windows\system32\svchost.exe
    2015-01-07    00:33:34:849     960    ad4    Misc      = Module: c:\windows\system32\wuaueng.dll
    2015-01-07    00:33:34:817     960    ad4    Service    *************
    2015-01-07    00:33:34:880     960    ad4    Service    ** START **  Service: Service startup
    2015-01-07    00:33:34:896     960    ad4    Service    *********
    2015-01-07    00:33:36:009     960    ad4    Agent      * WU client version 7.6.7600.256
    2015-01-07    00:33:36:009     960    ad4    Agent      * Base directory: C:\Windows\SoftwareDistribution
    2015-01-07    00:33:36:024     960    ad4    Agent      * Access type: No proxy
    2015-01-07    00:33:36:056     960    ad4    Agent      * Network state: Connected
    2015-01-07    00:34:24:432     960    ad4    Report    CWERReporter::Init succeeded
    2015-01-07    00:34:24:432     960    ad4    Agent    ***********  Agent: Initializing Windows Update Agent  ***********
    2015-01-07    00:34:24:432     960    ad4    Agent    ***********  Agent: Initializing global settings cache  ***********
    2015-01-07    00:34:24:432     960    ad4    Agent      * WSUS server: http://abcd.mydomain.com:8530
    2015-01-07    00:34:24:432     960    ad4    Agent      * WSUS status server: http://abcd.mydomain.com:8530
    2015-01-07    00:34:24:432     960    ad4    Agent      * Target group: (Unassigned Computers)
    2015-01-07    00:34:24:432     960    ad4    Agent      * Windows Update access disabled: No
    2015-01-07    00:34:24:448     960    ad4    DnldMgr    Download manager restoring 0 downloads
    2015-01-07    00:34:24:464     960    ad4    AU    ###########  AU: Initializing Automatic Updates  ###########
    2015-01-07    00:34:24:464     960    ad4    AU      # WSUS server: http://abcd.mydomain.com:8530
    2015-01-07    00:34:24:464     960    ad4    AU      # Detection frequency: 22
    2015-01-07    00:34:24:464     960    ad4    AU      # Approval type: Scheduled (Policy)
    2015-01-07    00:34:24:464     960    ad4    AU      # Scheduled install day/time: Every day at 11:00
    2015-01-07    00:34:24:464     960    ad4    AU      # Auto-install minor updates: Yes (Policy)
    2015-01-07    00:34:24:464     960    ad4    AU      # Will interact with non-admins (Non-admins are elevated (User preference))
    2015-01-07    00:34:24:542     960    ad4    AU    Setting AU scheduled install time to 2015-01-07 05:30:00
    2015-01-07    00:34:25:028     960    ad4    Report    ***********  Report: Initializing static reporting data  ***********
    2015-01-07    00:34:25:028     960    ad4    Report      * OS Version = 6.1.7601.1.0.65792
    2015-01-07    00:34:25:028     960    ad4    Report      * OS Product Type = 0x00000004
    2015-01-07    00:34:25:044     960    ad4    Report      * Computer Brand = VMware, Inc.
    2015-01-07    00:34:25:044     960    ad4    Report      * Computer Model = VMware Virtual Platform
    2015-01-07    00:34:25:044     960    ad4    Report      * Bios Revision = 6.00
    2015-01-07    00:34:25:044     960    ad4    Report      * Bios Name = PhoenixBIOS 4.0 Release 6.0     
    2015-01-07    00:34:25:044     960    ad4    Report      * Bios Release Date = 2013-07-30T00:00:00
    2015-01-07    00:34:25:044     960    ad4    Report      * Locale ID = 1033
    2015-01-07    00:34:25:138     960    ad4    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:34:25:138     960    ad4    AU    Initializing featured updates
    2015-01-07    00:34:25:138     960    ad4    AU    Found 0 cached featured updates
    2015-01-07    00:34:25:138     960    ad4    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:34:25:169     960    ad4    AU    Successfully wrote event for AU health state:0
    2015-01-07    00:34:25:169     960    ad4    AU    AU finished delayed initialization
    2015-01-07    00:34:30:201     960    778    Report    CWERReporter finishing event handling. (00000000)
    2015-01-07    01:03:29:607     960    a58    AU    Getting featured update notifications.  fIncludeDismissed = true
    2015-01-07    01:03:29:607     960    a58    AU    No featured updates available.

    Tuesday, January 6, 2015 9:21 PM
  • 2015-01-07 00:38:50:191 1048 62c PT WARNING: Exceeded max server round trips: 0x80244010

    This machine is suffering from a condition I've not seen for a while, and even today quite unusual for a Windows 7 Service Pack 1 machine, although certainly not impossible given the four years of updates involved in this process.

    Essentially the deal here is the number of round trips to transfer update metadata has a cap. The WUA is hitting that cap. Until it can fully cache all of the relevant update metadata, it will continue to hit this cap. You can likely expedite getting the metadata fully cached by running some repeated detection events, and monitoring the logfile until the "max server round trips" warning no longer occurs.

    You could also expedite it by reducing the Detection Frequency to a value in the 2-4 hour range for a few days.

    There's an excellent description of this condition in the WSUS Support Team Blog from September, 2008. See http://blogs.technet.com/b/sus/archive/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010.aspx


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, January 7, 2015 4:20 AM
    Moderator
  • Working client log

    Notice this logfile does not record the 0x80244010 WARNING.

    So, earlier, when I asked if there were any differences in these machines... this is what we were looking for. :-)


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, January 7, 2015 4:21 AM
    Moderator
  • But i am getting the error 0x80244010 only when i re-new the SUid's

    This the current log... It again shows the same error.. So i am suspecting the problem might be different .

    2015-01-07    11:07:36:872    1048    1fc8    AU    AU setting next detection timeout to 2015-01-07 10:37:36
    2015-01-07    11:07:36:872    1048    1fc8    AU    Setting AU scheduled install time to 2015-01-08 05:30:00
    2015-01-07    11:07:36:872    1048    1fc8    AU    Successfully wrote event for AU health state:0
    2015-01-07    11:07:36:887    1048    1fc8    AU    Successfully wrote event for AU health state:0
    2015-01-07    11:07:41:810    1048    15cc    Report    REPORT EVENT: {6845B461-EF54-4EB5-9883-BDD41C18F6A4}    2015-01-07 11:07:36:810+0530    1    148    101    {00000000-0000-0000-0000-000000000000}    0    8024400d    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x8024400d.
    2015-01-07    11:07:41:823    1048    15cc    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2015-01-07    11:07:41:823    1048    15cc    Report    WER Report sent: 7.6.7600.256 0x8024400d 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2015-01-07    11:07:41:824    1048    15cc    Report    CWERReporter finishing event handling. (00000000)

    Wednesday, January 7, 2015 5:41 AM
  • Hi Naresh,

    Did you restart WSUS website in IIS as I mentioned earlier? Can we know if you have latest service pack installed for WSUS? Also, you can give a reboot of WSUS server once. I think restarting WSUS website or server will not have impact on your production environment.

    Thanks,

    Umesh.S.K

    Wednesday, January 7, 2015 6:02 AM
  • From past two days i have rebooted the server many times...

    Which service pack you are asking about ?

    Wednesday, January 7, 2015 6:38 AM
  • Hi Naresh,

    Can you run "wsusutil checkhealth" on WSUS server and see if it logs any error event log? I was talking about service pack for WSUS.

    Thanks,

    Umesh.S.K

    Wednesday, January 7, 2015 7:57 AM
  • Umesh,

    As i said earlier i am getting only this error when i run it.

    Many client computers have not reported back to the server in the last 30 days. 66 have been detected so far.

    And i havnt installed any recent patches for WSUS

    Thanks,

    Naresh

    Wednesday, January 7, 2015 9:02 AM
  • I am thinking to re-index the wsus database.

    But i can see both up stream and replica servers using the common data base which is installed on another server. That server has sccm services.

    If i re-index the database will it impact the sccm services?

    Because again these replica servers are the secondary sites for the sccm server.

    Please suggest me.

    Thanks,

    Naresh

    Wednesday, January 7, 2015 1:28 PM
  • But i am getting the error 0x80244010 only when i re-new the SUid's

    Okay.

    Why are you renewing the SUids?


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, January 7, 2015 4:26 PM
    Moderator
  • I am thinking to re-index the wsus database.

    While reindexing the database should be a part of your regular WSUS maintenance activities, it's NOT going to do anything at all about resolving an 0x80244010 condition. That condition is a statement of fact, and the only way to resolve it is to let the client work it out. (As is discussed in the blog post I cited.)

    But i can see both up stream and replica servers using the common data base which is installed on another server.

    Because again these replica servers are the secondary sites for the sccm server.

    This is exceptionally critical information that would have been very useful to know about in your original post.

    For assistance with managing Configuration Manager environments with redundant SUPs using a shared database, you need to ask in the Configuration Manager Security, Updates, and Compliance forum, where the ConfigMgr MVPs actually understand the quirks of this particular deployment scenario.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, January 7, 2015 4:39 PM
    Moderator
  • i just tried, if it works or not.. but no lock
    Wednesday, January 7, 2015 5:01 PM
  • So reindexing will work or not ?

    • Edited by Naresh_TIS Wednesday, January 7, 2015 5:14 PM
    Wednesday, January 7, 2015 5:02 PM
  • Issue got resolved only after reinstalling the wsus ...

    No other solution for google didn't helped...

    Friday, January 9, 2015 8:09 PM
  • Hello,

    Sorry to bump this up.

    We are facing similar issue.

    Our setup:

    Windows 2008 SCCM with SUP service and WSUS.

    Some clients updating, some others not.

    Clients not updating show in WindowsUpdate.log the infamous SyncUpdates failure, error = 0x8024400D, with ErrorCode:InvalidParameters(7) and Message:parameters.OtherCachedUpdateIDs.

    From what I've understood, that means that there is the OtherCachedUpdateIDs parameter passed to the SOAP is invalid.

    All the usual troubleshooting steps (deleting SusClientId  and other regkeys, reseting authorization, reinstalling the WSUS (twice),...) have not worked.

    On the other hand there is something curious:

    From a working client, I can reach https://FQDN:8351/selfupdate/wuident.cab without problems

    From a non-working client, I can reach http://FQDN/ whithout problems (shows standard IIS70 page), but I can NOT reach https://FQDN:8351/selfupdate/wuident.cab

    Working client features IE9, non-working IE11.

    Connected to same network.

    I can only think of things such as different windows firewall settings (not very probable) or proxy settings.

    Is there any othrer plausible cause for that?

    Thanks in advance!!

    Wednesday, March 18, 2015 9:53 AM
  • [Update]

    On the non-working machines I was writing the wrong URL (prot 8351 instead of 8531).

    The non-working machines are able to download the wuident.cab file.

    So network connectivity is discarded.

    Now I am in the same situation that Naresh, but reinstaling WSUS does not work for me. :(

    Wednesday, March 18, 2015 12:55 PM
  • Hi,

    Facing a similar issue. First it start happening only if updating directly from MS, now it starts also happening with local WSUS server

    One thing I've noticed, it will happen on workstations with many MS products (for example 3 different versions of MS Office)

    2015-04-15    09:31:37:409    1080    574    PT    WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2015-04-15    09:31:37:409    1080    574    PT    WARNING: SOAP Fault: 0x00012c
    2015-04-15    09:31:37:409    1080    574    PT    WARNING:     faultstring:Fault occurred
    2015-04-15    09:31:37:409    1080    574    PT    WARNING:     ErrorCode:InvalidParameters(7)
    2015-04-15    09:31:37:409    1080    574    PT    WARNING:     Message:parameters.OtherCachedUpdateIDs
    2015-04-15    09:31:37:409    1080    574    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2015-04-15    09:31:37:409    1080    574    PT    WARNING:     ID:2a489716-c1c2-4db4-8ca9-278d6b93d0d2
    2015-04-15    09:31:37:409    1080    574    PT    WARNING: PTError: 0x8024400d
    2015-04-15    09:31:37:409    1080    574    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
    2015-04-15    09:31:37:409    1080    574    PT    WARNING: Sync of Updates: 0x8024400d
    2015-04-15    09:31:37:409    1080    574    PT    WARNING: SyncServerUpdatesInternal failed: 0x8024400d
    2015-04-15    09:31:37:409    1080    574    Agent      * WARNING: Failed to synchronize, error = 0x8024400D
    2015-04-15    09:31:37:409    1080    574    Agent      * WARNING: Exit code = 0x8024400D

    Wednesday, April 15, 2015 9:45 AM
  • I am facing similar issue. Did anyone got a solution of fix for the issue?

    Thanks in Advance!!

    Hitesh Jain

    Thursday, June 4, 2015 12:37 PM
  • Hi All,

    Actually, I just solved the same issue with Microsoft support, because reinstalling was not an option for me.

    It turns out, that in an environment, that has been running for too long, and has many different products syncronized in WSUS and installed on clients (for ex. multiple Office or other Microsoft product component versions), the updates accumulate over time. Once there are too many of them in WSUS, the checking of updates on client computers hits a limit configured in WSUS web services.

    In Your WSUS installation, you can find this limit in the file located most likely in C:\Program Files\Update Services\WebServices\clientwebservice\web.config.
    In that file there is a line:
    <add key="maxCachedUpdates" value="20000"/>
    Try increasing that value (in my case 26000 was enough), and see if it solves Your issue.

    The default value is 20000, but it does not mean that there are 20000 updates. It just depends on the way WSUS counts things. I did not get this info from MS, but I just guess that in the WindowsUpdate.log file (client computers C:\Windows\WindowsUpdate.log) you can find a line that shows how many "cached updates" is required, but they are called "deployed entities" here:
    Found 0 updates and 83 categories in search; evaluated appl. rules of 259 out of 20217 deployed entities.

    This is not Microsoft recommended solution, and should only be used as a temporary solution until the old and expired and superseded updates are cleaned from the WSUS. The actual solution is to use the script from this article:
    blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx
    Unfortunatelly, the cleanup script somehow did not work for me, but maybe I just had to wait more than an hour after the cleanup to see the results. If You have WSUS hierarchy, do the cleanup on the main and syncronize downstream servers.

    By the way, somehow Microsoft does not see this as a bug or at least a lack of documentation of required WSUS manual cleanup process. I guess that all of us should just know this stuff, it's basic, isn't it? :)

    Have a nice day!
    Vince

    • Proposed as answer by Kovacs Miklos Thursday, January 21, 2016 7:45 AM
    Monday, September 7, 2015 8:11 AM
  • Hi Vince,

    I can confirm your solution is working. However, in my case the failed systems didn't even get to the point to log how many updates they have, only writing the error:

    2016-01-20	00:47:41:553	1320	de80	PT	WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2016-01-20	00:47:41:553	1320	de80	PT	WARNING: SOAP Fault: 0x00012c
    2016-01-20	00:47:41:553	1320	de80	PT	WARNING:     faultstring:Fault occurred
    2016-01-20	00:47:41:553	1320	de80	PT	WARNING:     ErrorCode:InvalidParameters(7)
    2016-01-20	00:47:41:553	1320	de80	PT	WARNING:     Message:parameters.OtherCachedUpdateIDs
    2016-01-20	00:47:41:553	1320	de80	PT	WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2016-01-20	00:47:41:553	1320	de80	PT	WARNING:     ID:9260b54b-772a-41c6-9653-238ce538629a
    2016-01-20	00:47:41:553	1320	de80	PT	WARNING: PTError: 0x8024400d
    

    So I came to the same result as you by using Wireshark and check the value of the "OtherCachedUpdateIDs" parameter. But from that information it still wasn't clear, whether the high parameter value (20011) is causing the issue, so your comment ultimately ruled this out. Thank you!

    Miklos

    Thursday, January 21, 2016 7:45 AM
  • An alternative is probably a cleanup of the WSUS server and a subsequent deletion of the datastore.edb on the affected clients. We had the same issue (0x8024400D on a lot of machines) and it helped. The cleanup process was recently described in this blog: http://blogs.technet.com/b/configurationmgr/archive/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance.aspx.

    On the clients we ran

    net stop wuauserv

    del C:\Windows\SoftwareDistribution\DataStore\Datastore.edb

    net start wuauserv

    wuauclt /detectnow

    We saw error 0x80244010 until the database was fully rebuild but afterwards WUA was cured.

    Tuesday, February 16, 2016 4:54 PM
  • I confirm that it's the wsus MaxCachedUpdate value in the web.config file of WSUS or SCCM if using SCCM with WSUS.
    • Proposed as answer by emnavarro02 Friday, July 28, 2017 6:49 PM
    Monday, March 21, 2016 10:59 AM
  • Well this morning I am also having the same Error Report and unfortunately it has Refused to obtain the Updates, in the Windows Update Repair App it reads an Error 0x80070005 which is "Access Denied", usually a Case where the Clinton/Agent is Corrupt and unable to be repaired, in turn it usually means the Windows OS HAS to be Reinstalled due to the Agent Corruption, in turn it means the Latest Windows Update Agent completely Corrupts the Function making some Windows OSes think it is a Pirated Copy or invalided Copy, so that means it Bricks you from using the OS.
    Wednesday, April 13, 2016 1:17 PM
  • Dear Naresh,

    Many tanks for this batch, it was very usefull for me and solve my problem with WSUS and SCCM 2012

    Regards

    Jean Yves

    Friday, April 29, 2016 8:50 AM
  • This resolved my issue with my Windows 2016 update issue!

    I really appreciate your help!

    Thank you.

    Wednesday, May 24, 2017 6:23 PM
  • I confirm that changing MaxCachedUpdate solved my problem too.

    -- emnavarro02

    Friday, July 28, 2017 6:50 PM