Error Agent Failed Detecting With Reason 0x80072efd
Contents |
Running WSUS 3.0 on Windows 2003 Server Standard Edition Over 200 clients have been detected Update deployments are working send failed with hr = 80072efd Receiving Error: Agent failed detecting with reason: 0x80072efd on Windows XP
Windows Update Client Failed To Detect With Error 0x80072efd
machine. WindowsUpdate.log below. 2007-06-14 12:05:21 1112 a70 Agent ************* 2007-06-14 12:05:21 1112 a70 Agent ** START ** 80070057 wsus Agent: Finding updates [CallerId = AutomaticUpdates] 2007-06-14 12:05:21 1112 a70 Agent ********* 2007-06-14 12:05:22 1112 a70 Misc WARNING: Send failed with hr = 80072efd. 2007-06-14 12:05:22 1112 a70
Wsus 80072efd
Misc WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2007-06-14 12:05:22 1112 a70 Misc WARNING: WinHttp: SendRequestUsingProxy failed for
2003 ServerPart No(none)SummaryWhen you use the Windows Update website or the Microsoft Update Website to check for and install updates, the
80072efd Windows Update
event log reports the error 0x80072efd.Symptoms When you use the Windows®
Wsus Client Diagnostics Tool
Update Website or the Microsoft® Update website to check for and install updates, it fails to wsus 80244010 complete the update and the event log reports the error below: "Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot http://www.winvistatips.com/threads/error-agent-failed-detecting-with-reason-0x80072efd.745370/ download and install updates according to the set schedule. Windows will continue to try to establish a connection.Error: Agent failed detecting with reason: 0x80072efd" Also in thelog file '%Windir%\WindowsUpdate.log'you can see many errors, one of which is: "FATAL: IsUpdateRequired failed with error 0x80072efd"CauseThe WindowsUpdate Agent (WUA)uses theWinHTTP proxy settings to access the WSUS Server. The http://support.rm.com/technicalarticle.asp?cref=tec1770489 WinHTTP proxy settings are separate from the proxy settings in Microsoft Internet Explorer. If you are using aProxy server to access the Internet and the proxy settings are configured for Internet Explorer, and at the same time if WinHTTP proxy settings are set to null, then WUA may fail with the errors as seen above. RequirementsBefore you troubleshoot this issue, you can check the WinHTTP proxy settings and the user's InternetExplorerproxy settings by using the ClientDiag tool. You can download this from http://technet.microsoft.com/en-us/windowsserver/bb466192.aspx For the following procedure youmust have local administrator privileges, so that proxycfg.exe can update the registry of the local computer. Procedure Double-click on the ClientDiag application. Thisdisplays the WinHTTP local machine Proxy settingsandUser IE Proxy settings in the command prompt window. Configure theWinHTTP local machine Proxy settings to use User IE Proxy settings by using the proxycfg utility. To do this,type proxycfg.exe -u in the command prompt. This will force the Windows Automatic Client to use the same proxy settin
Discussions > WSUS 2 Server issues View New Content Page 1 of 1 You cannot start a new topic This topic is locked Error: Agent failed detecting with http://www.wsus.info/index.php?showtopic=5508 reason: 0x80248 This computer has not reported status #1 AdamsL Newbie Group: Validating Posts: 1 Joined: 16-Jun-05 Posted 16 Jun 2005, 13:09 The WSUS has been working fine for months. now http://sysadmins.ru/topic115670.html the computers are showing up in the WSUS console with the following error: Error: Agent failed detecting with reason: 0x80248013. This computer has not reported status in 9 or more days. Any windows update Ideas? 0 Back to top of the page up there ^ MultiQuote Reply #2 AdamL Newbie Group: Regular Members Posts: 3 Joined: 16-Jun-05 Posted 16 Jun 2005, 13:19 2005-06-16 12:43:59 852 5cc AU ############# 2005-06-16 12:43:59 852 5cc AU ## START ## AU: Search for updates 2005-06-16 12:43:59 852 5cc AU ######### 2005-06-16 12:43:59 852 5cc AU <<## SUBMITTED ## AU: Search for error agent failed updates [CallId = {88DD09AE-9B5B-4427-B930-064188BEDDFE}] 2005-06-16 12:43:59 852 59c Agent ************* 2005-06-16 12:43:59 852 59c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] 2005-06-16 12:43:59 852 59c Agent ********* 2005-06-16 12:44:10 852 59c Setup *********** Setup: Checking whether self-update is required *********** 2005-06-16 12:44:10 852 59c Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf 2005-06-16 12:44:10 852 59c Setup Update NOT required for C:\WINDOWS\System32\cdm.dll: target version = 5.8.0.2469, required version = 5.8.0.2469 2005-06-16 12:44:10 852 59c Setup Update NOT required for C:\WINDOWS\System32\iuengine.dll: target version = 5.8.0.2469, required version = 5.8.0.2469 2005-06-16 12:44:10 852 59c Setup Update NOT required for C:\WINDOWS\System32\wuapi.dll: target version = 5.8.0.2469, required version = 5.8.0.2469 2005-06-16 12:44:10 852 59c Setup Update NOT required for C:\WINDOWS\System32\wuauclt.exe: target version = 5.8.0.2469, required version = 5.8.0.2469 2005-06-16 12:44:10 852 59c Setup Update NOT required for C:\WINDOWS\System32\wuauclt1.exe: target version = 5.8.0.2469, required version = 5.8.0.2469 2005-06-16 12:44:10 852 59c Setup Update NOT required for C:\WINDOWS\System32\wuaucpl.cpl: target version = 5.8.0.2469, required version = 5.8.0.2469 2005-06-16 12:44:10 852 59c Setup Update NOT required for C:\WINDOWS\System32\wuaueng.dll: target version = 5.8.0.2469, required version = 5.8.0.2469 2005-06-16 12:44:10 852 59c Setup Update NOT required for C:\WINDOWS\System32\wuaueng1.dll: target ver