ScanJob({32B50DD3-9D05-405A-A7B8-1682533DE396}): CScanJob::OnScanComplete -Scan Failed with Error=0x80072efd ScanAgent 13.02.2014 15:54:05 8156 (0x1FDC)
ScanJob({32B50DD3-9D05-405A-A7B8-1682533DE396}): CScanJob::ScheduleScanRetry- ScanRetry Timer task successfully scheduled. Will wake up in next 1799 seconds ScanAgent 13.02.2014 15:54:05 8156 (0x1FDC)
ScanJob({32B50DD3-9D05-405A-A7B8-1682533DE396}): CScanJob::OnScanComplete - Scan Retry successfully scheduled ScanAgent 13.02.2014 15:54:05 8156 (0x1FDC)
ScanJob({32B50DD3-9D05-405A-A7B8-1682533DE396}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle. ScanAgent 13.02.2014 15:54:05 8156 (0x1FDC)
CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631 ScanAgent 13.02.2014 15:54:05 8156 (0x1FDC)
ScanJob({95B11B6C-EC6B-433A-8B7D-9C00F64CA6FC}): CScanJob::OnScanRetry- Requesting scan ScanAgent 13.02.2014 15:55:40 7284 (0x1C74)
Sources are current, but Invalid. TTL is also invalid. ScanAgent 13.02.2014 15:55:40 2092 (0x082C)
WUAHandler.log:
Its a WSUS Update Source type ({4B577F7B-0849-46A0-934C-CAFFC46B0BBF}), adding it. WUAHandler 13.02.2014 15:55:40 2092 (0x082C)
Existing WUA Managed server was already set (HTTP://DEPLOYSERVER.domain.DE:8530), skipping Group Policy registration. WUAHandler 13.02.2014 15:55:40 2092 (0x082C)
Added Update Source ({4B577F7B-0849-46A0-934C-CAFFC46B0BBF}) of content type: 2 WUAHandler 13.02.2014 15:55:40 2092 (0x082C)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 13.02.2014 15:55:40 2092 (0x082C)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 13.02.2014 15:55:40 2092 (0x082C)
Async searching of updates using WUAgent started. WUAHandler 13.02.2014 15:55:40 2092 (0x082C)
Async searching completed. WUAHandler 13.02.2014 15:55:41 5236 (0x1474)
OnSearchComplete - Failed to end search job. Error = 0x80072efd. WUAHandler 13.02.2014 15:55:41 2092 (0x082C)
Scan failed with error = 0x80072efd. WUAHandler 13.02.2014 15:55:41 2092 (0x082C)
I am wondering, why the client want to use a proxy-adress ... as seen in the WindowsUpdate.log
"WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <172.16.10.10:8080> Bypass List used : <(null)> Auth Schemes used : <>"
Maybe this has to do with the fact of our problem?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hello,
we're using SCCM 2012 on Windows Server 2008 R2 with Windows 7 Prof Clients.
On one Client we have several errors with the deployment of the Windows Updates, e.g. "Windows Update Client failed to detect with error 0x80072efd."
Windows Firewall on the server and on the clients are disabled.
Here the results of the log-files
SoftwareDistribution\ReportingEvents.log:
WindowsUpdate.log:
ScanAgent.log:
I am wondering, why the client want to use a proxy-adress ... as seen in the WindowsUpdate.log
"WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <172.16.10.10:8080> Bypass List used : <(null)> Auth Schemes used : <>"
Maybe this has to do with the fact of our problem?
How can we delete this proxy-entry?
Regards
Marcel
Share this post
Link to post
Share on other sites