"chvgms" <> wrote in message
news:7CAD5E56-28EE-42F7-BE5A-...
> I am getting the error codes on the WSUS 3.0 SP1 server and client
> (win xp sp3). Though the updates has been approved on the server,
> clients are not downloading and getting failed with the below error
> codes. WSUS is behind proxy (ISA 2006). I am able to browse windows
> update via proxy and also http://wsus01/selfupdate/wuident.cab is
> successful from client.
I need some clarification on what you mean by "WSUS is behind proxy".
Do you mean that the clients need to go through the ISA Server to get to the
WSUS Server? If so, there's a boatload of configuration considerations for
publishing a WSUS Server via ISA Server.
Do you mean that the WSUS Server needs to go through the ISA Server to get
to the Internet. If so, is the *proxy service* required, or are we only
concerned with ISA Server as a firewall?
> Client:
>
> WARNING: WinHttp: SendRequestToServerForFileInformation failed with
> 0x80190194 2009-09-01 21:06:58:771 1088 1410 Misc WARNING: WinHttp:
> ShouldFileBeDownloaded failed with 0x80190194
> 2009-09-01 21:06:58:771 1088 1410 Agent WARNING: Fail to download
> eula file
> http://sydnagents/Content/2C/85605E2...15F1B7242C.txt
> with error 0x80244019
This is an HTTP 404 error trying to download this EULA txt file.
- Verify that the EULA text file physically exists in the
~\WSUS\WSUSContent\2C folder.
- Verify that the ISA Server is not configured to block transfer of TXT
files.
- Verify that the WinHTTP is properly configured to connect to the proxy
server.
Note: In this response "WSUS Server" (with Server capitalized) refers to the
WSUS service itself; "WSUS server" (with server not capitalized) refers to
the WUAgent (client) on the server hosting WSUS.
> :: Server:
> ::
> :: WARNING: SendRequest failed with hr = 80072efd. Proxy List used:
> :: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
> :: 2009-09-02 14:24:10:312 816 7fc Misc WARNING: WinHttp:
> :: SendRequestUsingProxy failed for
> :: <http://update.microsoft.com/v8/windowsupdate/redir/muv3wuredir.cab>.
> :: error 0x80072efd
My first observation is that the WSUS server is not configured to use "WSUS"
to get updates. This is the WUAgent on the WSUS server attempting to make a
connection to Microsoft Update and failing. This is interesting, because the
WSUS Server ought to be able to get to this URL to support WSUS services, so
there's no reason at all that the WUAgent on the WSUS server should be
failing.
Unless, of course, if you've misconfigured the WinHTTP proxy client
configuration on the WSUS Server -- but if this were the case, the WSUS
Server wouldn't be downloading *any* content at all, and the clients
wouldn't even be attempting to download content, as they wouldn't even be
detecting the availability of updates.
The other possibility is that somebody reconfigured the ISA Server and broke
all of this functionalitythat used to be working.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website:
http://www.microsoft.com/wsus
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin
Similar Threads
Linear Mode
