none
Update Failed - Error - 0x87d00219 and 0x80240438 RRS feed

  • Frage

  • Hi people,

    We have some problem about update using Sccm. 

    We can see all updates on Configuration Manager console. We downloaded them and we deployeded them but we dont see them on the client machine. However, applications work fine, we can see and install it.

    Any ideas ? We go crazy! 

    This is the WUAhandler.log, i can share another if need. 

    THANKS A LOT :) 


    OnSearchComplete - Failed CCMGetGlobalService. Error = 0x87d00219 WUAHandler 26/11/2018 09:42:17 8732 (0x221C)
    Its a WSUS Update Source type ({3E4D2569-325A-4FC1-9698-CBAEF4D472B7}), adding it. WUAHandler 26/11/2018 09:44:43 6524 (0x197C)
    Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 26/11/2018 09:44:43 9356 (0x248C)
    SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 26/11/2018 09:44:43 9356 (0x248C)
    Existing WUA Managed server was already set (http://******), skipping Group Policy registration. WUAHandler 26/11/2018 09:44:43 6524 (0x197C)
    Added Update Source ({3E4D2569-325A-4FC1-9698-CBAEF4D472B7}) of content type: 2 WUAHandler 26/11/2018 09:44:43 6524 (0x197C)
    Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 26/11/2018 09:44:43 6524 (0x197C)
    Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 26/11/2018 09:44:43 6524 (0x197C)
    Async searching of updates using WUAgent started. WUAHandler 26/11/2018 09:44:43 6524 (0x197C)
    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles WUAHandler 26/11/2018 09:44:43 9224 (0x2408)
    Async searching completed. WUAHandler 26/11/2018 09:45:50 5032 (0x13A8)
    OnSearchComplete - Failed to end search job. Error = 0x80240438. WUAHandler 26/11/2018 09:45:50 6608 (0x19D0)
    Scan failed with error = 0x80240438. WUAHandler 26/11/2018 09:45:50 6608 (0x19D0)
    Its a WSUS Update Source type ({3E4D2569-325A-4FC1-9698-CBAEF4D472B7}), adding it. WUAHandler 26/11/2018 09:45:50 6520 (0x1978)
    Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 26/11/2018 09:45:50 6136 (0x17F8)
    SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 26/11/2018 09:45:50 6136 (0x17F8)
    Existing WUA Managed server was already set (********), skipping Group Policy registration. WUAHandler 26/11/2018 09:45:50 6520 (0x1978)
    Added Update Source ({3E4D2569-325A-4FC1-9698-CBAEF4D472B7}) of content type: 2 WUAHandler 26/11/2018 09:45:50 6520 (0x1978)
    Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 26/11/2018 09:45:50 6520 (0x1978)
    Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 26/11/2018 09:45:50 6520 (0x1978)
    Async searching of updates using WUAgent started. WUAHandler 26/11/2018 09:45:50 6520 (0x1978)

    • Bearbeitet SccmTek Montag, 26. November 2018 09:24
    Montag, 26. November 2018 09:22

Alle Antworten

  • Have you:
    - Declined all superseded updates directly in WSUS?
    - Adjusted the private memory limit on the WSUS IIS App Pool?
    - Adjusted the queue length on the WSUS IIS App Pool?
    - Reindexed the DB and rebuilt its statistics?
    - Applied the latest CU to the OS hosting the WSUS instance?
    - Declined version Next updates?
    - Removed unecessary product categories from your SUP configuration?

    References:

    - https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/
    - http://blog.ctglobalservices.com/configuration-manager-sccm/kea/house-of-cardsthe-configmgr-software-update-point-and-WSUS/
    - https://blogs.msdn.microsoft.com/the_secure_infrastructure_guy/2015/09/02/windows-server-2012-r2-wsus-issue-clients-cause-the-wsus-app-pool-to-become-unresponsive-with-http-503/
    - https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/
    - https://support.microsoft.com/en-us/help/4163525/high-bandwidth-use-when-clients-scan-for-updates-from-local-wsus-serve

    Jason | https://home.configmgrftw.com | @jasonsandys

    Montag, 26. November 2018 16:44
  • Dear Sir,

    This error(Scan failed with error = 0x80240438) may also be caused by proxy-related issues.
    So please verify the proxy settings on the client, and make sure that they are configured correctly. The Windows Update Agent uses WinHTTP to scan for available updates. So, when there is a proxy server between the client and the WSUS computer, the proxy settings must be configured correctly on the clients to enable them to communicate with WSUS by using the computer's FQDN. 

    And the following post describes a similar issue:

    http://myitpath.blogspot.com/2016/12/sccm-windows-update-deployment-failure.html

    https://gallery.technet.microsoft.com/ConfigMgr-Scan-failed-with-6c00f52c

    I hope the above information is helpful to you.

    Best regards,
    Larry


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

    Dienstag, 27. November 2018 08:42
  • Great !

    Thanks for all your ideas.. I will check it ! 

    Many thanks :) 

    Dienstag, 27. November 2018 10:09
  • I had similar issue with few clients, i disabled proxy , updated client policies, it started working. Thanks Larry :) 

    Anil Suthar

    Montag, 24. Juni 2019 02:25
  • Hey, 

    How did you go with this?

    can you please share with us?

    Thanks,

    Dienstag, 29. Oktober 2019 04:00
  • Hi Lary

    It is worked. Thank  you.

    Dienstag, 30. Juni 2020 17:51