WSUS running not well with Windows 2003 - error code :80072efe and 80072efd

Hi there:
Here's the story.
We got a new IBM X226 server running Windows 2003 /w sp1. After joining it
to our domain, we promoted it to DC. Then we configure IIS 6.0 and install
WSUS 2.0 sp1 to use port 80 for windows update. We did the WSUS
installation twice because the first time we cnofigure it to be a replica
and then we decided to make it a downstream WSUS server.
There was an error message shown on the to do list in WSUS console saying
that there are problems with selfupdate but we managed to solved it by
changing some settings in IIS. Now, here is the problem! All client PCs
can be found since we use GPO to set up their WSUS server to be this one.
Yet all PCs' show same status - "not yet reported". More clue can be found
from windowsupdate.log. It looks like:
2007-01-11 11:23:52 1116 718 AU #############
2007-01-11 11:23:52 1116 718 AU ## START ## AU: Search for updates
2007-01-11 11:23:52 1116 718 AU #########
2007-01-11 11:23:52 1116 718 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
2007-01-11 11:23:52 1116 5a8 Agent *************
2007-01-11 11:23:52 1116 5a8 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2007-01-11 11:23:52 1116 5a8 Agent *********
2007-01-11 11:23:52 1116 5a8 Setup *********** Setup: Checking whether
self-update is required ***********
2007-01-11 11:23:52 1116 5a8 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version =
5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
version = 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2007-01-11 11:23:52 1116 5a8 Setup * IsUpdateRequired = No
2007-01-11 11:23:55 1116 5a8 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2007-01-11 11:23:55 1116 5a8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://s64101101/ClientWebService/client.asmx
2007-01-11 11:23:55 1116 5a8 PT Initializing simple targeting cookie,
clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
name = c64101010.d161
2007-01-11 11:23:55 1116 5a8 PT Server URL =
http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
2007-01-11 11:23:55 1116 5a8 Misc WARNING: Send failed with hr = 80072efe.
2007-01-11 11:23:55 1116 5a8 Misc WARNING: SendRequest failed with hr =
80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2007-01-11 11:23:55 1116 5a8 PT + Last proxy send request failed with hr =
0x80072EFE, HTTP status code = 0
2007-01-11 11:23:55 1116 5a8 PT + Caller provided credentials = No
2007-01-11 11:23:55 1116 5a8 PT + Impersonate flags = 0
2007-01-11 11:23:55 1116 5a8 PT + Possible authorization schemes used =
2007-01-11 11:23:55 1116 5a8 PT WARNING: GetAuthorizationCookie failure,
error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP status
code = 200
2007-01-11 11:23:55 1116 5a8 PT WARNING: Sync of Updates: 0x80072efe
2007-01-11 11:23:55 1116 5a8 Agent * WARNING: Failed to synchronize, error
= 0x80072EFE
2007-01-11 11:23:55 1116 5a8 Agent * WARNING: Exit code = 0x80072EFE
2007-01-11 11:23:55 1116 5a8 Agent *********
2007-01-11 11:23:55 1116 5a8 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2007-01-11 11:23:55 1116 5a8 Agent *************
2007-01-11 11:23:55 1116 5a8 Agent WARNING: WU client failed Searching for
update with error 0x80072efe
2007-01-11 11:23:55 1116 5a8 AU >>## RESUMED ## AU: Search for updates
[CallId = {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
2007-01-11 11:23:55 1116 5a8 AU # WARNING: Search callback failed, result
= 0x80072EFE
2007-01-11 11:23:55 1116 5a8 AU #########
2007-01-11 11:23:55 1116 5a8 AU ## END ## AU: Search for updates [CallId
= {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
2007-01-11 11:23:55 1116 5a8 AU #############
2007-01-11 11:23:55 1116 5a8 AU AU setting next detection timeout to
2007-01-11 07:09:45
2007-01-11 11:24:00 1116 46c Report REPORT EVENT:
{4B3DBFFC-43D7-4671-AEE8-78D66EF9068D} 2007-01-11 11:23:55+0800 1 148 101
{00000000-0000-0000-0000-000000000000} 0 80072efe AutomaticUpdates Failure
Software Synchronization Error: Agent failed detecting with reason:
0x80072efe
2007-01-11 11:30:50 1116 578 DnldMgr Error 0x80072efd occurred while
downloading update; notifying dependent calls.
2007-01-11 11:37:01 1116 5a8 PT Initializing simple targeting cookie,
clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
name = c64101010.d161
2007-01-11 11:37:01 1116 5a8 PT Server URL =
http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
2007-01-11 11:37:03 1116 5a8 Misc WARNING: Send failed with hr = 80072efe.
2007-01-11 11:37:03 1116 5a8 Misc WARNING: SendRequest failed with hr =
80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2007-01-11 11:37:03 1116 5a8 PT + Last proxy send request failed with hr =
0x80072EFE, HTTP status code = 0
2007-01-11 11:37:03 1116 5a8 PT + Caller provided credentials = No
2007-01-11 11:37:03 1116 5a8 PT + Impersonate flags = 0
2007-01-11 11:37:03 1116 5a8 PT + Possible authorization schemes used =
2007-01-11 11:37:03 1116 5a8 PT WARNING: GetAuthorizationCookie failure,
error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP status
code = 200
2007-01-11 11:37:03 1116 5a8 Report WARNING: Reporter failed to upload
events with hr = 80072efe.
2007-01-11 11:50:59 1116 87c DnldMgr Error 0x80072efd occurred while
downloading update; notifying dependent calls.
2007-01-11 12:00:09 1116 718 AU Forced install timer expired for scheduled
install
2007-01-11 12:06:29 1116 53c PT Initializing simple targeting cookie,
clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
name = c64101010.d161
2007-01-11 12:06:29 1116 53c PT Server URL =
http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
2007-01-11 12:06:29 1116 53c Misc WARNING: Send failed with hr = 80072efe.
2007-01-11 12:06:29 1116 53c Misc WARNING: SendRequest failed with hr =
80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2007-01-11 12:06:29 1116 53c PT + Last proxy send request failed with hr =
0x80072EFE, HTTP status code = 0
2007-01-11 12:06:29 1116 53c PT + Caller provided credentials = No
2007-01-11 12:06:29 1116 53c PT + Impersonate flags = 0
2007-01-11 12:06:29 1116 53c PT + Possible authorization schemes used =
2007-01-11 12:06:29 1116 53c PT WARNING: GetAuthorizationCookie failure,
error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP status
code = 200
2007-01-11 12:06:29 1116 53c Report WARNING: Reporter failed to upload
events with hr = 80072efe.
2007-01-11 12:10:03 1116 46c DnldMgr *********** DnldMgr: Downloading
regulation Odf ***********
2007-01-11 12:10:03 1116 46c DnldMgr * ServiceId =
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2007-01-11 12:10:03 1116 46c DnldMgr * URL =
http://rs.update.microsoft.com/odf/v6odf.xml
2007-01-11 12:10:07 1116 46c Misc WARNING: Send failed with hr = 80072efd.
2007-01-11 12:10:07 1116 46c Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error 0x80072efd
2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2007-01-11 12:10:09 1116 46c Misc WARNING: Send failed with hr = 80072efd.
2007-01-11 12:10:09 1116 46c Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error 0x80072efd
2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2007-01-11 12:10:11 1116 46c Misc WARNING: Send failed with hr = 80072efd.
2007-01-11 12:10:11 1116 46c Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error 0x80072efd
2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2007-01-11 12:10:14 1116 46c Misc WARNING: Send failed with hr = 80072efd.
2007-01-11 12:10:14 1116 46c Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
used : <>
2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error 0x80072efd
2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
failed with 0x80072efd
2007-01-11 12:10:14 1116 46c DnldMgr FATAL:
DM:CDownloadRegulator::DownloadOdf: WinHttpDownloadFile failed with
0x80072efd.
2007-01-11 12:10:14 1116 46c DnldMgr * Last proxy send request failed with
hr = 0x80072EFD, HTTP status code = 0
2007-01-11 12:10:14 1116 46c DnldMgr * Caller provided credentials = No
2007-01-11 12:10:14 1116 46c DnldMgr * Impersonate flags = 0
2007-01-11 12:10:14 1116 46c DnldMgr * Possible authorization schemes used
=
2007-01-11 12:10:14 1116 46c DnldMgr FATAL: DM:CDownloadRegulator::Refresh:
DownloadOdf failed with 0x80072efd.
2007-01-11 12:10:14 1116 46c DnldMgr FATAL:
DM:CAgentDownloadManager::ProcessWorkItem: Refresh failed with 0x80072efd.
2007-01-11 12:10:27 1116 bd0 DnldMgr Error 0x80072efd occurred while
downloading update; notifying dependent calls.



Well, I hope someone can help me. Many thanksss.


Neil Chou, Sinotech Engineering Consultants, Ltd.
Email: neil.chou@msa.hinet.net ; chous@sinotech.com.tw

0x80072efd - ERROR INTERNET CANNOT CONNECT

0x80072efe - ERROR INTERNET CONNECTION ABORTED

Quoting from one of Lawrence Garvin's replies last April.
===================================
In essence this is a infrastructure problem. The WUA records the '2efd'
error when it gets /NO/ response from a webserver at the designated URL.
This can actually happen for a number of reasons, but the bottom line is
that there is not a functioning webserver available at the specified URL.

(a) The web server may exist and be stopped; or the WWW service is not
running.

(b) The port number may be incorrect. (Are you positive the WSUS server is
installed on the alternate port?)

(c) The IP Address may be incorrect.

(d) A router, firewall, or proxy server may be blocking access. (Do you have
any of these devices between the client and WSUS server? If so, does the
device have the necessary access rule in place? NOTE: Normally, this type of
error will return a '403' from the proxy server, but that's not guaranteed,
as it's dependent on the proxy server configuration.)

(e) DNS would be an issue only if you were using a hostname-based URL.
You're not, so DNS is irrelevant, but a defective DNS resolver /can/ produce
a '2efd' error if using a hostname-based URL.

Best testing methodology is to determine if this error is replicatable on
/all/ clients, or only selected clients. If /all/ clients, look to the
server for the cause; if only selected clients, look to the common
infrastructure elements of those clients that do /not/ exist on the working
clients. (e.g. item (d) and (e) above)
===================




On Fri, 12 Jan 2007 14:03:08 +0800, "Neil Chou" <chous@sinotech.com.tw> wrote:

>Hi there:
>Here's the story.
>We got a new IBM X226 server running Windows 2003 /w sp1. After joining it
>to our domain, we promoted it to DC. Then we configure IIS 6.0 and install
>WSUS 2.0 sp1 to use port 80 for windows update. We did the WSUS
>installation twice because the first time we cnofigure it to be a replica
>and then we decided to make it a downstream WSUS server.
>There was an error message shown on the to do list in WSUS console saying
>that there are problems with selfupdate but we managed to solved it by
>changing some settings in IIS. Now, here is the problem! All client PCs
>can be found since we use GPO to set up their WSUS server to be this one.
>Yet all PCs' show same status - "not yet reported". More clue can be found
>from windowsupdate.log. It looks like:
>2007-01-11 11:23:52 1116 718 AU #############
>2007-01-11 11:23:52 1116 718 AU ## START ## AU: Search for updates
>2007-01-11 11:23:52 1116 718 AU #########
>2007-01-11 11:23:52 1116 718 AU <<## SUBMITTED ## AU: Search for updates
>[CallId = {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
>2007-01-11 11:23:52 1116 5a8 Agent *************
>2007-01-11 11:23:52 1116 5a8 Agent ** START ** Agent: Finding updates
>[CallerId = AutomaticUpdates]
>2007-01-11 11:23:52 1116 5a8 Agent *********
>2007-01-11 11:23:52 1116 5a8 Setup *********** Setup: Checking whether
>self-update is required ***********
>2007-01-11 11:23:52 1116 5a8 Setup * Inf file:
>C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version =
>5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
>version = 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required version
>= 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
>version = 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
>version = 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
>version = 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
>version = 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
>version = 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
>version = 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required version
>= 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required version
>= 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required version
>= 5.8.0.2607
>2007-01-11 11:23:52 1116 5a8 Setup * IsUpdateRequired = No
>2007-01-11 11:23:55 1116 5a8 PT +++++++++++ PT: Synchronizing server
>updates +++++++++++
>2007-01-11 11:23:55 1116 5a8 PT + ServiceId =
>{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
>http://s64101101/ClientWebService/client.asmx
>2007-01-11 11:23:55 1116 5a8 PT Initializing simple targeting cookie,
>clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
>name = c64101010.d161
>2007-01-11 11:23:55 1116 5a8 PT Server URL =
>http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
>2007-01-11 11:23:55 1116 5a8 Misc WARNING: Send failed with hr = 80072efe.
>2007-01-11 11:23:55 1116 5a8 Misc WARNING: SendRequest failed with hr =
>80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
>used : <>
>2007-01-11 11:23:55 1116 5a8 PT + Last proxy send request failed with hr =
>0x80072EFE, HTTP status code = 0
>2007-01-11 11:23:55 1116 5a8 PT + Caller provided credentials = No
>2007-01-11 11:23:55 1116 5a8 PT + Impersonate flags = 0
>2007-01-11 11:23:55 1116 5a8 PT + Possible authorization schemes used =
>2007-01-11 11:23:55 1116 5a8 PT WARNING: GetAuthorizationCookie failure,
>error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP status
>code = 200
>2007-01-11 11:23:55 1116 5a8 PT WARNING: Sync of Updates: 0x80072efe
>2007-01-11 11:23:55 1116 5a8 Agent * WARNING: Failed to synchronize, error
>= 0x80072EFE
>2007-01-11 11:23:55 1116 5a8 Agent * WARNING: Exit code = 0x80072EFE
>2007-01-11 11:23:55 1116 5a8 Agent *********
>2007-01-11 11:23:55 1116 5a8 Agent ** END ** Agent: Finding updates
>[CallerId = AutomaticUpdates]
>2007-01-11 11:23:55 1116 5a8 Agent *************
>2007-01-11 11:23:55 1116 5a8 Agent WARNING: WU client failed Searching for
>update with error 0x80072efe
>2007-01-11 11:23:55 1116 5a8 AU >>## RESUMED ## AU: Search for updates
>[CallId = {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
>2007-01-11 11:23:55 1116 5a8 AU # WARNING: Search callback failed, result
>= 0x80072EFE
>2007-01-11 11:23:55 1116 5a8 AU #########
>2007-01-11 11:23:55 1116 5a8 AU ## END ## AU: Search for updates [CallId
>= {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
>2007-01-11 11:23:55 1116 5a8 AU #############
>2007-01-11 11:23:55 1116 5a8 AU AU setting next detection timeout to
>2007-01-11 07:09:45
>2007-01-11 11:24:00 1116 46c Report REPORT EVENT:
>{4B3DBFFC-43D7-4671-AEE8-78D66EF9068D} 2007-01-11 11:23:55+0800 1 148 101
>{00000000-0000-0000-0000-000000000000} 0 80072efe AutomaticUpdates Failure
>Software Synchronization Error: Agent failed detecting with reason:
>0x80072efe
>2007-01-11 11:30:50 1116 578 DnldMgr Error 0x80072efd occurred while
>downloading update; notifying dependent calls.
>2007-01-11 11:37:01 1116 5a8 PT Initializing simple targeting cookie,
>clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
>name = c64101010.d161
>2007-01-11 11:37:01 1116 5a8 PT Server URL =
>http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
>2007-01-11 11:37:03 1116 5a8 Misc WARNING: Send failed with hr = 80072efe.
>2007-01-11 11:37:03 1116 5a8 Misc WARNING: SendRequest failed with hr =
>80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
>used : <>
>2007-01-11 11:37:03 1116 5a8 PT + Last proxy send request failed with hr =
>0x80072EFE, HTTP status code = 0
>2007-01-11 11:37:03 1116 5a8 PT + Caller provided credentials = No
>2007-01-11 11:37:03 1116 5a8 PT + Impersonate flags = 0
>2007-01-11 11:37:03 1116 5a8 PT + Possible authorization schemes used =
>2007-01-11 11:37:03 1116 5a8 PT WARNING: GetAuthorizationCookie failure,
>error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP status
>code = 200
>2007-01-11 11:37:03 1116 5a8 Report WARNING: Reporter failed to upload
>events with hr = 80072efe.
>2007-01-11 11:50:59 1116 87c DnldMgr Error 0x80072efd occurred while
>downloading update; notifying dependent calls.
>2007-01-11 12:00:09 1116 718 AU Forced install timer expired for scheduled
>install
>2007-01-11 12:06:29 1116 53c PT Initializing simple targeting cookie,
>clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
>name = c64101010.d161
>2007-01-11 12:06:29 1116 53c PT Server URL =
>http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
>2007-01-11 12:06:29 1116 53c Misc WARNING: Send failed with hr = 80072efe.
>2007-01-11 12:06:29 1116 53c Misc WARNING: SendRequest failed with hr =
>80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
>used : <>
>2007-01-11 12:06:29 1116 53c PT + Last proxy send request failed with hr =
>0x80072EFE, HTTP status code = 0
>2007-01-11 12:06:29 1116 53c PT + Caller provided credentials = No
>2007-01-11 12:06:29 1116 53c PT + Impersonate flags = 0
>2007-01-11 12:06:29 1116 53c PT + Possible authorization schemes used =
>2007-01-11 12:06:29 1116 53c PT WARNING: GetAuthorizationCookie failure,
>error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP status
>code = 200
>2007-01-11 12:06:29 1116 53c Report WARNING: Reporter failed to upload
>events with hr = 80072efe.
>2007-01-11 12:10:03 1116 46c DnldMgr *********** DnldMgr: Downloading
>regulation Odf ***********
>2007-01-11 12:10:03 1116 46c DnldMgr * ServiceId =
>{9482F4B4-E343-43B6-B170-9A65BC822C77}
>2007-01-11 12:10:03 1116 46c DnldMgr * URL =
>http://rs.update.microsoft.com/odf/v6odf.xml
>2007-01-11 12:10:07 1116 46c Misc WARNING: Send failed with hr = 80072efd.
>2007-01-11 12:10:07 1116 46c Misc WARNING: SendRequest failed with hr =
>80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
>used : <>
>2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
>failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error 0x80072efd
>2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp:
>SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
>2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp:
>SendRequestToServerForFileInformation failed with 0x80072efd
>2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
>failed with 0x80072efd
>2007-01-11 12:10:09 1116 46c Misc WARNING: Send failed with hr = 80072efd.
>2007-01-11 12:10:09 1116 46c Misc WARNING: SendRequest failed with hr =
>80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
>used : <>
>2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
>failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error 0x80072efd
>2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp:
>SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
>2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp:
>SendRequestToServerForFileInformation failed with 0x80072efd
>2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
>failed with 0x80072efd
>2007-01-11 12:10:11 1116 46c Misc WARNING: Send failed with hr = 80072efd.
>2007-01-11 12:10:11 1116 46c Misc WARNING: SendRequest failed with hr =
>80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
>used : <>
>2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
>failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error 0x80072efd
>2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp:
>SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
>2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp:
>SendRequestToServerForFileInformation failed with 0x80072efd
>2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
>failed with 0x80072efd
>2007-01-11 12:10:14 1116 46c Misc WARNING: Send failed with hr = 80072efd.
>2007-01-11 12:10:14 1116 46c Misc WARNING: SendRequest failed with hr =
>80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes
>used : <>
>2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
>failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error 0x80072efd
>2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp:
>SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
>2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp:
>SendRequestToServerForFileInformation failed with 0x80072efd
>2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
>failed with 0x80072efd
>2007-01-11 12:10:14 1116 46c DnldMgr FATAL:
>DM:CDownloadRegulator::DownloadOdf: WinHttpDownloadFile failed with
>0x80072efd.
>2007-01-11 12:10:14 1116 46c DnldMgr * Last proxy send request failed with
>hr = 0x80072EFD, HTTP status code = 0
>2007-01-11 12:10:14 1116 46c DnldMgr * Caller provided credentials = No
>2007-01-11 12:10:14 1116 46c DnldMgr * Impersonate flags = 0
>2007-01-11 12:10:14 1116 46c DnldMgr * Possible authorization schemes used
>=
>2007-01-11 12:10:14 1116 46c DnldMgr FATAL: DM:CDownloadRegulator::Refresh:
>DownloadOdf failed with 0x80072efd.
>2007-01-11 12:10:14 1116 46c DnldMgr FATAL:
>DM:CAgentDownloadManager::ProcessWorkItem: Refresh failed with 0x80072efd.
>2007-01-11 12:10:27 1116 bd0 DnldMgr Error 0x80072efd occurred while
>downloading update; notifying dependent calls.
>
>
>
>Well, I hope someone can help me. Many thanksss.
>
>
>Neil Chou, Sinotech Engineering Consultants, Ltd.
>Email: neil.chou@msa.hinet.net ; chous@sinotech.com.tw
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

Dave, Thanks for your reply.
Well, I found that my problem might be related to some api.dll overwritten
while starting IIS. I remember when prompted to insert windows 2003 CD duing
configuring IIS, I put in a CD without sp1. Later I were prompted again to
insert windows 2003 CD, then I found my CD with sp1. This might be the
problem causing WSUS malfunction.
So, what next, should I reinstall Windows 2003 SP1. Somebody said it
worked. any suggestions?
"Dave Mills" <News1@nospam--djmills-dot-co.uk>
vpeeq2h0raqsrvh47viol95ofejf95ls6v@4ax.com...
> 0x80072efd - ERROR INTERNET CANNOT CONNECT
>
> 0x80072efe - ERROR INTERNET CONNECTION ABORTED
>
> Quoting from one of Lawrence Garvin's replies last April.
> ===================================
> In essence this is a infrastructure problem. The WUA records the '2efd'
> error when it gets /NO/ response from a webserver at the designated URL.
> This can actually happen for a number of reasons, but the bottom line is
> that there is not a functioning webserver available at the specified URL.
>
> (a) The web server may exist and be stopped; or the WWW service is not
> running.
>
> (b) The port number may be incorrect. (Are you positive the WSUS server is
> installed on the alternate port?)
>
> (c) The IP Address may be incorrect.
>
> (d) A router, firewall, or proxy server may be blocking access. (Do you
> have
> any of these devices between the client and WSUS server? If so, does the
> device have the necessary access rule in place? NOTE: Normally, this type
> of
> error will return a '403' from the proxy server, but that's not
> guaranteed,
> as it's dependent on the proxy server configuration.)
>
> (e) DNS would be an issue only if you were using a hostname-based URL.
> You're not, so DNS is irrelevant, but a defective DNS resolver /can/
> produce
> a '2efd' error if using a hostname-based URL.
>
> Best testing methodology is to determine if this error is replicatable on
> /all/ clients, or only selected clients. If /all/ clients, look to the
> server for the cause; if only selected clients, look to the common
> infrastructure elements of those clients that do /not/ exist on the
> working
> clients. (e.g. item (d) and (e) above)
> ===================
>
>
>
>
> On Fri, 12 Jan 2007 14:03:08 +0800, "Neil Chou" <chous@sinotech.com.tw>
> wrote:
>
>>Hi there:
>>Here's the story.
>>We got a new IBM X226 server running Windows 2003 /w sp1. After joining
>>it
>>to our domain, we promoted it to DC. Then we configure IIS 6.0 and
>>install
>>WSUS 2.0 sp1 to use port 80 for windows update. We did the WSUS
>>installation twice because the first time we cnofigure it to be a replica
>>and then we decided to make it a downstream WSUS server.
>>There was an error message shown on the to do list in WSUS console saying
>>that there are problems with selfupdate but we managed to solved it by
>>changing some settings in IIS. Now, here is the problem! All client PCs
>>can be found since we use GPO to set up their WSUS server to be this one.
>>Yet all PCs' show same status - "not yet reported". More clue can be
>>found
>>from windowsupdate.log. It looks like:
>>2007-01-11 11:23:52 1116 718 AU #############
>>2007-01-11 11:23:52 1116 718 AU ## START ## AU: Search for updates
>>2007-01-11 11:23:52 1116 718 AU #########
>>2007-01-11 11:23:52 1116 718 AU <<## SUBMITTED ## AU: Search for updates
>>[CallId = {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
>>2007-01-11 11:23:52 1116 5a8 Agent *************
>>2007-01-11 11:23:52 1116 5a8 Agent ** START ** Agent: Finding updates
>>[CallerId = AutomaticUpdates]
>>2007-01-11 11:23:52 1116 5a8 Agent *********
>>2007-01-11 11:23:52 1116 5a8 Setup *********** Setup: Checking whether
>>self-update is required ***********
>>2007-01-11 11:23:52 1116 5a8 Setup * Inf file:
>>C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version
>>=
>>5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
>>version = 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required
>>version
>>= 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
>>version = 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
>>version = 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
>>version = 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
>>version = 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
>>version = 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
>>version = 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required
>>version
>>= 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required
>>version
>>= 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup Update NOT required for
>>C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required
>>version
>>= 5.8.0.2607
>>2007-01-11 11:23:52 1116 5a8 Setup * IsUpdateRequired = No
>>2007-01-11 11:23:55 1116 5a8 PT +++++++++++ PT: Synchronizing server
>>updates +++++++++++
>>2007-01-11 11:23:55 1116 5a8 PT + ServiceId =
>>{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
>>http://s64101101/ClientWebService/client.asmx
>>2007-01-11 11:23:55 1116 5a8 PT Initializing simple targeting cookie,
>>clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
>>name = c64101010.d161
>>2007-01-11 11:23:55 1116 5a8 PT Server URL =
>>http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
>>2007-01-11 11:23:55 1116 5a8 Misc WARNING: Send failed with hr = 80072efe.
>>2007-01-11 11:23:55 1116 5a8 Misc WARNING: SendRequest failed with hr =
>>80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth
>>Schemes
>>used : <>
>>2007-01-11 11:23:55 1116 5a8 PT + Last proxy send request failed with hr
>>=
>>0x80072EFE, HTTP status code = 0
>>2007-01-11 11:23:55 1116 5a8 PT + Caller provided credentials = No
>>2007-01-11 11:23:55 1116 5a8 PT + Impersonate flags = 0
>>2007-01-11 11:23:55 1116 5a8 PT + Possible authorization schemes used =
>>2007-01-11 11:23:55 1116 5a8 PT WARNING: GetAuthorizationCookie failure,
>>error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP
>>status
>>code = 200
>>2007-01-11 11:23:55 1116 5a8 PT WARNING: Sync of Updates: 0x80072efe
>>2007-01-11 11:23:55 1116 5a8 Agent * WARNING: Failed to synchronize,
>>error
>>= 0x80072EFE
>>2007-01-11 11:23:55 1116 5a8 Agent * WARNING: Exit code = 0x80072EFE
>>2007-01-11 11:23:55 1116 5a8 Agent *********
>>2007-01-11 11:23:55 1116 5a8 Agent ** END ** Agent: Finding updates
>>[CallerId = AutomaticUpdates]
>>2007-01-11 11:23:55 1116 5a8 Agent *************
>>2007-01-11 11:23:55 1116 5a8 Agent WARNING: WU client failed Searching for
>>update with error 0x80072efe
>>2007-01-11 11:23:55 1116 5a8 AU >>## RESUMED ## AU: Search for updates
>>[CallId = {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
>>2007-01-11 11:23:55 1116 5a8 AU # WARNING: Search callback failed,
>>result
>>= 0x80072EFE
>>2007-01-11 11:23:55 1116 5a8 AU #########
>>2007-01-11 11:23:55 1116 5a8 AU ## END ## AU: Search for updates
>>[CallId
>>= {0F64790B-FBFC-4345-88E3-0F404217A3E7}]
>>2007-01-11 11:23:55 1116 5a8 AU #############
>>2007-01-11 11:23:55 1116 5a8 AU AU setting next detection timeout to
>>2007-01-11 07:09:45
>>2007-01-11 11:24:00 1116 46c Report REPORT EVENT:
>>{4B3DBFFC-43D7-4671-AEE8-78D66EF9068D} 2007-01-11 11:23:55+0800 1 148 101
>>{00000000-0000-0000-0000-000000000000} 0 80072efe AutomaticUpdates Failure
>>Software Synchronization Error: Agent failed detecting with reason:
>>0x80072efe
>>2007-01-11 11:30:50 1116 578 DnldMgr Error 0x80072efd occurred while
>>downloading update; notifying dependent calls.
>>2007-01-11 11:37:01 1116 5a8 PT Initializing simple targeting cookie,
>>clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
>>name = c64101010.d161
>>2007-01-11 11:37:01 1116 5a8 PT Server URL =
>>http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
>>2007-01-11 11:37:03 1116 5a8 Misc WARNING: Send failed with hr = 80072efe.
>>2007-01-11 11:37:03 1116 5a8 Misc WARNING: SendRequest failed with hr =
>>80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth
>>Schemes
>>used : <>
>>2007-01-11 11:37:03 1116 5a8 PT + Last proxy send request failed with hr
>>=
>>0x80072EFE, HTTP status code = 0
>>2007-01-11 11:37:03 1116 5a8 PT + Caller provided credentials = No
>>2007-01-11 11:37:03 1116 5a8 PT + Impersonate flags = 0
>>2007-01-11 11:37:03 1116 5a8 PT + Possible authorization schemes used =
>>2007-01-11 11:37:03 1116 5a8 PT WARNING: GetAuthorizationCookie failure,
>>error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP
>>status
>>code = 200
>>2007-01-11 11:37:03 1116 5a8 Report WARNING: Reporter failed to upload
>>events with hr = 80072efe.
>>2007-01-11 11:50:59 1116 87c DnldMgr Error 0x80072efd occurred while
>>downloading update; notifying dependent calls.
>>2007-01-11 12:00:09 1116 718 AU Forced install timer expired for scheduled
>>install
>>2007-01-11 12:06:29 1116 53c PT Initializing simple targeting cookie,
>>clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
>>name = c64101010.d161
>>2007-01-11 12:06:29 1116 53c PT Server URL =
>>http://s64101101/SimpleAuthWebService/SimpleAuth.asmx
>>2007-01-11 12:06:29 1116 53c Misc WARNING: Send failed with hr = 80072efe.
>>2007-01-11 12:06:29 1116 53c Misc WARNING: SendRequest failed with hr =
>>80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth
>>Schemes
>>used : <>
>>2007-01-11 12:06:29 1116 53c PT + Last proxy send request failed with hr
>>=
>>0x80072EFE, HTTP status code = 0
>>2007-01-11 12:06:29 1116 53c PT + Caller provided credentials = No
>>2007-01-11 12:06:29 1116 53c PT + Impersonate flags = 0
>>2007-01-11 12:06:29 1116 53c PT + Possible authorization schemes used =
>>2007-01-11 12:06:29 1116 53c PT WARNING: GetAuthorizationCookie failure,
>>error = 0x80072EFE, soap client error = 5, soap error code = 0, HTTP
>>status
>>code = 200
>>2007-01-11 12:06:29 1116 53c Report WARNING: Reporter failed to upload
>>events with hr = 80072efe.
>>2007-01-11 12:10:03 1116 46c DnldMgr *********** DnldMgr: Downloading
>>regulation Odf ***********
>>2007-01-11 12:10:03 1116 46c DnldMgr * ServiceId =
>>{9482F4B4-E343-43B6-B170-9A65BC822C77}
>>2007-01-11 12:10:03 1116 46c DnldMgr * URL =
>>http://rs.update.microsoft.com/odf/v6odf.xml
>>2007-01-11 12:10:07 1116 46c Misc WARNING: Send failed with hr = 80072efd.
>>2007-01-11 12:10:07 1116 46c Misc WARNING: SendRequest failed with hr =
>>80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth
>>Schemes
>>used : <>
>>2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
>>failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error
>>0x80072efd
>>2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp:
>>SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
>>2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp:
>>SendRequestToServerForFileInformation failed with 0x80072efd
>>2007-01-11 12:10:07 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
>>failed with 0x80072efd
>>2007-01-11 12:10:09 1116 46c Misc WARNING: Send failed with hr = 80072efd.
>>2007-01-11 12:10:09 1116 46c Misc WARNING: SendRequest failed with hr =
>>80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth
>>Schemes
>>used : <>
>>2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
>>failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error
>>0x80072efd
>>2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp:
>>SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
>>2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp:
>>SendRequestToServerForFileInformation failed with 0x80072efd
>>2007-01-11 12:10:09 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
>>failed with 0x80072efd
>>2007-01-11 12:10:11 1116 46c Misc WARNING: Send failed with hr = 80072efd.
>>2007-01-11 12:10:11 1116 46c Misc WARNING: SendRequest failed with hr =
>>80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth
>>Schemes
>>used : <>
>>2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
>>failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error
>>0x80072efd
>>2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp:
>>SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
>>2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp:
>>SendRequestToServerForFileInformation failed with 0x80072efd
>>2007-01-11 12:10:11 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
>>failed with 0x80072efd
>>2007-01-11 12:10:14 1116 46c Misc WARNING: Send failed with hr = 80072efd.
>>2007-01-11 12:10:14 1116 46c Misc WARNING: SendRequest failed with hr =
>>80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth
>>Schemes
>>used : <>
>>2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp: SendRequestUsingProxy
>>failed for <http://rs.update.microsoft.com/odf/v6odf.xml>. error
>>0x80072efd
>>2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp:
>>SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
>>2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp:
>>SendRequestToServerForFileInformation failed with 0x80072efd
>>2007-01-11 12:10:14 1116 46c Misc WARNING: WinHttp: ShouldFileBeDownloaded
>>failed with 0x80072efd
>>2007-01-11 12:10:14 1116 46c DnldMgr FATAL:
>>DM:CDownloadRegulator::DownloadOdf: WinHttpDownloadFile failed with
>>0x80072efd.
>>2007-01-11 12:10:14 1116 46c DnldMgr * Last proxy send request failed
>>with
>>hr = 0x80072EFD, HTTP status code = 0
>>2007-01-11 12:10:14 1116 46c DnldMgr * Caller provided credentials = No
>>2007-01-11 12:10:14 1116 46c DnldMgr * Impersonate flags = 0
>>2007-01-11 12:10:14 1116 46c DnldMgr * Possible authorization schemes
>>used
>>=
>>2007-01-11 12:10:14 1116 46c DnldMgr FATAL:
>>DM:CDownloadRegulator::Refresh:
>>DownloadOdf failed with 0x80072efd.
>>2007-01-11 12:10:14 1116 46c DnldMgr FATAL:
>>DM:CAgentDownloadManager::ProcessWorkItem: Refresh failed with 0x80072efd.
>>2007-01-11 12:10:27 1116 bd0 DnldMgr Error 0x80072efd occurred while
>>downloading update; notifying dependent calls.
>>
>>
>>
>>Well, I hope someone can help me. Many thanksss.
>>
>>
>>Neil Chou, Sinotech Engineering Consultants, Ltd.
>>Email: neil.chou@msa.hinet.net ; chous@sinotech.com.tw
> --
> Dave Mills
> There are 10 type of people, those that understand binary and those that
> don't.

"Neil Chou" <chous@sinotech.com.tw> wrote in message
news:uuhp1oqNHHA.4916@TK2MSFTNGP06.phx.gbl...

> Well, I found that my problem might be related to some api.dll overwritten
> while starting IIS. I remember when prompted to insert windows 2003 CD
> duing configuring IIS, I put in a CD without sp1. Later I were prompted
> again to insert windows 2003 CD, then I found my CD with sp1. This might
> be the problem causing WSUS malfunction.

Yes.. mismatched DLLs could cause the problem, but generally the installer
reads a file in the root of the installation media that identifes the SP
level of the media, and if it's incorrect, it won't use the media.

> So, what next, should I reinstall Windows 2003 SP1. Somebody said it
> worked. any suggestions?

I'd say that's a bit radical. If you believe there may be an issue with
using the wrong media during IIS installation, then I'd suggest uninstalling
WSUS (keep the database, logs, and content), and uninstalling IIS. Reinstall
IIS; Reinstall WSUS. The whole process will take about 30 minutes. Then try
again.

One other thing I'm curious about, Neil....

2007-01-11 11:23:55 1116 5a8 PT Initializing simple targeting cookie,
clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
name = c64101010.d161

The DNS name of the client 'c64101010.d161' is not the typical structure
that's seen in a MACHINE name. Your active directory domain should be of the
form domainname.suffix, and machine names would be of the form
machinename.domainname.suffix.

If you're doing something nonstandard in DNS or domain naming, this could be
contributing to issues you have with network functionality.

--
Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....

Hi, Lawrence:
As for the DNS form, you are right, we use the single word (that is d161) as
the domain name and also the DNS domain. This is true because it was a NT
4.0 domain and we promoted it to Windows 2000 domain without changing any
naming scheme. Therefore DNS name is ok.
I also did a test. I set up a Window 2003 sp1 server and activiated its
IIS. When prompted to insert CD, I gave it a Win2003 without sp1 CD. Then
later I was prompted again, this time I put in the Win2003 with SP1. Later
I install WSUS 2.0 sp1. --- This is the same procedure I did. The only
difference is that this time I am not working on a DC.
Surprisingly, the WSUS runs well, wthout mentioning IIS.
Well, I guess I will try to reinstall Windows 2003 sp1 first. If this
failed to fix WSUS, I will UNINTALL IIS and reinstall IIS.
Thanks for your advice.
Neil


"Lawrence Garvin (MVP)" <onsitech@community.nospam>
eV$R9I2NHHA.4172@TK2MSFTNGP04.phx.gbl...
> "Neil Chou" <chous@sinotech.com.tw> wrote in message
> news:uuhp1oqNHHA.4916@TK2MSFTNGP06.phx.gbl...
>
>> Well, I found that my problem might be related to some api.dll
>> overwritten while starting IIS. I remember when prompted to insert
>> windows 2003 CD duing configuring IIS, I put in a CD without sp1. Later
>> I were prompted again to insert windows 2003 CD, then I found my CD with
>> sp1. This might be the problem causing WSUS malfunction.
>
> Yes.. mismatched DLLs could cause the problem, but generally the installer
> reads a file in the root of the installation media that identifes the SP
> level of the media, and if it's incorrect, it won't use the media.
>
>> So, what next, should I reinstall Windows 2003 SP1. Somebody said it
>> worked. any suggestions?
>
> I'd say that's a bit radical. If you believe there may be an issue with
> using the wrong media during IIS installation, then I'd suggest
> uninstalling WSUS (keep the database, logs, and content), and uninstalling
> IIS. Reinstall IIS; Reinstall WSUS. The whole process will take about 30
> minutes. Then try again.
>
> One other thing I'm curious about, Neil....
>
> 2007-01-11 11:23:55 1116 5a8 PT Initializing simple targeting cookie,
> clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
> name = c64101010.d161
>
> The DNS name of the client 'c64101010.d161' is not the typical structure
> that's seen in a MACHINE name. Your active directory domain should be of
> the form domainname.suffix, and machine names would be of the form
> machinename.domainname.suffix.
>
> If you're doing something nonstandard in DNS or domain naming, this could
> be contributing to issues you have with network functionality.
>
> --
> Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, everything else is at
> http://wsusinfo.onsitechsolutions.com
> ....
>

Again I'm not a pro, but I don't think you can run WSUS on a DC. Someone
feel free to chime in if this is not the case.


"Neil Chou" <chous@sinotech.com.tw> wrote in message
news:edBaVu4NHHA.5104@TK2MSFTNGP06.phx.gbl...
> Hi, Lawrence:
> As for the DNS form, you are right, we use the single word (that is d161)
> as the domain name and also the DNS domain. This is true because it was
> a NT 4.0 domain and we promoted it to Windows 2000 domain without changing
> any naming scheme. Therefore DNS name is ok.
> I also did a test. I set up a Window 2003 sp1 server and activiated its
> IIS. When prompted to insert CD, I gave it a Win2003 without sp1 CD.
> Then later I was prompted again, this time I put in the Win2003 with SP1.
> Later I install WSUS 2.0 sp1. --- This is the same procedure I did. The
> only difference is that this time I am not working on a DC.
> Surprisingly, the WSUS runs well, wthout mentioning IIS.
> Well, I guess I will try to reinstall Windows 2003 sp1 first. If this
> failed to fix WSUS, I will UNINTALL IIS and reinstall IIS.
> Thanks for your advice.
> Neil
>
>
> "Lawrence Garvin (MVP)" <onsitech@community.nospam>
> eV$R9I2NHHA.4172@TK2MSFTNGP04.phx.gbl...
>> "Neil Chou" <chous@sinotech.com.tw> wrote in message
>> news:uuhp1oqNHHA.4916@TK2MSFTNGP06.phx.gbl...
>>
>>> Well, I found that my problem might be related to some api.dll
>>> overwritten while starting IIS. I remember when prompted to insert
>>> windows 2003 CD duing configuring IIS, I put in a CD without sp1. Later
>>> I were prompted again to insert windows 2003 CD, then I found my CD with
>>> sp1. This might be the problem causing WSUS malfunction.
>>
>> Yes.. mismatched DLLs could cause the problem, but generally the
>> installer reads a file in the root of the installation media that
>> identifes the SP level of the media, and if it's incorrect, it won't use
>> the media.
>>
>>> So, what next, should I reinstall Windows 2003 SP1. Somebody said it
>>> worked. any suggestions?
>>
>> I'd say that's a bit radical. If you believe there may be an issue with
>> using the wrong media during IIS installation, then I'd suggest
>> uninstalling WSUS (keep the database, logs, and content), and
>> uninstalling IIS. Reinstall IIS; Reinstall WSUS. The whole process will
>> take about 30 minutes. Then try again.
>>
>> One other thing I'm curious about, Neil....
>>
>> 2007-01-11 11:23:55 1116 5a8 PT Initializing simple targeting cookie,
>> clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
>> name = c64101010.d161
>>
>> The DNS name of the client 'c64101010.d161' is not the typical structure
>> that's seen in a MACHINE name. Your active directory domain should be of
>> the form domainname.suffix, and machine names would be of the form
>> machinename.domainname.suffix.
>>
>> If you're doing something nonstandard in DNS or domain naming, this could
>> be contributing to issues you have with network functionality.
>>
>> --
>> Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
>> Everything you need for WSUS is at
>> http://technet2.microsoft.com/window...s/default.mspx
>> And, everything else is at
>> http://wsusinfo.onsitechsolutions.com
>> ....
>>
>
>

On Wed, 17 Jan 2007 13:58:06 -0500, "SLongxyzzy" <slr64<at>earthlink<dot>net>
wrote:

>Again I'm not a pro, but I don't think you can run WSUS on a DC. Someone
>feel free to chime in if this is not the case.
>
You certainly can. You just cannot run dcpromo after IIS is installed without
breaking IIS. Hence WSUS will break too.

>
>"Neil Chou" <chous@sinotech.com.tw> wrote in message
>news:edBaVu4NHHA.5104@TK2MSFTNGP06.phx.gbl...
>> Hi, Lawrence:
>> As for the DNS form, you are right, we use the single word (that is d161)
>> as the domain name and also the DNS domain. This is true because it was
>> a NT 4.0 domain and we promoted it to Windows 2000 domain without changing
>> any naming scheme. Therefore DNS name is ok.
>> I also did a test. I set up a Window 2003 sp1 server and activiated its
>> IIS. When prompted to insert CD, I gave it a Win2003 without sp1 CD.
>> Then later I was prompted again, this time I put in the Win2003 with SP1.
>> Later I install WSUS 2.0 sp1. --- This is the same procedure I did. The
>> only difference is that this time I am not working on a DC.
>> Surprisingly, the WSUS runs well, wthout mentioning IIS.
>> Well, I guess I will try to reinstall Windows 2003 sp1 first. If this
>> failed to fix WSUS, I will UNINTALL IIS and reinstall IIS.
>> Thanks for your advice.
>> Neil
>>
>>
>> "Lawrence Garvin (MVP)" <onsitech@community.nospam>
>> eV$R9I2NHHA.4172@TK2MSFTNGP04.phx.gbl...
>>> "Neil Chou" <chous@sinotech.com.tw> wrote in message
>>> news:uuhp1oqNHHA.4916@TK2MSFTNGP06.phx.gbl...
>>>
>>>> Well, I found that my problem might be related to some api.dll
>>>> overwritten while starting IIS. I remember when prompted to insert
>>>> windows 2003 CD duing configuring IIS, I put in a CD without sp1. Later
>>>> I were prompted again to insert windows 2003 CD, then I found my CD with
>>>> sp1. This might be the problem causing WSUS malfunction.
>>>
>>> Yes.. mismatched DLLs could cause the problem, but generally the
>>> installer reads a file in the root of the installation media that
>>> identifes the SP level of the media, and if it's incorrect, it won't use
>>> the media.
>>>
>>>> So, what next, should I reinstall Windows 2003 SP1. Somebody said it
>>>> worked. any suggestions?
>>>
>>> I'd say that's a bit radical. If you believe there may be an issue with
>>> using the wrong media during IIS installation, then I'd suggest
>>> uninstalling WSUS (keep the database, logs, and content), and
>>> uninstalling IIS. Reinstall IIS; Reinstall WSUS. The whole process will
>>> take about 30 minutes. Then try again.
>>>
>>> One other thing I'm curious about, Neil....
>>>
>>> 2007-01-11 11:23:55 1116 5a8 PT Initializing simple targeting cookie,
>>> clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161, DNS
>>> name = c64101010.d161
>>>
>>> The DNS name of the client 'c64101010.d161' is not the typical structure
>>> that's seen in a MACHINE name. Your active directory domain should be of
>>> the form domainname.suffix, and machine names would be of the form
>>> machinename.domainname.suffix.
>>>
>>> If you're doing something nonstandard in DNS or domain naming, this could
>>> be contributing to issues you have with network functionality.
>>>
>>> --
>>> Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
>>> Everything you need for WSUS is at
>>> http://technet2.microsoft.com/window...s/default.mspx
>>> And, everything else is at
>>> http://wsusinfo.onsitechsolutions.com
>>> ....
>>>
>>
>>
>
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

So I am back with smile.
I am tired of fixing WSUS so I decided to begin a fresh start.
I un-installed WSUS, IIS, .Net framework 1.1, stopped MSDE and deleted
related database. Then I Reinstall .Net framework 1.1, IIS, and finally,
WSUS.
This machine runs well now. So DC is not a problem. I guess my problem is
related to some security issue about local or global account when promoting
to domain controller.
Thank you all for the replies.
Neil


=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
"Dave Mills" <News1@nospam--djmills-dot-co.uk>
:hl8tq2t1g515r781qoufqhoeff8coomrmh@4ax.com...
> On Wed, 17 Jan 2007 13:58:06 -0500, "SLongxyzzy"
> <slr64<at>earthlink<dot>net>
> wrote:
>
>>Again I'm not a pro, but I don't think you can run WSUS on a DC. Someone
>>feel free to chime in if this is not the case.
>>
> You certainly can. You just cannot run dcpromo after IIS is installed
> without
> breaking IIS. Hence WSUS will break too.
>
>>
>>"Neil Chou" <chous@sinotech.com.tw> wrote in message
>>news:edBaVu4NHHA.5104@TK2MSFTNGP06.phx.gbl...
>>> Hi, Lawrence:
>>> As for the DNS form, you are right, we use the single word (that is
>>> d161)
>>> as the domain name and also the DNS domain. This is true because it
>>> was
>>> a NT 4.0 domain and we promoted it to Windows 2000 domain without
>>> changing
>>> any naming scheme. Therefore DNS name is ok.
>>> I also did a test. I set up a Window 2003 sp1 server and activiated its
>>> IIS. When prompted to insert CD, I gave it a Win2003 without sp1 CD.
>>> Then later I was prompted again, this time I put in the Win2003 with
>>> SP1.
>>> Later I install WSUS 2.0 sp1. --- This is the same procedure I did. The
>>> only difference is that this time I am not working on a DC.
>>> Surprisingly, the WSUS runs well, wthout mentioning IIS.
>>> Well, I guess I will try to reinstall Windows 2003 sp1 first. If this
>>> failed to fix WSUS, I will UNINTALL IIS and reinstall IIS.
>>> Thanks for your advice.
>>> Neil
>>>
>>>
>>> "Lawrence Garvin (MVP)" <onsitech@community.nospam>
>>> eV$R9I2NHHA.4172@TK2MSFTNGP04.phx.gbl...
>>>> "Neil Chou" <chous@sinotech.com.tw> wrote in message
>>>> news:uuhp1oqNHHA.4916@TK2MSFTNGP06.phx.gbl...
>>>>
>>>>> Well, I found that my problem might be related to some api.dll
>>>>> overwritten while starting IIS. I remember when prompted to insert
>>>>> windows 2003 CD duing configuring IIS, I put in a CD without sp1.
>>>>> Later
>>>>> I were prompted again to insert windows 2003 CD, then I found my CD
>>>>> with
>>>>> sp1. This might be the problem causing WSUS malfunction.
>>>>
>>>> Yes.. mismatched DLLs could cause the problem, but generally the
>>>> installer reads a file in the root of the installation media that
>>>> identifes the SP level of the media, and if it's incorrect, it won't
>>>> use
>>>> the media.
>>>>
>>>>> So, what next, should I reinstall Windows 2003 SP1. Somebody said it
>>>>> worked. any suggestions?
>>>>
>>>> I'd say that's a bit radical. If you believe there may be an issue with
>>>> using the wrong media during IIS installation, then I'd suggest
>>>> uninstalling WSUS (keep the database, logs, and content), and
>>>> uninstalling IIS. Reinstall IIS; Reinstall WSUS. The whole process will
>>>> take about 30 minutes. Then try again.
>>>>
>>>> One other thing I'm curious about, Neil....
>>>>
>>>> 2007-01-11 11:23:55 1116 5a8 PT Initializing simple targeting cookie,
>>>> clientId = 6e70c183-48b3-430c-8516-501ce5bd5370, target group = d161,
>>>> DNS
>>>> name = c64101010.d161
>>>>
>>>> The DNS name of the client 'c64101010.d161' is not the typical
>>>> structure
>>>> that's seen in a MACHINE name. Your active directory domain should be
>>>> of
>>>> the form domainname.suffix, and machine names would be of the form
>>>> machinename.domainname.suffix.
>>>>
>>>> If you're doing something nonstandard in DNS or domain naming, this
>>>> could
>>>> be contributing to issues you have with network functionality.
>>>>
>>>> --
>>>> Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
>>>> Everything you need for WSUS is at
>>>> http://technet2.microsoft.com/window...s/default.mspx
>>>> And, everything else is at
>>>> http://wsusinfo.onsitechsolutions.com
>>>> ....
>>>>
>>>
>>>
>>
> --
> Dave Mills
> There are 10 type of people, those that understand binary and those that
> don't.

"Neil Chou" <chous@sinotech.com.tw> wrote in message
news:uavicyqOHHA.4724@TK2MSFTNGP02.phx.gbl...

> This machine runs well now. So DC is not a problem. I guess my problem
> is related to some security issue about local or global account when
> promoting to domain controller.

If you ran dcpromo /after/ installing IIS, then you've been fighting with a
well documented issue, discussed here at least monthly, and sometimes more
frequently.

> it was
> a NT 4.0 domain and we promoted it to Windows 2000 domain without changing
> any naming scheme.

This probably has something to do with it also, depending on what order you
performed the various steps in this process.

Glad you found a solution.



--
Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....