locked
Windows could not search for new Updates RRS feed

  • Question

  • We Hosted windows 2008 R2 SP1 server and hosted WSUS on it on nov 2014. Now we noticed that our newly added systems and newly added servers are not getting updates and getting error from JAN 2016. Windows could not search for new updates. But FEP updates are getting installed on all the servers from WSUS.

    When i checked the events, found below mentioned error in the event logs of the wsus servers.

    EVENT ID 1309, ASP.NET 2.0.50727.0

    Event code: 3001
    Event message: The request has been aborted.
    Event time: 2/15/2016 3:04:36 PM
    Event time (UTC): 2/15/2016 7:04:36 AM
    Event ID: 0c2a41e0e5ec4f969adb28cd6a4ac0e2
    Event sequence: 715
    Event occurrence: 9
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/1/ROOT/ClientWebService-1-130999926610251198
        Trust level: Full
        Application Virtual Path: /ClientWebService
        Application Path: C:\Program Files\Update Services\WebServices\ClientWebService\
        Machine name: PHMA63999070
     
    Process information:
        Process ID: 4836
        Process name: w3wp.exe
        Account name: NT AUTHORITY\NETWORK SERVICE
     
    Exception information:
        Exception type: HttpException
        Exception message: Request timed out.
     
    Request information:
        Request URL: http://10.242.107.133/ClientWebService/client.asmx
        Request path: /ClientWebService/client.asmx
        User host address: 10.215.76.49
        User:  
        Is authenticated: False
        Authentication Type:  
        Thread account name: NT AUTHORITY\NETWORK SERVICE
     
    Thread information:
        Thread ID: 20
        Thread account name: NT AUTHORITY\NETWORK SERVICE
        Is impersonating: False
        Stack trace:
     
    Please suggest for resolving this issue. 

    Monday, February 15, 2016 7:59 AM

Answers

  • Hi Mamatha,

    the 80244010 (WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS) error is a transient error. Meaning that during that search attempt a limit was reached when talking to the WSUS server. This error will go away with 2-3 additional searches, because there will no longer be as much data to shift from the server to the client.

    Check and see if the following URL can be opended from the client:

    http://servernameorip:8530/selfupdate/wuident.cab

    Best regards,

    Andrei


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

    Wednesday, February 24, 2016 6:29 PM

