SCCM Scan agent Sources are current, but Invalid. TTL is also invalid issue

Question

_{Monday, November 27, 2017 11:28 AM}

I have an SCCM 1706 fresh deployment, I noticed that all Secondary sites machines are getting an error in SCAN agent log:

ScanJob({0A20915E-39CE-409D-8AAD-475855170622}): CScanJob::OnScanComplete -Scan Failed with Error=0x8024401c

CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631

I tried to reinstall the agent with no help.

please advise.

Ahmed Ali

All replies (6)

_{Monday, November 27, 2017 12:01 PM}

0x8024401c is timeout. Is the SUP/WSUS working?

Torsten Meringer | http://www.mssccmfaq.de

_{Monday, November 27, 2017 12:48 PM}

yes working 

I noticed when running scan agent on any machine on same boundary of the primary site it will has:

Sources are current and valid. TTLs are however, invalid.

however with the machines that linked to secondary site will have:

Sources are current, but Invalid. TTL is also invalid.

Ahmed Ali

_{Tuesday, November 28, 2017 5:37 AM}

Hi,

How many SUPs are there? Is there SUP for secondary site? If so, be sure the SUP is healthy and synced with Primary Site SUP.

Check below Knowledge article and search the error code for troubleshooting the issue:

https://support.microsoft.com/en-us/help/3090184/how-to-troubleshoot-software-update-scan-failures-in-system-center-201

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, January 29, 2018 11:19 AM}

I am experiencing the same problem, but I am using a previous version of CM. (SCCM 1702 hotfix rollup KB4019926). did you find where is the problem?

thank you in advance.

_{Monday, May 7, 2018 8:21 AM}

I am also facing the same issue. Below is the thread - 

https://social.technet.microsoft.com/Forums/en-US/c47a7c4c-88cd-4ce3-8f96-7658c817fdfa/same-as-http-status-408-the-server-timed-out-waiting-for-the-request?forum=ConfigMgrDeployment

Hemanth

_{Wednesday, November 21, 2018 6:20 AM}

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?

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/

Hemanth