Close Menu
    Facebook X (Twitter) Instagram
    Monday, June 23
    X (Twitter) LinkedIn
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»CM2012»SCCM Configmgr 2012 Software Update Scan failed OnSearchComplete – Failed to end search job. Error = 0xc8000222

    SCCM Configmgr 2012 Software Update Scan failed OnSearchComplete – Failed to end search job. Error = 0xc8000222

    Eswar KonetiBy Eswar KonetiNovember 17, 12:32 pm2 Mins Read CM2012 11,769 Views
    Share
    Facebook Twitter LinkedIn Reddit

    Trying to run the patch compliance report based on OU per Software update Group (For October 2014) ,report is available to download from http://eskonr.com/2014/11/sccm-configmgr-2012-patch-report-ou-based-compliance-status-per-update-group/ . Report shows some good success rate but still there are computers with unknown status .Unknown status means,these clients do not report anything to CM DB whether they required patches or not required ,no compliance information at all.

    I pick one computer randomly and start looking at Software Update logs on the client side . The software update logs that helps to identify the scan issues are WUAHandler.log (CCM\logs),windowsupdate.log(%Windir%)

    WUAHandler.log log shows ,client started to search for windows updates but it failed with error code 0xc8000222.

    Error message : OnSearchComplete - Failed to end search job. Error = 0xc8000222.

    Scan failed with error = 0xc8000222.

    To know the description of this error code,tried error lookup from the CMtrace log ,but that doesn’t give me any clue.

    image

    The next log to look at is ,Windowsupdate.log  ,to know more about windowsupdate.log and how to read it,please refer https://support.microsoft.com/kb/902093?wa=wsignin1.0 and http://www.updatexp.com/windows-update-log.html

    Windowsupdate.log errors out with message : DtaStor    FATAL: Failed to initialize datastore, error = 0xC8000222

    It seems to like,the datastore or  other related component from C:\windows\softwaredistribution folders are corrupted.

    image

     

    Solution :

    The solution for this issue ,is to stop windows update service,rename software distribution folder,start windows update service and then run the software update scan action.

    1. Open the CMD (run as administrator) ,type net stop wuauserv to stop the windows update service

    2.Type rename C:\windows\softwaredistribution softwaredistribution.old to rename

    3.Type net start wuauserv to start windows update service

    4.Initiate software update scan cycle from Configuration manager applet .

    To run action 4,there are various scripts/tools available,like wmic,right click tools,sccm client center etc.

    You can also script this solution to perform on bulk clients.

    After you run action 4,monitor WUAhandler.log ,should see sync status with success.

    image

     

    Hope it helps!

    0xc8000222 CM12 Error = 0xc8000222 patching Scan failed with SCCM 2012 software update scan error Software Update Scan failed OnSearchComplete SUP WUAHandler.log
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    Optimize Your Intune Workflow with a Powerful Browser Extension

    March 22, 10:39 am

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

    February 11, 9:50 pm

    Combine Intune Data with WUfB Data in Log Analytics (KQL) for Better Device Insights

    January 16, 10:08 pm

    12 Comments

    1. Pingback: Troubleshoot client side software updates issue. | system center experts

    2. Nawaz Kazi on November 27, 2014 6:25 PM

      Its Finding the correct software update point but all are in CAPS i guess is this because of UPPERCASE issue ?
      for e:g http://SUP.DOMAIN.COM:8530

      Reply
      • Eswar Koneti on November 28, 2014 5:25 PM

        Nope, it will be uppercase and it is not case sensitive. You can try initiating the software update scan action again to see if that works

        Reply
    3. Nawaz Kazi on November 27, 2014 1:13 PM

      i am getting error on many servers in wuahadler.log file "OnSearchComplete - Failed to end search job. Error = 0x80244016."

      Reply
      • Eswar Koneti on November 27, 2014 5:49 PM

        Did you look at Windowsupdate. Log from c:\windows folder? What does this log says? Did it find right wsus server?

        Reply
    4. Nawaz Kazi on November 26, 2014 9:32 AM

      will wait for another report on v_updatescanstatus.

      Reply
      • Eswar Koneti on December 8, 2014 10:34 AM

        did you try this scan status report ? http://eskonr.com/2014/10/sccm-configmgr-2012-report-get-the-status-of-software-update-scan-results/

        Reply
    5. Ch on November 22, 2014 8:44 AM

      Hi,

      I am using that only.However i am trying to use the below report for a customized collection which is static ? The overall compliance has only the three states.Also some say that the overall compliance is not as effective a the deployment status . Is this correct ?

      http://blog.coretech.dk/kea/status-report-for-software-update-deployments/

      thanks

      Reply
      • Eswar Koneti on November 26, 2014 6:27 AM

        IT is effective as far i know and i never use the console deployment for monitoring the status.Always use reports to get the compliance reports.
        yes,there are many 3 states that we measure the deployment status . 1)Compliant 2)Not Compliant 3)Unknown
        Compliant means,the client has successfully performed scan and they are okay (could be that patches are installed or not applicable). These clients are safe
        Not Compliant---clients having some problem with scanning and requires troubleshooting.
        Unknown--these computers have not done anything with respect to scanning ,means,they are not assigned or some issues with SUP component.If the scanning is performed successfully,this information will be tracked in v_updatescanstatus.
        I will soon post another Patch Compliance report that will give more information about the non compliant and unknown machines that will help to troubleshoot the clients .

        Reply
    6. Ch on November 21, 2014 11:47 AM

      Hi,

      We use one update list to which we add patches every month.This is linked to different workstation deployments.When i use report that would give status for a particular deployment it opens up the collection to which it is linked (in the deployment management). Would it be possible to get the deployment status for a customized collection ? Can this be achieved by linking any report or not possible at all ?

      Reply
      • Eswar Koneti on November 22, 2014 7:44 AM

        did you look at the default report ? patch compliance --overall compliance that give you to choose the update group and collection.

        Reply
    7. Nawaz Kazi on November 17, 2014 1:00 PM

      Thanks Mate.

      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.