locked
WSUS Clients showing "Not Yet Reported" Error : failed: 0x80244010 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    HI

    we have Upstream server and down stream server in XYZ location out 10 % of windows 7 clients are showing "NOT YET REPORTED" status and getting below error in the Windowsupdate.log

    "2016-05-05    10:58:24:557     320    19dc    PT    WARNING: Exceeded max server round trips: 0x80244010
    2016-05-05    10:58:24:557     320    19dc    PT    WARNING: Sync of Updates: 0x80244010
    2016-05-05    10:58:24:557     320    19dc    PT    WARNING: SyncServerUpdatesInternal failed: 0x80244010
    2016-05-05    10:58:24:557     320    19dc    Agent      * WARNING: Failed to synchronize, error = 0x80244010
    2016-05-05    10:58:24:558     320    19dc    Agent      * WARNING: Exit code = 0x80244010
    2016-05-05    10:58:24:558     320    19dc    Agent    *********
    2016-05-05    10:58:24:558     320    19dc    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-05-05    10:58:24:558     320    19dc    Agent    *************
    2016-05-05    10:58:24:558     320    19dc    Agent    WARNING: WU client failed Searching for update with error 0x80244010
    2016-05-05    10:58:24:596     320    19d8    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {AA9C5F43-436D-46A0-9F9E-A63347006564}]
    2016-05-05    10:58:24:596     320    19d8    AU      # WARNING: Search callback failed, result = 0x80244010
    2016-05-05    10:58:24:596     320    19dc    Report    REPORT EVENT: {F51048A9-15E2-4B1A-A3DF-5E93C9FE7F73}    2016-05-05 10:55:05:328+0530    1    202    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Reboot completed.
    2016-05-05    10:58:24:596     320    19d8    AU      # WARNING: Failed to find updates with error code 80244010
    2016-05-05    10:58:24:596     320    19d8    AU    #########
    2016-05-05    10:58:24:596     320    19d8    AU    ##  END  ##  AU: Search for updates [CallId = {AA9C5F43-436D-46A0-9F9E-A63347006564}]
    2016-05-05    10:58:24:596     320    19d8    AU    #############
    2016-05-05    10:58:24:599     320    19d8    AU    Successfully wrote event for AU health state:0
    2016-05-05    10:58:24:600     320    19d8    AU    AU setting next detection timeout to 2016-05-05 09:22:01
    2016-05-05    10:58:24:600     320    19d8    AU    AU was unable to detect updates for more than 48 hours
    2016-05-05    10:58:24:601     320    19d8    AU    Setting AU scheduled install time to 2016-05-05 07:30:00
    2016-05-05    10:58:24:602     320    19d8    AU    Successfully wrote event for AU health state:0
    2016-05-05    10:58:24:603     320    19d8    AU    Successfully wrote event for AU health state:0
    2016-05-05    10:58:24:604     320    19dc    Report    CWERReporter finishing event handling. (00000000)
    2016-05-05    10:58:24:604     320    19dc    Report    REPORT EVENT: {48FB6B71-78E7-4D4B-B7C5-511E4CADAE23}    2016-05-05 10:58:24:558+0530    1    148    101    {00000000-0000-0000-0000-000000000000}    0    80244010    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80244010.
    2016-05-05    10:58:24:605     320    19dc    Report    REPORT EVENT: {3839C652-55DC-49F3-9615-FDDA0BFFFC73}    2016-05-05 10:58:24:600+0530    1    149    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Failure    Software Synchronization    Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
    2016-05-05    10:58:24:680     320    19dc    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-05-05    10:58:24:680     320    19dc    Report    WER Report sent: 7.6.7600.256 0x80244010 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2016-05-05    10:58:24:680     320    19dc    Report    CWERReporter finishing event handling. (00000000)
    2016-05-05    10:58:25:049     320    19dc    Report    Uploading 2 events using cached cookie, reporting URL = http://xxxxxxxxxxxxxxxxx.com/ReportingWebService/ReportingWebService.asmx
    2016-05-05    10:58:25:051     320    19dc    Report    Reporter successfully uploaded 2 events.

    Tried the bElow:

    1. Reset the windows update agent using tool

    2. Renamed the softwaredistribution folder and removed susclientID

    3. run wuauclt.exe /resetauthorization /detectnow

    but still not able to get rid of this error.

    Thursday, May 5, 2016 10:20 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi SPV4645,

    Have you got any progress? Welcome to feed back.

    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.

    • Marked as answer by SPV4645 Monday, July 4, 2016 9:31 AM
    Monday, May 9, 2016 2:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    we found that those system are installed with OS Images(customized). we have reinstalled the OS now it is working fine.

    • Marked as answer by SPV4645 Monday, July 4, 2016 9:31 AM
    Monday, July 4, 2016 9:30 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi SPV4645,

    > WARNING: Sync of Updates: 0x80244010

    Error 0x80244010 means WU_E_PT_EXCEEDED_MAX_SERVER_TRIP. It may happen when a client has exceed the number of trips allowed to a WSUS server. MS defines the maximum number of trips as 200 within code and it cannot be reconfigured. I guess this error occurs on new clients in your lab, since this often exits during the first scan.

    Here is the detailed explanation of this problem, and it is by design, also seems there haven't been official fix for it yet.

    WSUS clients fail with WARNING: SyncServerUpdatesInternal failed: 0x80244010

    https://blogs.technet.microsoft.com/sus/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010/

    But there's still something we can do:

    1. As the blog indicates, updates for "Offices" are typically large in size, so, we may not check "Office" products in WSUS server at the initial sync;

    2. Identify all superseded updates on the WSUS server and decline them to reduce the number of updates.

    Lawrence also explains this issue here in detail for your reference:

    https://social.technet.microsoft.com/Forums/en-US/f29f6f83-3870-460a-954f-448f146d6c38/wsus-clients-fail-with-0x80244010-in-a-silent-installation?forum=winserverwsus

    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, May 6, 2016 2:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Anne He

    Let me follow this and update to you the result.

    Friday, May 6, 2016 6:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi SPV4645,

    Have you got any progress? Welcome to feed back.

    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.

    • Marked as answer by SPV4645 Monday, July 4, 2016 9:31 AM
    Monday, May 9, 2016 2:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    we have waiting for approval so i will update soon.

    Monday, May 9, 2016 5:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi SPV,

    Just to confirm if you have got any progress, if you need further help, feel free to feed back.

    Best Regards,

    Anne

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

    Monday, May 16, 2016 2:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    we found that those system are installed with OS Images(customized). we have reinstalled the OS now it is working fine.

    • Marked as answer by SPV4645 Monday, July 4, 2016 9:31 AM
    Monday, July 4, 2016 9:30 AM