我最近开始testingSCCM 2012的SUPfunction。我已经按照指南设置了服务器,并且似乎都工作正常。 正在下载更新并显示在服务器控制台上。
然而,在客户端,似乎有一些初期问题。 客户正在显示他们需要更新,但没有下载。
我查了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)
但是今天整天都有和以前一样的错误。 如果任何人可以阐明为什么发生这种情况,以及如何补救,那么将不胜感激。
0x80244022意味着与HTTP状态503相同 – 服务暂时超载。 (来源:Windows Update代理)
我会build议这是一个实际的WSUS组件的问题,它与HTTP 503绑定的事实将解释为什么它有时工作,有时不。 如果在客户端的WindowsUpdate.log中看到任何有趣的内容,那么也可以查看问题的严重程度,然后再查找一下。
在我看来,虽然这是一个WSUS的问题,而不是ConfigMgr,如果你也经历一个代理服务器,也可能是一个问题。 仅供参考,0x87d00631表示扫描重试正在处理。
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/