0x80190194 and 80072efd

[chvgms]

Hi,

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.

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/85605E276A7D714B23CCE78FACE8F915F1B7242C.txt
with error 0x80244019

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
2009-09-02 14:24:10:312 816 7fc Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2009-09-02 14:24:10:312 816 7fc Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2009-09-02 14:24:10:312 816 7fc Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80072efd
2009-09-02 14:24:15:750 816 7fc Misc WARNING: Send failed with hr = 80072efd.

Thanks,
Sridhar

[TaurArian]

chvgms wrote:
:: Hi,

Perhaps try the WSUS Newsgroup for their expert advice -

On the web:
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services

In your newsreader:
news://msnews.microsoft.com/microsoft.public.windows.server.update_services
--

TaurArian [MVP] 2005-2010 - Update Services
http://taurarian.mvps.org
======================================
Disclaimer: The information has been posted "as is" with no warranties
or guarantees and doesn't give any rights.

[Eddie Bowers [MSFT]]

I think you have two seperate issues.
The error you are getting from the client to WSUS is a 404 not found error
indicating tha the requested file either isn't present at that location or
your WSUS server is set up for port 8530, but your policy doesn't specify
the port (the selfupdate will exist on both sites)

The error you are getting on the server going to WindowsUpdate is a more
general Connection Failed error.
If you can get to that same path with IE, you might try running
proxycfg -u to import the IE proxy setings into your WinHTTP configuration.

-Eddie