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:
{31BC61EF-E274-41A6-8634-C8394D328D25}2014-02-1315:51:02:677+01001148101{00000000-0000-0000-0000-000000000000}080072efdCcmExecFailureSoftwareSynchronizationWindowsUpdateClient failed to detect with error 0x80072efd.
WindowsUpdate.log:
2014-02-1314:51:01:92143961d44 COMAPI -------------2014-02-1314:51:01:92143961d44 COMAPI -- START -- COMAPI:Search[ClientId=CcmExec]2014-02-1314:51:01:92143961d44 COMAPI ---------2014-02-1314:51:01:921716724Agent*************2014-02-1314:51:01:92143961d44 COMAPI <<-- SUBMITTED -- COMAPI:Search[ClientId=CcmExec]2014-02-1314:51:01:921716724Agent** START **Agent:Finding updates [CallerId=CcmExec]2014-02-1314:51:01:921716724Agent*********2014-02-1314:51:01:921716724Agent*Include potentially superseded updates
2014-02-1314:51:01:921716724Agent*Online=Yes;Ignore download priority =Yes2014-02-1314:51:01:921716724Agent*Criteria="(DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')"2014-02-1314:51:01:921716724Agent*ServiceID={3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}Managed2014-02-1314:51:01:921716724Agent*SearchScope={Machine}2014-02-1314:51:01:968716724 PT +++++++++++ PT:Synchronizing server updates +++++++++++2014-02-1314:51:01:968716724 PT +ServiceId={3DA21691-E39D-4DA6-8A4B-B43877BCB1B7},Server URL =HTTP://DEPLOYSERVER.domain.DE:8530/ClientWebService/client.asmx'>HTTP://DEPLOYSERVER.domain.DE:8530/ClientWebService/client.asmx2014-02-1314:51:03:013716724Misc WARNING:SendRequest failed with hr =80072efd.ProxyList used:<172.16.10.10:8080>BypassList used :<(null)>AuthSchemes used :<>2014-02-1314:51:03:013716724 PT +Last proxy send request failed with hr =0x80072EFD, HTTP status code =02014-02-1314:51:03:013716724 PT +Caller provided proxy =No2014-02-1314:51:03:013716724 PT +Proxy list used =172.16.10.10:80802014-02-1314:51:03:013716724 PT +Bypass list used =<NULL>2014-02-1314:51:03:013716724 PT +Caller provided credentials =No2014-02-1314:51:03:013716724 PT +Impersonate flags =02014-02-1314:51:03:013716724 PT +Possible authorization schemes used =2014-02-1314:51:03:013716724 PT WARNING:GetConfig failure, error =0x80072EFD, soap client error =5, soap error code =0, HTTP status code =2002014-02-1314:51:03:013716724 PT WARNING:PTError:0x80072efd2014-02-1314:51:03:013716724 PT WARNING:GetConfig_WithRecovery failed:0x80072efd2014-02-1314:51:03:013716724 PT WARNING:RefreshConfig failed:0x80072efd2014-02-1314:51:03:013716724 PT WARNING:RefreshPTState failed:0x80072efd2014-02-1314:51:03:013716724 PT WARNING:SyncofUpdates:0x80072efd2014-02-1314:51:03:013716724 PT WARNING:SyncServerUpdatesInternal failed:0x80072efd2014-02-1314:51:03:013716724Agent* WARNING:Failed to synchronize, error =0x80072EFD2014-02-1314:51:03:013716724Agent* WARNING:Exit code =0x80072EFD2014-02-1314:51:03:013716724Agent*********2014-02-1314:51:03:013716724Agent**END**Agent:Finding updates [CallerId=CcmExec]2014-02-1314:51:03:013716724Agent*************2014-02-1314:51:03:013716724Agent WARNING: WU client failed Searchingfor update with error 0x80072efd2014-02-1314:51:03:02943961d44 COMAPI >>-- RESUMED -- COMAPI:Search[ClientId=CcmExec]2014-02-1314:51:03:02943961d44 COMAPI -Updates found =02014-02-1314:51:03:02943961d44 COMAPI - WARNING:Exit code =0x00000000,Result code =0x80072EFD2014-02-1314:51:03:02943961d44 COMAPI ---------2014-02-1314:51:03:02943961d44 COMAPI --END-- COMAPI:Search[ClientId=CcmExec]2014-02-1314:51:03:02943961d44 COMAPI -------------2014-02-1314:51:03:02943961d44 COMAPI WARNING:Operation failed due to earlier error, hr=80072EFD2014-02-1314:51:03:02943961d44 COMAPI FATAL:Unable to complete asynchronous search.(hr=80072EFD)2014-02-1314:51:08:021716724Report REPORT EVENT:{9FCAD677-4C4E-4F97-801B-26871FBE087A}2014-02-1314:51:03:013+01001148101{00000000-0000-0000-0000-000000000000}080072efdCcmExecFailureSoftwareSynchronizationWindowsUpdateClient failed to detect with error 0x80072efd.2014-02-1314:51:08:021716724ReportCWERReporter::HandleEvents- WER report upload completed with status 0x82014-02-1314:51:08:021716724Report WER Report sent:7.5.7601.175140x80072efd00000000-0000-0000-0000-000000000000Scan101Managed2014-02-1314:51:08:021716724ReportCWERReporter finishing event handling.(00000000)
ScanAgent.log:
ScanJob({32B50DD3-9D05-405A-A7B8-1682533DE396}):CScanJob::OnScanComplete-ScanFailedwithError=0x80072efdScanAgent13.02.201415:54:058156(0x1FDC)ScanJob({32B50DD3-9D05-405A-A7B8-1682533DE396}):CScanJob::ScheduleScanRetry-ScanRetryTimer task successfully scheduled.Will wake up innext1799 seconds ScanAgent13.02.201415:54:058156(0x1FDC)ScanJob({32B50DD3-9D05-405A-A7B8-1682533DE396}):CScanJob::OnScanComplete-ScanRetry successfully scheduled ScanAgent13.02.201415:54:058156(0x1FDC)ScanJob({32B50DD3-9D05-405A-A7B8-1682533DE396}):CScanJobManager::OnScanComplete-Scan has failed, scan request will be pending for scan retry cycle.ScanAgent13.02.201415:54:058156(0x1FDC)CScanAgent::ScanCompleteCallback- failed at OnScanCompletewith error=0x87d00631ScanAgent13.02.201415:54:058156(0x1FDC)ScanJob({95B11B6C-EC6B-433A-8B7D-9C00F64CA6FC}):CScanJob::OnScanRetry-Requesting scan ScanAgent13.02.201415:55:407284(0x1C74)Sources are current, but Invalid. TTL is also invalid.ScanAgent13.02.201415:55:402092(0x082C)
WUAHandler.log:
Its a WSUS UpdateSource type ({4B577F7B-0849-46A0-934C-CAFFC46B0BBF}), adding it.WUAHandler13.02.201415:55:402092(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)AddedUpdateSource({4B577F7B-0849-46A0-934C-CAFFC46B0BBF})of content type:2WUAHandler13.02.201415:55:402092(0x082C)Scan results will include superseded updates only when they are superseded by service packs and definition updates.WUAHandler13.02.201415:55:402092(0x082C)SearchCriteriais(DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')WUAHandler13.02.201415:55:402092(0x082C)Async searching of updates usingWUAgent started.WUAHandler13.02.201415:55:402092(0x082C)Async searching completed.WUAHandler13.02.201415:55:415236(0x1474)OnSearchComplete-Failed to end search job.Error=0x80072efd.WUAHandler13.02.201415:55:412092(0x082C)Scan failed with error =0x80072efd.WUAHandler13.02.201415:55:412092(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