All replies

  • Am 15.02.2016 schrieb Mamatha Rangaswamy:

    We Hosted windows 2008 R2 SP1 server and hosted WSUS on it on nov 2014. Now we noticed that our newly added systems and newly added servers are not getting updates and getting error from JAN 2016. Windows could not search for new updates. But FEP updates are getting installed on all the servers from WSUS.

    Pls check Build from your WSUS. Here you find the place of the build:
    http://www.wsus.de/images/wsus-version.png
    If the Build is lower then .274, you have to update. Here you find the
    KBs to update to the last Build:

    WSUS 3.0 (SP2):     Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211:     Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608:     Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185:     Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066:     Build 3.2.7600.274

    After the Build is .274, restart the whole Server and just now restart
    your Clients/Server and try to connect WSUS.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Monday, February 15, 2016 7:26 PM
  • Hi Mamatha Rangaswamy,

    As Winfried has suggested, you may upgrade your WSUS server first and check the result.

    If it still doesn't work, we may check the following things:

    1. Check if the new added WSUS clients have applied the correct GPO, check the WSUS server's name, if you use FQDN, then check if the clients could resolve the name;

    2. Check the network connection between the clients and the WSUS server, you may use ping command;

    3. Check if you have approved related updates for the new add clients, only updates that have been approved for installation could be download by clients;

    4. If it still doesn't work, you may provide the windowsupdate log which is located in : 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.

    Tuesday, February 16, 2016 7:41 AM
  • Thanks for looking into this, we upgraded our WSUS as per the sugestion and rebooted the WSUS server and client, still getting the same error.

    Please find the windows update log from the client.

    2016-02-17    12:51:42:444     980    8e0    AU    ###########  AU: Initializing Automatic Updates  ###########
    2016-02-17    12:51:42:444     980    8e0    AU      # WSUS server: http://WSUS server ip
    2016-02-17    12:51:42:444     980    8e0    AU      # Detection frequency: 22
    2016-02-17    12:51:42:444     980    8e0    AU      # Approval type: Scheduled (Policy)
    2016-02-17    12:51:42:444     980    8e0    AU      # Scheduled install day/time: Every day at 16:00
    2016-02-17    12:51:42:444     980    8e0    AU      # Auto-install minor updates: Yes (Policy)
    2016-02-17    12:51:42:460     980    8e0    AU    Setting AU scheduled install time to 2016-02-17 08:00:00
    2016-02-17    12:51:42:460     980    8e0    AU    Successfully wrote event for AU health state:0
    2016-02-17    12:51:42:460     980    8e0    AU    Initializing featured updates
    2016-02-17    12:51:42:460     980    8e0    AU    Found 0 cached featured updates
    2016-02-17    12:51:42:460     980    8e0    AU    Successfully wrote event for AU health state:0
    2016-02-17    12:51:42:460     980    8e0    AU    Successfully wrote event for AU health state:0
    2016-02-17    12:51:42:460     980    8e0    AU    AU finished delayed initialization
    2016-02-17    12:54:52:593     980    e70    AU    Triggering AU detection through DetectNow API
    2016-02-17    12:54:52:593     980    e70    AU    Triggering Online detection (interactive)
    2016-02-17    12:54:52:593     980    8e0    AU    #############
    2016-02-17    12:54:52:593     980    8e0    AU    ## START ##  AU: Search for updates
    2016-02-17    12:54:52:593     980    8e0    AU    #########
    2016-02-17    12:54:52:640     980    8e0    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {12553E05-576F-4429-96A8-D1C9DD83FE87}]
    2016-02-17    12:54:52:640     980    f98    Agent    *************
    2016-02-17    12:54:52:640     980    f98    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-02-17    12:54:52:655     980    f98    Agent    *********
    2016-02-17    12:54:52:655     980    f98    Agent      * Online = Yes; Ignore download priority = No
    2016-02-17    12:54:52:655     980    f98    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-17    12:54:52:655     980    f98    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-02-17    12:54:52:655     980    f98    Agent      * Search Scope = {Machine}
    2016-02-17    12:54:52:655     980    f98    Setup    Checking for agent SelfUpdate
    2016-02-17    12:54:52:655     980    f98    Setup    Client version: Core: 7.6.7601.19077  Aux: 7.6.7601.19077
    2016-02-17    12:54:53:545     980    f98    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-02-17    12:54:53:591     980    f98    Misc     Microsoft signed: NA
    2016-02-17    12:54:53:607     980    f98    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPAE38.tmp with dwProvFlags 0x00000080:
    2016-02-17    12:54:53:638     980    f98    Misc     Microsoft signed: NA
    2016-02-17    12:54:53:732     980    f98    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-02-17    12:54:53:732     980    f98    Misc     Microsoft signed: NA
    2016-02-17    12:54:53:857     980    f98    Setup    Determining whether a new setup handler needs to be downloaded
    2016-02-17    12:54:53:857     980    f98    Setup    SelfUpdate handler is not found.  It will be downloaded
    2016-02-17    12:54:53:857     980    f98    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-02-17    12:54:54:013     980    f98    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-02-17    12:54:54:013     980    f98    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-02-17    12:54:54:169     980    f98    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-02-17    12:54:54:169     980    f98    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-02-17    12:54:54:387     980    f98    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-02-17    12:54:54:403     980    f98    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-02-17    12:54:54:715     980    f98    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-02-17    12:54:54:715     980    f98    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUS server ip/ClientWebService/client.asmx
    2016-02-17    12:54:54:730     980    f98    PT    WARNING: Cached cookie has expired or new PID is available
    2016-02-17    12:54:54:730     980    f98    PT    Initializing simple targeting cookie, clientId = 7bec1a3a-5c04-44ab-99d3-43456ea9ebe7, target group = , DNS name = DC FQDN
    2016-02-17    12:54:54:730     980    f98    PT      Server URL = http://WSUS server ip/SimpleAuthWebService/SimpleAuth.asmx
    2016-02-17    12:55:04:168     980    f98    PT    WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2016-02-17    12:55:04:184     980    f98    PT    WARNING: SOAP Fault: 0x00012c
    2016-02-17    12:55:04:184     980    f98    PT    WARNING:     faultstring:Fault occurred
    2016-02-17    12:55:04:184     980    f98    PT    WARNING:     ErrorCode:ConfigChanged(2)
    2016-02-17    12:55:04:184     980    f98    PT    WARNING:     Message:(null)
    2016-02-17    12:55:04:184     980    f98    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2016-02-17    12:55:04:184     980    f98    PT    WARNING:     ID:2612fd1a-38c6-41bd-a296-a88654d07e32
    2016-02-17    12:55:04:262     980    f98    PT    WARNING: Cached cookie has expired or new PID is available
    2016-02-17    12:55:04:262     980    f98    PT    Initializing simple targeting cookie, clientId = 7bec1a3a-5c04-44ab-99d3-43456ea9ebe7, target group = , DNS name = DC FQDN
    2016-02-17    12:55:04:262     980    f98    PT      Server URL = http://WSUS server ip/SimpleAuthWebService/SimpleAuth.asmx
    2016-02-17    12:56:07:223     980    f98    Misc    WARNING: Send failed with hr = 80072ee2.
    2016-02-17    12:56:07:223     980    f98    Misc    WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-02-17    12:56:07:223     980    f98    Misc    FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-02-17    12:56:07:223     980    f98    PT      + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-02-17    12:56:07:223     980    f98    PT      + Caller provided credentials = No
    2016-02-17    12:56:07:223     980    f98    PT      + Impersonate flags = 0
    2016-02-17    12:56:07:223     980    f98    PT      + Possible authorization schemes used =
    2016-02-17    12:56:07:223     980    f98    PT    WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-02-17    12:56:07:223     980    f98    PT    WARNING: PTError: 0x80072ee2
    2016-02-17    12:56:07:223     980    f98    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
    2016-02-17    12:56:07:223     980    f98    PT    WARNING: Sync of Updates: 0x80072ee2
    2016-02-17    12:56:07:223     980    f98    PT    WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
    2016-02-17    12:56:07:223     980    f98    Agent      * WARNING: Failed to synchronize, error = 0x80072EE2
    2016-02-17    12:56:07:223     980    f98    Agent      * WARNING: Exit code = 0x80072EE2
    2016-02-17    12:56:07:223     980    f98    Agent    *********
    2016-02-17    12:56:07:223     980    f98    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-02-17    12:56:07:223     980    f98    Agent    *************
    2016-02-17    12:56:07:223     980    f98    Agent    WARNING: WU client failed Searching for update with error 0x80072ee2
    2016-02-17    12:56:07:223     980    e40    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {12553E05-576F-4429-96A8-D1C9DD83FE87}]
    2016-02-17    12:56:07:223     980    e40    AU      # WARNING: Search callback failed, result = 0x80072EE2
    2016-02-17    12:56:07:223     980    e40    AU      # WARNING: Failed to find updates with error code 80072EE2
    2016-02-17    12:56:07:223     980    e40    AU    #########
    2016-02-17    12:56:07:223     980    e40    AU    ##  END  ##  AU: Search for updates [CallId = {12553E05-576F-4429-96A8-D1C9DD83FE87}]
    2016-02-17    12:56:07:223     980    e40    AU    #############
    2016-02-17    12:56:07:223     980    e40    AU    Successfully wrote event for AU health state:0
    2016-02-17    12:56:07:223     980    e40    AU    AU setting next detection timeout to 2016-02-17 09:56:07
    2016-02-17    12:56:07:223     980    e40    AU    Setting AU scheduled install time to 2016-02-17 08:00:00
    2016-02-17    12:56:07:223     980    e40    AU    Successfully wrote event for AU health state:0
    2016-02-17    12:56:07:239     980    e40    AU    Successfully wrote event for AU health state:0
    2016-02-17    12:56:12:231     980    f98    Report    REPORT EVENT: {CB3FAEDF-6761-4BDB-86FD-D7311E889ABB}    2016-02-17 12:56:07:223+0800    1    148    101    {00000000-0000-0000-0000-000000000000}    0    80072ee2    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80072ee2.
    2016-02-17    12:56:12:356     980    f98    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-02-17    12:56:12:356     980    f98    Report    WER Report sent: 7.6.7601.19077 0x80072ee2(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0


    Wednesday, February 17, 2016 5:00 AM
  • Hi Mamatha,

    >Failed to find updates with error code 80072EE2

    Error code 80072EE2 is related with connection issue to WSUS server, check if the related WSUS port is opened on client, you may turn off the firewall temporarily to check the result.

    And check if the client could resolve the WSUSname. Also run ping command to check the network connection between WSUS client and WSUS server.

    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 19, 2016 8:22 AM
  • Am 17.02.2016 schrieb Mamatha Rangaswamy:

    2016-02-17    12:56:07:223     980    f98    Misc    WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-02-17    12:56:07:223     980    f98    Misc    FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2

    Is there a Proxy in your LAN?

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Friday, February 19, 2016 2:36 PM
  • Sorry for delayed in the response, thanks a lot for all you responses.

    Ports are enabled at user systems, till january the WSUS was fine. Now systems are getting error "Windows could not search for new updates. Error found Code 80244010". Restarted Background Intelligent Transfer Service and Windows update services.

    WSUS server version : 3.2.7600.274

    WSUS Client version : 7.6.7601.19116

    Can you please suggest.


    Wednesday, February 24, 2016 11:24 AM
  • Hi Mamatha,

    the 80244010 (WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS) error is a transient error. Meaning that during that search attempt a limit was reached when talking to the WSUS server. This error will go away with 2-3 additional searches, because there will no longer be as much data to shift from the server to the client.

    Check and see if the following URL can be opended from the client:

    http://servernameorip:8530/selfupdate/wuident.cab

    Best regards,

    Andrei


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

    Wednesday, February 24, 2016 6:29 PM
  • Am 24.02.2016 wrote Mamatha Rangaswamy:

    Ports are enabled at user systems, till january the WSUS was fine. Now systems are getting error "Windows could not search for new updates. Error found Code 80244010". Restarted Background Intelligent Transfer Service and Windows update services.

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

    Another Tipp:
    http://www.sysax.com/ftblog/windows-ftp/exceeded-max-server-round-trips-0x80244010/

    Is the problem still exist at all clients?

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Wednesday, February 24, 2016 6:40 PM
  • Hi Mamatha,

    Do you get any progress with the issue. 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.

    Monday, February 29, 2016 1:47 AM
  • Still few systems had issue, so now i'm migrating WSUS server to Windows 2012. Thanks everyone for you support.
    Friday, March 18, 2016 11:12 AM
  • Well other errors also include these,

    0x8024000B

    0x8024001e

    Sometimes 0x80070005

    Then a message in the logs while looking for updates says that "Windows Update Received a Shutdown Request",

    Which tells me the Agent is Faulty and most of the Microsoft Staff say it is a Virus/Malware/Rootkit problem, but I have scanned many times and have not seen ANYTHING,

    Microsoft, I hope you better not be Abandoning Windows 7 Users for Windows 10, because it sounds like you want to have the Malware and Rootkits Infect Windows 7 users and not Window 8.,1 and Windows 10 with the Metro UI system. 

    Wednesday, April 13, 2016 7:25 PM