Close Menu
    Facebook X (Twitter) Instagram
    Friday, May 16
    X (Twitter) LinkedIn
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»CM2012»Configmgr OnSearchComplete – Failed to end search job Error 0x80244022 WUAHandler.log

    Configmgr OnSearchComplete – Failed to end search job Error 0x80244022 WUAHandler.log

    Eswar KonetiBy Eswar KonetiFebruary 18, 5:58 am2 Mins Read CM2012 45,647 Views
    Share
    Facebook Twitter LinkedIn Reddit

    Recently,After the Path Tuesday, None of the clients which are reporting to Primary Site did not perform a successful Scan (clients beneath secondary Site are working Good) .This leads me to look at the software update logs on the client to see what is going wrong. Since most of the clients directly reporting to Primary are having issues ,so thought of checking/troubleshoot this issue on the Primary site itself .

    Browse through the wuahandler.log from Drive:\Configmr\SMS_CCM\Logs,below is what I can see.

     

    OnSearchComplete - Failed to end search job. Error = 0x80244022.

    Scan failed with error = 0x80244022.

    image

    To know the error code description about ‘0x80244022’ ,use error lookup from cmtrace (ctrl+L).image

    Same as HTTP status 503 - the service is temporarily overloaded.

    Source: Windows Update Agent

    The 503 Service Unavailable error means, the problem is usually with the web site is down which is WSUS in this case.

    Tried restarting the server ,followed by WSUS service and IIS service but issue still exist.

    after the search on the internet,found this article ,leads me to check the application pool in IIS.I jump into IIS to check the status of WSUS application pool which was in stopped state .

    After starting the wsuspool application,sync completed successfully.

    image

    Tried to initiate software update scan cycle on the client,monitor wuahandler.log

    image

    so why does the WSUS pool in IIS stopped ? that could be because of  memory limit.take a look at these blogs http://blogs.technet.com/b/configurationmgr/archive/2015/03/23/configmgr-2012-support-tip-wsus-sync-fails-with-http-503-errors.aspx and http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/

    Hope it helps!

    apppool stopped CM12 configmgr Error = 0x80244022 memory limit OnSearchComplete scan failed SCCM 2012 wsuspool WUAHandler.log
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    Migrate Microsoft 365 Updates from SCCM/MECM to Intune for Co-Managed Devices

    February 11, 9:50 pm

    How to detect the source of registry key modifications on windows devices – Intune

    November 21, 8:49 pm

    Identifying devices managed by Intune but not reporting to WUfB using KQL

    November 09, 10:28 am

    27 Comments

    1. Weerasak Suksanguan on June 16, 2020 11:29 AM

      I had this same error. In my HQ all clients can work correctly, but another site (WAN connection has firewall between sites), I create new DP to support all clients in this site. The new DP and all clients in WAN site has same error "OnSearchComplete – Failed to end search job Error 0x80244022" in WUAHandler.log. What should I do in this case? Please advise.

      Reply
      • Eswar Koneti on June 16, 2020 5:06 PM

        did you check the wsus app pool and the client logs if there is any proxy/firewall for the update scan.
        also check the scanagent.log for further troubleshooting.

        Thanks,
        Eswar

        Reply
        • Weerasak Suksanguan on June 16, 2020 6:23 PM

          WSUS app pool already started, no setting for proxy and firewall already allow for any service.
          scanagent.log got error as below

          ScanJob({447A5316-9F8F-4BA9-94EC-3FB9B2C788E6}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle.
          CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631
          ScanJob({D6A0ED5A-EC23-4319-8096-554FF12A35F8}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244022

          Reply
        • Weerasak Suksanguan on June 17, 2020 11:16 AM

          I checked WSUS app pool already started, I do not use proxy and FW allow any services for sccm environment. I got error on scanagent.log as
          ScanJob({D6A0ED5A-EC23-4319-8096-554FF12A35F8}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle.
          CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631
          ScanJob({D6A0ED5A-EC23-4319-8096-554FF12A35F8}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244022

          Reply
          • Eswar Koneti on June 20, 2020 12:26 AM

            are you able to browse the WSUS URL from the client? you can get the URL of WSUS that it is trying to scan from wuahandler.log.

            Thanks,
            Eswar

            Reply
            • Weerasak Suksanguan on June 22, 2020 1:17 PM

              ํYes, I can browse from the client.

              Reply
            • Weerasak Suksanguan on June 23, 2020 12:52 PM

              I opened http://WSUSSERVER:8530/SimpleAuthWebService/SimpleAuth.asmx URL on a web browser and got without error, but still scan failed.

              Reply
    2. Hema on April 24, 2020 3:27 PM

      I have same issue but my wsus pool is working , I don't know what to do next , next I have many devices which are ending up with this error kindly suggest me .

      Reply
      • Eswar Koneti on April 28, 2020 2:19 AM

        Hi,
        you can initiate the software update scan and monitor the logs for further troubleshooting.
        The logs should help you with error codes and what is going on.

        Thanks,
        Eswar

        Reply
        • Weerasak Suksanguan on June 16, 2020 11:25 AM

          I had this same error. In my HQ all clients can work correctly, but another site (WAN connection has firewall between sites), I create new DP to support all clients in this site. The new DP and all clients in WAN site has same error "OnSearchComplete – Failed to end search job Error 0x80244022" in WUAHandler.log. What should I do in this case? Please advise.

          Reply
    3. Vijaya.G on January 22, 2020 12:12 AM

      I have got the same issue. But in my case i could not find the wsus pool in IIS manger. Please advise.

      Reply
      • Eswar Koneti on January 22, 2020 2:38 PM

        Hi,
        IIS is prereq for WSUS . Do you have working WSUS and configuration done correctly?
        can you share the IIS screenshot that has WSUS installed.

        Thanks,
        Eswar

        Reply
    4. Jonathan Dono on April 7, 2018 2:14 AM

      Just in case this helps someone else, I had this same error due to our Palo Alto firewall receiving an update that changed it's app filtering and thus prevented the client-server traffic from reaching SCCM/WSUS. TCP ports 80, 443, 8530, & 8531 are needed for this to work. In my case, the ports were technically open, but not for the specific application as defined by Palo Alto so I ended up turning off the application level filtering and just allowing all traffic on those ports.

      Reply
      • Eswar Koneti on July 8, 2018 9:29 PM

        Thanks Jonathan ,appreciate your help on this.

        Regards,
        Eswar

        Reply
    5. Pingback: Config Manager Current Branch Delta Downloads and WSUS | Confessions of a Config Manager Engineer

    6. Pingback: Windows 10 In Place Upgrade via SCCM stuck on 75% – SCCM not so common issues

    7. Jon on October 21, 2015 8:33 PM

      I had the same issue and looking for a solution 2 days... Hope this will fix my issue

      Reply
      • Eswar Koneti on October 21, 2015 10:23 PM

        Did it solve the problem ?

        Reply
        • Veeresh DR on April 12, 2018 1:55 AM

          I have still this issue though the WsusPool in started status. What should I do in this case?

          Reply
          • Eswar Koneti on July 8, 2018 9:27 PM

            can you restart the WSUS IIS pool ? can you look at windowsupdate.log and get the URL of WSUS and try to access using browser if you can access it or not ?

            Regards,
            Eswar

            Reply
            • dipesh on October 2, 2019 9:34 PM

              Thanks Eswar this helped me too. I found the WSUS pool private memory was too less as result of that it was in stopped state. When i started it scan completed successfully.
              Steps to increase WSUS pool memory:
              https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/

              Reply
              • Eswar Koneti on October 2, 2019 9:51 PM

                Glad it helped, thanks for the link too!

              • jon on October 21, 2020 2:15 PM

                It didn't help me, mine is in running state. Pool Memory allotted 0, server RAM 128GB.

                sorry posting comment to a year old post.

    8. Eve on September 17, 2015 10:03 PM

      Thanks. Clear and precise solution.

      Reply
      • Rildo on April 20, 2018 8:03 PM

        This post was precise. It solved my issue. That was exactly the WsusPool stopped in IIS.

        Reply
    9. Jason on May 22, 2015 1:56 PM

      I ran into this same issue, i was wondering if you know why this happened? It would be good to know why it stopped so that i can prevent it in the future.

      Thanks,

      Reply
      • Eswar Koneti on May 23, 2015 8:14 AM

        this could be because of apppool memory limit in IIS.have a look at this blog http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/

        Reply

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2024 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.