Download failed - 0x80200011

[Quintin Zammit]

Hi,

I have been working with WSUS for the last 8 months and had no problems with
installation of approved updates on the clients but during the last Ms
updates I am experiecing 'Failed' installation of updates on most of the
workstations with the Result code 0x80200011.

When doing wuauclt.exe /detectnow, the workstation will successfully
sycnhronise with WSUS server but the updates are not installed.

Before this problem started occuring, I have segmented the network with ISA
2006 firewalls. All internal traffic between the ISA 2006 firewalls is
allowed for the time being and could not find what could have caused the
updates to fail.

Your feedback will be highly appreciated.

Regards,
Quintin

[Lawrence Garvin (MVP)]

"Quintin Zammit" <qztar...@newsgroup.nospam> wrote in message
news:ukqbDIGb...@TK2MSFTNGP02.phx.gbl...

> Hi,
>
> I have been working with WSUS for the last 8 months and had no problems
> with installation of approved updates on the clients but during the last
> Ms updates I am experiecing 'Failed' installation of updates on most of
> the workstations with the Result code 0x80200011.

0x80200011
BG E MISSING FILE SIZE
When BITS sends a HEAD request and server/proxy doesn't return
Content-Length header in the response, BITS puts the job in ERROR state with
BG E MISSING FILE SIZE. BITS 1.5 puts the job in ERROR state with BG E
INVALID SERVER RESPONSE error. Apache 2.0 proxy server is known to exhibit
this behavior.

The source for the error description above is the list of error codes for
the legacy AU client, so the error message may be a bit out of date
(specifically as concerns the reference to BITS 1.5). This is the first I've
ever seen any 0x8020xxxx error code in use with WSUS.

Applying a bit of 'between the lines' to this scenario, I would suggest:

[a] Ensure that BITS 2.0 is properly installed on these workstations. I
suspect, however, that this error message is also applicable to BITS 2.0
environments.
[b] Ensure that any proxy server between the workstations and the WSUS
server is properly configured to support HTTP v1.1.
[c] Ensure that the =client= is enabled to use HTTP v1.1.

> Before this problem started occuring, I have segmented the network with
> ISA 2006 firewalls. All internal traffic between the ISA 2006 firewalls is
> allowed for the time being and could not find what could have caused the
> updates to fail.

Well.... I'd bet dollars to donuts is a configuration issue with your
ISA2006 internal firewalls.

But.... I've not yet had a chance to work with ISA2006, so I cannot offer
any product-specific guidance at this time concerning configurations of
ISA2006 and WSUS.

The general guidance to ensure that the ISA systems are not blocking HTTP
v1.1 protocols, specifically the use of Content-Length Headers is the key
focus point.

--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
....

[Erik Mattsson]

I got the same error at a customer. Since I did not think the error
message made sense, I set all failing updates to "Detect Only" and then
back to "Install" again. After that they all installed.

Regards ErikM