我最近开始测试 SCCM 2012 的 SUP 功能。我按照指南设置了服务器，一切似乎都运行良好。更新正在下载并显示在服务器控制台上。
然而在客户端方面似乎存在一些初期问题。客户端显示需要更新但却没有下载。
我检查了 WUAHandler.log 并发现此错误经常重复出现。
Its a WSUS Update Source type ({804E0972-01D9-479F-8E38-E58576D82725}), adding it. WUAHandler 12/07/2013 12:18:16 3216 (0x0C90)
Existing WUA Managed server was already set (HTTP://Ourservername.LOCAL:8530), skipping Group Policy registration. WUAHandler 12/07/2013 12:18:16 3216 (0x0C90)
Added Update Source ({804E0972-01D9-479F-8E38-E58576D82725}) of content type: 2 WUAHandler 12/07/2013 12:18:16 3216 (0x0C90)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 12/07/2013 12:18:16 3216 (0x0C90)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 12/07/2013 12:18:16 3216 (0x0C90)
Async searching of updates using WUAgent started. WUAHandler 12/07/2013 12:18:16 3216 (0x0C90)
Async searching completed. WUAHandler 12/07/2013 12:18:17 5284 (0x14A4)
OnSearchComplete - Failed to end search job. Error = 0x80244022. WUAHandler 12/07/2013 12:18:17 3216 (0x0C90)
Scan failed with error = 0x80244022. WUAHandler 12/07/2013 12:18:17 3216 (0x0C90)
我查看了 Scanagent.log，里面全是红色。主要重复相同的 0x80244022 错误，还有 0x87d00631 错误。
Sources are current, but Invalid. TTL is also invalid. ScanAgent 12/07/2013 12:18:14 6104 (0x17D8)
ScanJob({2821C25B-DD2A-4505-B406-CB4642515CF9}): CScanJob::OnScanRetry- Requesting scan ScanAgent 12/07/2013 12:18:15 6104 (0x17D8)
No CatScan history exists ScanAgent 12/07/2013 12:18:15 3216 (0x0C90)
ScanJob({4A6446FE-72C7-46E6-AF39-7D6BCD2DC337}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244022 ScanAgent 12/07/2013 12:18:15 5240 (0x1478)
ScanJob({4A6446FE-72C7-46E6-AF39-7D6BCD2DC337}): CScanJob::ScheduleScanRetry- ScanRetry Timer task successfully scheduled. Will wake up in next 1798 seconds ScanAgent 12/07/2013 12:18:16 5240 (0x1478)
ScanJob({4A6446FE-72C7-46E6-AF39-7D6BCD2DC337}): CScanJob::OnScanComplete - Scan Retry successfully scheduled ScanAgent 12/07/2013 12:18:16 5240 (0x1478)
Sources are current, but Invalid. TTL is also invalid. ScanAgent 12/07/2013 12:18:16 3216 (0x0C90)
ScanJob({4A6446FE-72C7-46E6-AF39-7D6BCD2DC337}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle. ScanAgent 12/07/2013 12:18:16 5240 (0x1478)
CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631 ScanAgent 12/07/2013 12:18:16 5240 (0x1478)
ScanJob({2821C25B-DD2A-4505-B406-CB4642515CF9}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244022 ScanAgent 12/07/2013 12:18:17 5240 (0x1478)
ScanJob({2821C25B-DD2A-4505-B406-CB4642515CF9}): CScanJob::ScheduleScanRetry- ScanRetry Timer task successfully scheduled. Will wake up in next 1798 seconds ScanAgent 12/07/2013 12:18:17 5240 (0x1478)
ScanJob({2821C25B-DD2A-4505-B406-CB4642515CF9}): CScanJob::OnScanComplete - Scan Retry successfully scheduled ScanAgent 12/07/2013 12:18:17 5240 (0x1478)
ScanJob({2821C25B-DD2A-4505-B406-CB4642515CF9}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle. ScanAgent 12/07/2013 12:18:17 5240 (0x1478)
CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631 ScanAgent 12/07/2013 12:18:17 5240 (0x1478)
我在网上搜索可能的原因，但一无所获。我想知道是否有人可以解释一下这个问题。
同样非常奇怪的是昨晚扫描确实有效并且在 WUAHandler 中我得到了这个。
Its a WSUS Update Source type ({804E0972-01D9-479F-8E38-E58576D82725}), adding it. WUAHandler 12/07/2013 06:43:27 5468 (0x155C)
Existing WUA Managed server was already set (HTTP://Ourservername.LOCAL:8530), skipping Group Policy registration. WUAHandler 12/07/2013 06:43:57 5468 (0x155C)
Added Update Source ({804E0972-01D9-479F-8E38-E58576D82725}) of content type: 2 WUAHandler 12/07/2013 06:43:57 5468 (0x155C)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 12/07/2013 06:43:57 5468 (0x155C)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 12/07/2013 06:43:57 5468 (0x155C)
Async searching of updates using WUAgent started. WUAHandler 12/07/2013 06:43:57 5468 (0x155C)
Async searching completed. WUAHandler 12/07/2013 06:44:51 592 (0x0250)
Successfully completed scan. WUAHandler 12/07/2013 06:46:56 2568 (0x0A08)
The new content version (4) of update source is less than before (5), continuing. WUAHandler 12/07/2013 07:28:10 5468 (0x155C)
但今天一整天我都遇到和以前一样的错误。如果有人能解释一下为什么会发生这种情况以及如何解决，我将不胜感激。
答案1
0x80244022 表示与 HTTP 状态 503 相同 - 服务暂时过载。（来源：Windows Update 代理）
我认为这是实际 WSUS 组件的问题，它与 HTTP 503 相关联这一事实可以解释为什么它有时有效，有时无效。查看客户端上的 WindowsUpdate.log 中是否有任何有趣的内容也很有用，可以了解问题的严重程度并进一步确定问题所在。
在我看来，虽然这是 WSUS 的问题而不是 ConfigMgr 的问题，但如果您也使用代理服务器，也可能是代理服务器的问题。仅供参考，0x87d00631 表示扫描重试正在等待。
答案2
OnSearchComplete - Failed to end search job. Error = 0x80244022.
此错误可能由与 WSUS Web 服务器的连接或访问相关的许多不同问题导致。
就我而言，我发现 IIS 应用程序池（WSUSPool）已崩溃/停止。
根据下面链接的博客，这是一个由于分配给应用程序池的内存不足而导致的常见问题。
http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/