locked
One computer with "This computer has not reported status yet" RRS feed

  • Question

  • Looking for some help on this, please?

    I have WSUS running on Windows Server 2008 R2. It has been running without issue for around a year, however I have one computer with the message of "This computer has not reported status yet".

    Here is the history so far:

    • Group policy has not changed and is being applied as expected
    • Computer has been restarted and server has been restarted
    • The server has had the latest updates applied, and another restart performed
    • Other computers which have been added recently, pick up WSUS updates
    • I have run wuauclt with the usual switches to reset authorization and to report in etc
    • Windowsupdate.log shows the correct path to get to the server and the registry reflects this too
    • I have installed the latest Windows update client on to the computer from Microsoft
    • I can manually install updates if I take the computer object out of the company Organisational Unit

    Here is what the windowsupdate.log says...

    2016-02-22 13:19:59:217 996 1e90 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2016-02-22 13:19:59:217 996 1e90 PT WARNING: SOAP Fault: 0x00012c
    2016-02-22 13:19:59:217 996 1e90 PT WARNING:     faultstring:Fault occurred
    2016-02-22 13:19:59:217 996 1e90 PT WARNING:     ErrorCode:InvalidParameters(7)
    2016-02-22 13:19:59:217 996 1e90 PT WARNING:     Message:parameters.OtherCachedUpdateIDs
    2016-02-22 13:19:59:217 996 1e90 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2016-02-22 13:19:59:217 996 1e90 PT WARNING:     ID:7ac50417-a2ef-40fe-b52b-23707ba63bd5
    2016-02-22 13:19:59:217 996 1e90 PT WARNING: PTError: 0x8024400d
    2016-02-22 13:19:59:217 996 1e90 PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
    2016-02-22 13:19:59:217 996 1e90 PT WARNING: Sync of Updates: 0x8024400d
    2016-02-22 13:19:59:217 996 1e90 PT WARNING: SyncServerUpdatesInternal failed: 0x8024400d
    2016-02-22 13:19:59:217 996 1e90 Agent  * WARNING: Failed to synchronize, error = 0x8024400D
    2016-02-22 13:19:59:217 996 1e90 Agent  * WARNING: Exit code = 0x8024400D
    2016-02-22 13:19:59:217 996 1e90 Agent *********
    2016-02-22 13:19:59:217 996 1e90 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-02-22 13:19:59:217 996 1e90 Agent *************
    2016-02-22 13:19:59:217 996 1e90 Agent WARNING: WU client failed Searching for update with error 0x8024400d
    2016-02-22 13:19:59:227 996 1878 AU >>##  RESUMED  ## AU: Search for updates [CallId = {8C404211-71C1-43F6-B7FA-E3ED2D07F33C}]
    2016-02-22 13:19:59:227 996 1878 AU  # WARNING: Search callback failed, result = 0x8024400D
    2016-02-22 13:19:59:227 996 1878 AU  # WARNING: Failed to find updates with error code 8024400D
    2016-02-22 13:19:59:227 996 1878 AU #########
    2016-02-22 13:19:59:227 996 1878 AU ##  END  ##  AU: Search for updates [CallId = {8C404211-71C1-43F6-B7FA-E3ED2D07F33C}]
    2016-02-22 13:19:59:227 996 1878 AU #############
    2016-02-22 13:19:59:227 996 1878 AU Successfully wrote event for AU health state:0
    2016-02-22 13:19:59:227 996 1878 AU AU setting next detection timeout to 2016-02-22 18:19:59
    2016-02-22 13:19:59:227 996 1878 AU Setting AU scheduled install time to 2016-02-27 23:00:00
    2016-02-22 13:19:59:227 996 1878 AU Successfully wrote event for AU health state:0
    2016-02-22 13:19:59:227 996 1878 AU Successfully wrote event for AU health state:0
    2016-02-22 13:20:04:218 996 1e90 Report REPORT EVENT: {C33323B4-768C-4408-A5FD-3BB146566846} 2016-02-22 13:19:59:217-0000 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400d AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400d.
    2016-02-22 13:20:04:238 996 1e90 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-02-22 13:20:04:238 996 1e90 Report WER Report sent: 7.6.7601.19116 0x8024400d(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2016-02-22 13:27:06:258 996 1e90 PT WARNING: Cached cookie has expired or new PID is available
    2016-02-22 13:27:06:258 996 1e90 PT Initializing simple targeting cookie, clientId = e705e617-058d-4470-9490-aa5555560399, target group = Workstations, DNS name = lon-cfpat-wks-037.cfpat.local
    2016-02-22 13:27:06:258 996 1e90 PT  Server URL = http://lon-cfpat-adm-001/SimpleAuthWebService/SimpleAuth.asmx
    2016-02-22 13:27:06:278 996 1e90 Report Uploading 1 events using cached cookie, reporting URL = http://lon-cfpat-adm-001/ReportingWebService/ReportingWebService.asmx
    2016-02-22 13:27:06:278 996 1e90 Report Reporter successfully uploaded 1 events.



    Monday, February 22, 2016 3:45 PM

Answers

All replies

  • Hi Reo,

    We may do the following things to check if it could work:

    1. On WSUS server, decline all expired updates and unused updates, then run server cleanup wizard;

    2. Use the following method to reindex WSUS database:

    https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).aspx

    3. On WSUS client, use to following method to reset window update component:

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

    4. Clean SoftwareDistribution folder on client:

    In cmd: run net stop wuauserv;

    Go to folder: C:\windows\SoftwareDistribution, rename SoftwareDistribution folder;

    In cmd: run net start wuauserv

    5. After finish the above steps, both restart WSUS server and WSUS client, check the result.

    Besides, we may run server cleanup wizard and reindex wsus database regularly, it may help WSUS server to work well.

    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.


    Tuesday, February 23, 2016 1:28 AM
  • All steps have been done. The issue remains, however.
    Tuesday, February 23, 2016 10:09 AM
  • Hi Reo,

    Then check windows update log on the client, maybe we can find something useful.

    Windows update log location: C:\Windows\WindowsUpdate.log

    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.

    Wednesday, February 24, 2016 4:17 AM
  •  
    2016-02-25 01:28:17:894 996 1f94 Report Uploading 1 events using cached cookie, reporting URL = http://lon-cfpat-adm-001/ReportingWebService/ReportingWebService.asmx
    2016-02-25 01:28:17:897 996 1f94 Report Reporter successfully uploaded 1 events.
    2016-02-25 04:50:12:051 6024 1cc4 Misc ===========  Logging initialized (build: 7.6.7601.19116, tz: -0000)  ===========
    2016-02-25 04:50:12:051 6024 1cc4 Misc  = Process: c:\program files\windows defender\MpCmdRun.exe
    2016-02-25 04:50:12:051 6024 1cc4 Misc  = Module: C:\Windows\system32\wuapi.dll
    2016-02-25 04:50:12:051 6024 1cc4 COMAPI -------------
    2016-02-25 04:50:12:051 6024 1cc4 COMAPI -- START --  COMAPI: Search [ClientId = Windows Defender]
    2016-02-25 04:50:12:051 6024 1cc4 COMAPI ---------
    2016-02-25 04:50:12:064 996 18ac Agent *************
    2016-02-25 04:50:12:064 6024 1cc4 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = Windows Defender]
    2016-02-25 04:50:12:064 996 18ac Agent ** START **  Agent: Finding updates [CallerId = Windows Defender]
    2016-02-25 04:50:12:064 996 18ac Agent *********
    2016-02-25 04:50:12:064 996 18ac Agent  * Online = Yes; Ignore download priority = No
    2016-02-25 04:50:12:064 996 18ac Agent  * Criteria = "(IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains '8c3fcc84-7410-4a95-8b89-a166a0190486' and CategoryIDs contains 'e0789628-ce08-4437-be74-2495b842f43b')"
    2016-02-25 04:50:12:064 996 18ac Agent  * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2016-02-25 04:50:12:064 996 18ac Agent  * Search Scope = {Machine}
    2016-02-25 04:50:12:129 996 18ac PT WARNING: Cached cookie has expired or new PID is available
    2016-02-25 04:50:12:129 996 18ac PT Initializing simple targeting cookie, clientId = e705e617-058d-4470-9490-aa5555560399, target group = Workstations, DNS name = lon-cfpat-wks-037.cfpartners.local
    2016-02-25 04:50:12:129 996 18ac PT  Server URL = http://lon-cfpat-adm-001/SimpleAuthWebService/SimpleAuth.asmx
    2016-02-25 04:50:14:707 996 18ac PT +++++++++++  PT: Starting category scan  +++++++++++
    2016-02-25 04:50:14:707 996 18ac PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lon-cfpat-adm-001/ClientWebService/client.asmx
    2016-02-25 04:50:14:746 996 18ac PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-02-25 04:50:14:746 996 18ac PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lon-cfpat-adm-001/ClientWebService/client.asmx
    2016-02-25 04:50:14:754 996 18ac PT WARNING: Cached cookie has expired or new PID is available
    2016-02-25 04:50:14:754 996 18ac PT Initializing simple targeting cookie, clientId = e705e617-058d-4470-9490-aa5555560399, target group = Workstations, DNS name = lon-cfpat-wks-037.cfpartners.local
    2016-02-25 04:50:14:754 996 18ac PT  Server URL = http://lon-cfpat-adm-001/SimpleAuthWebService/SimpleAuth.asmx
    2016-02-25 04:50:14:786 996 18ac Agent  * Found 0 updates and 3 categories in search; evaluated appl. rules of 3 out of 3 deployed entities
    2016-02-25 04:50:14:790 996 18ac Agent *********
    2016-02-25 04:50:14:790 996 18ac Agent **  END  **  Agent: Finding updates [CallerId = Windows Defender]
    2016-02-25 04:50:14:790 996 18ac Agent *************
    2016-02-25 04:50:14:791 6024 ffc COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = Windows Defender]
    2016-02-25 04:50:14:791 6024 ffc COMAPI  - Updates found = 0
    2016-02-25 04:50:14:791 6024 ffc COMAPI ---------
    2016-02-25 04:50:14:791 6024 ffc COMAPI --  END  --  COMAPI: Search [ClientId = Windows Defender]
    2016-02-25 04:50:14:791 6024 ffc COMAPI -------------
    2016-02-25 04:50:19:790 996 18ac Report REPORT EVENT: {9BCC12D8-B693-4CBC-A0C9-2D1C2984C354} 2016-02-25 04:50:14:790-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Defender Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2016-02-25 04:57:21:841 996 18ac Report Uploading 1 events using cached cookie, reporting URL = http://lon-cfpat-adm-001/ReportingWebService/ReportingWebService.asmx
    2016-02-25 04:57:21:846 996 18ac Report Reporter successfully uploaded 1 events.
    2016-02-25 06:21:11:049 996 944 AU #############
    2016-02-25 06:21:11:049 996 944 AU ## START ##  AU: Search for updates
    2016-02-25 06:21:11:049 996 944 AU #########
    2016-02-25 06:21:11:059 996 944 AU <<## SUBMITTED ## AU: Search for updates [CallId = {DA860910-0FAD-48D3-B931-CC44A9A0B81E}]
    2016-02-25 06:21:11:059 996 1bc8 Agent *************
    2016-02-25 06:21:11:059 996 1bc8 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-02-25 06:21:11:059 996 1bc8 Agent *********
    2016-02-25 06:21:11:059 996 1bc8 Agent  * Online = Yes; Ignore download priority = No
    2016-02-25 06:21:11:059 996 1bc8 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-02-25 06:21:11:059 996 1bc8 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-02-25 06:21:11:059 996 1bc8 Agent  * Search Scope = {Machine}
    2016-02-25 06:21:11:079 996 1bc8 Setup Checking for agent SelfUpdate
    2016-02-25 06:21:11:120 996 1bc8 Setup Client version: Core: 7.6.7601.19116  Aux: 7.6.7601.19116
    2016-02-25 06:21:13:386 996 1bc8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-02-25 06:21:13:395 996 1bc8 Misc Microsoft signed: NA
    2016-02-25 06:21:13:395 996 1bc8 Misc WARNING: Cab does not contain correct inner CAB file.
    2016-02-25 06:21:13:395 996 1bc8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-02-25 06:21:13:398 996 1bc8 Misc Microsoft signed: NA
    2016-02-25 06:21:13:415 996 1bc8 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
    2016-02-25 06:21:13:415 996 1bc8 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2016-02-25 06:21:13:415 996 1bc8 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-02-25 06:21:14:399 996 1bc8 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-02-25 06:21:14:399 996 1bc8 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lon-cfpat-adm-001/ClientWebService/client.asmx
    2016-02-25 06:21:14:410 996 1bc8 PT WARNING: Cached cookie has expired or new PID is available
    2016-02-25 06:21:14:410 996 1bc8 PT Initializing simple targeting cookie, clientId = e705e617-058d-4470-9490-aa5555560399, target group = Workstations, DNS name = lon-cfpat-wks-037.cfpartners.local
    2016-02-25 06:21:14:410 996 1bc8 PT  Server URL = http://lon-cfp-adm-001/SimpleAuthWebService/SimpleAuth.asmx
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING: SOAP Fault: 0x00012c
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING:     faultstring:Fault occurred
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING:     ErrorCode:InvalidParameters(7)
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING:     Message:parameters.OtherCachedUpdateIDs
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING:     ID:e604b1ec-e9ca-431d-8f67-4c49cecc1f6d
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING: PTError: 0x8024400d
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400d
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING: Sync of Updates: 0x8024400d
    2016-02-25 06:21:16:624 996 1bc8 PT WARNING: SyncServerUpdatesInternal failed: 0x8024400d
    2016-02-25 06:21:16:624 996 1bc8 Agent  * WARNING: Failed to synchronize, error = 0x8024400D
    2016-02-25 06:21:16:624 996 1bc8 Agent  * WARNING: Exit code = 0x8024400D
    2016-02-25 06:21:16:625 996 1bc8 Agent *********
    2016-02-25 06:21:16:625 996 1bc8 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-02-25 06:21:16:625 996 1bc8 Agent *************
    2016-02-25 06:21:16:625 996 1bc8 Agent WARNING: WU client failed Searching for update with error 0x8024400d
    2016-02-25 06:21:16:633 996 19a8 AU >>##  RESUMED  ## AU: Search for updates [CallId = {DA860910-0FAD-48D3-B931-CC44A9A0B81E}]
    2016-02-25 06:21:16:633 996 19a8 AU  # WARNING: Search callback failed, result = 0x8024400D
    2016-02-25 06:21:16:633 996 19a8 AU  # WARNING: Failed to find updates with error code 8024400D
    2016-02-25 06:21:16:633 996 19a8 AU #########
    2016-02-25 06:21:16:633 996 19a8 AU ##  END  ##  AU: Search for updates [CallId = {DA860910-0FAD-48D3-B931-CC44A9A0B81E}]
    2016-02-25 06:21:16:633 996 19a8 AU #############
    2016-02-25 06:21:16:633 996 19a8 AU Successfully wrote event for AU health state:0
    2016-02-25 06:21:16:634 996 19a8 AU AU setting next detection timeout to 2016-02-25 11:21:16
    2016-02-25 06:21:16:634 996 19a8 AU Setting AU scheduled install time to 2016-02-27 23:00:00
    2016-02-25 06:21:16:634 996 19a8 AU Successfully wrote event for AU health state:0
    2016-02-25 06:21:16:634 996 19a8 AU Successfully wrote event for AU health state:0
    2016-02-25 06:21:21:623 996 1bc8 Report REPORT EVENT: {D09D91A6-CF07-49EE-BBF3-CC16209F3955} 2016-02-25 06:21:16:624-0000 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400d AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400d.
    2016-02-25 06:21:21:642 996 1bc8 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-02-25 06:21:21:642 996 1bc8 Report WER Report sent: 7.6.7601.19116 0x8024400d(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2016-02-25 06:28:23:671 996 1bc8 PT WARNING: Cached cookie has expired or new PID is available
    2016-02-25 06:28:23:671 996 1bc8 PT Initializing simple targeting cookie, clientId = e705e617-058d-4470-9490-aa5555560399, target group = Workstations, DNS name = lon-cfpat-wks-037.cfpartners.local
    2016-02-25 06:28:23:671 996 1bc8 PT  Server URL = http://lon-cfpat-adm-001/SimpleAuthWebService/SimpleAuth.asmx
    2016-02-25 06:28:23:691 996 1bc8 Report Uploading 1 events using cached cookie, reporting URL = http://lon-cfp-adm-001/ReportingWebService/ReportingWebService.asmx
    2016-02-25 06:28:23:694 996 1bc8 Report Reporter successfully uploaded 1 events.
    2016-02-25 08:44:57:352 996 944 AU AU setting next sqm report timeout to 2016-02-26 08:44:57
    Thursday, February 25, 2016 9:21 AM
  • Hi Reo,

    >PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

    According to the error, I found this blog:

    https://blogs.technet.microsoft.com/sus/2008/10/29/wsus-clients-fail-synchronization-with-0x80244015-and-0x8024400d-errors/

    Do you have WSUS cluster?

    If not, also check if reset SUSID of the client could work.

    Reset WSUS Authorization and get new WSUS SID:

    https://gallery.technet.microsoft.com/scriptcenter/Reset-WSUS-Authorization-2e26d1b0

    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.

    Friday, February 26, 2016 2:19 AM
  • We don't run a cluster. I have run the bat file as per the second suggestion. I will let that settle and report back early next week.
    Friday, February 26, 2016 10:10 AM
  • Hi Reo,

    The errors below are caused by having too many updates available on the WSUS server.

    PT WARNING:     ErrorCode:InvalidParameters(7)
    2016-02-25 06:21:16:624
    996 1bc8
    PT WARNING:     Message:parameters.OtherCachedUpdateIDs

    This limit is exceeded during the search for updates:

    The limit is 22000 on a WSUS 4.0 server:

    C:\Program Files\Update Services\WebServices\ClientWebService\web.config

    <add key="maxCachedUpdates" value="22000"/>

    And 20000 on a WSUS 3.2 Server:

    <!-- The maximim number of update IDs that a client can pass to SyncUpdates,

             SyncPrinterCatalogs, or RefreshCache.

             An InvalidParameters exception is thrown if this limit is exceeded.

        -->

        <add key="maxCachedUpdates" value="20000"/>

    As you see above we get the same InvalidParameters error.

    The solution is to decline as many updates as possible and I recommend that we start with the superseded ones that we no longer need, more info:

    https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/

    After the cause has been removed (too many updates) do a test by deleting the c:\windows\softwaredistribution folder on one of the clients. If the search is successful then you have declined enough updates to not hit that limit. Please let me know when you have reached this part.

    Best regards,

    Andrei


    We could change the world, if God would give us the source code.

    Friday, February 26, 2016 2:13 PM
  • Resetting the SUSID was the last action taken, and the computer is now reporting in OK. Thank you for your help.

    Tuesday, March 1, 2016 9:33 AM
  • Hi Reo,

    You are welcome and glad to hear it works, cheers!

    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.

    Tuesday, March 1, 2016 9:38 AM