Solution: Error 0x80190194 / 0x80244019 while downloading updates

I'm sure this is old news to some folks out there, but I had a devil of
a time solving this. So this is just a quick note to (hopefully) save
someone a little time should they ever encounter this problem...

I am running WSUS on a Windows 2003 Server system, and I came across a
problem where certain updates would fail to download onto the client
machines every single time. When I looked at the
"%windir%\WindowsUpdate.log" file on the client machines, I noticed that
the updates were failing with an error something like this:

DnldMgr WARNING: BITS job {F65EC03C-34DC-4CFC-BDFD-EA8DF7A1FBB2}
failed, updateId = {9829AC5C-CF1D-4706-A3C3-8DC63A1F5924}.100, hr =
0x80190194, BG_ERROR_CONTEXT = 5

DnldMgr Progress failure bytes total = 299579, bytes transferred = 0

DnldMgr Failed job file: URL =
http://updates/Content/B6/A2E8C22844...C8400811B6.psf,
local path =
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\dbdf54c109f1fd214852e996a6632102\download\WindowsXP-KB908521-x86-ENU.psf.blob

DnldMgr Error 0x80244019 occurred while downloading update;
notifying dependent calls.



Looking at the WSUS error code reference at
http://members.chello.nl/pvawisse/wi...date_codes.htm, I determined
that both the 0x80190194 and 0x80244019 error codes are the same as HTTP
status 404 - "The server cannot find the requested URI (Uniform Resource
Identifier)." And when I entered the URL directly into Internet
Explorer, sure enough it returned a 404 Not Found error.

Yet when I looked in the appropriate folders under "C:\WSUS\WsusContent"
on my server, I could see that the files most definitely were there.
But when I thought about it, I realized that I had never seen a ".psf"
file before, and that's when I remembered a "gotcha" I encountered a
while back: Microsoft KB Article #326965, "IIS 6.0 Does Not Serve
Unknown MIME Types"
(http://support.microsoft.com/default...;en-us;326965).

So I fired up the IIS Manager and checked the registered MIME types, and
sure enough - the ".psf" type was missing! A quick search on the
Internet revealed the following list of types that are required for WSUS
to work properly:

.cab - application/octet-stream
.msp - application/octet-stream
.msi - application/octet-stream
.psf - application/octet-stream


After adding the missing types, I confirmed that I am now able to
download all of the updates with no problems. Yay!

I hope this helps someone out there!

Thanks for the reminder about MIME types, Nathan.

The WSUS install /should/ have registered those MIME types if they were not
already registered.

This is good information to know - you mention 'a quick search revealed MIME
types required for WSUS'. I have not been able to find this information.
Would you point me to the url location of where this is documented?

Good question Dave. I have .psf registered on my workstation as
'AutoCAD LT PostScript Patterns'. I do have AutoCAD installed. The .psf
in not a registered file typ on my WSUS server as seen by Windows
Explorer.

On Mon, 20 Feb 2006 23:25:48 -0600, "Lawrence Garvin \(MVP\)"
<onsitech@news.postalias> wrote:

>And even if they're not registered, the registration is for the benefit of
>the /browser/.
>
>From the standpoint of the WUA, it sends a request to BITS to GET a
>specified file. BITS issues a GET request for the file, and all of those
>requests should simply involve a file transfer. The purpose of MIME types is
>to identify applications or applets that "run" a file when it is downloaded.
>In the case of WUA/BITS, the file is merely downloaded and written to the
>filesystem. There's nothing to "run".
>
>btw... the .psf file is part of the Express Installation Files bundle.

Thanks Lawrence. That explains why I have not seen any recently

--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.