[solved] Download failure for dotnet x86-glb

[IslandBoy77]

Hi

For the last 3 days Wsus is broken. See the log below:

Code: Select all

Thu 16/08/2012 19:26:50.12 - Info: Starting WSUS Offline Update download (v. 7.4.2) for w60 glb
Thu 16/08/2012 19:26:50.12 - Info: Option /includedotnet detected
Thu 16/08/2012 19:26:50.14 - Info: Option /nocleanup detected
Thu 16/08/2012 19:26:50.16 - Info: Option /verify detected
Thu 16/08/2012 19:26:50.16 - Info: Option /exitonerror detected
Thu 16/08/2012 19:26:50.17 - Info: Option /skipiso detected
Thu 16/08/2012 19:26:50.23 - Info: Set time zone to LOC-12:00
Thu 16/08/2012 19:26:50.25 - Info: Verified integrity of Windows Update Agent installation and catalog files
Thu 16/08/2012 19:26:51.19 - Info: Downloaded/validated most recent Windows Update Agent installation and catalog files
Thu 16/08/2012 19:26:51.19 - Info: Verified digital file signatures of Windows Update Agent installation and catalog files
Thu 16/08/2012 19:26:51.19 - Info: Created integrity database for Windows Update Agent installation and catalog files
Thu 16/08/2012 19:26:52.14 - Info: Verified integrity of .NET Frameworks' installation files
Thu 16/08/2012 19:26:55.57 - Info: Downloaded/validated installation files for .NET Frameworks 3.5 SP1 and 4
Thu 16/08/2012 19:26:55.57 - Info: Verified integrity of existing updates for dotnet x86-glb
Thu 16/08/2012 19:26:58.48 - Info: Determined static update urls for dotnet x86-glb
Thu 16/08/2012 19:26:59.21 - Error: Download failure for dotnet x86-glb

If I take the tick out of Include C++ etc, I get this instead:

Code: Select all

Thu 16/08/2012 19:09:41.80 - Info: Starting WSUS Offline Update download (v. 7.4.2) for w60 glb
Thu 16/08/2012 19:09:41.80 - Info: Option /nocleanup detected
Thu 16/08/2012 19:09:41.82 - Info: Option /verify detected
Thu 16/08/2012 19:09:41.83 - Info: Option /exitonerror detected
Thu 16/08/2012 19:09:41.83 - Info: Option /skipiso detected
Thu 16/08/2012 19:09:41.89 - Info: Set time zone to LOC-12:00
Thu 16/08/2012 19:09:41.92 - Info: Verified integrity of Windows Update Agent installation and catalog files
Thu 16/08/2012 19:09:43.09 - Info: Downloaded/validated most recent Windows Update Agent installation and catalog files
Thu 16/08/2012 19:09:43.09 - Info: Verified digital file signatures of Windows Update Agent installation and catalog files
Thu 16/08/2012 19:09:43.09 - Info: Created integrity database for Windows Update Agent installation and catalog files
Thu 16/08/2012 19:09:45.12 - Info: Verified integrity of existing updates for win glb
Thu 16/08/2012 19:09:47.25 - Info: Determined static update urls for win glb
Thu 16/08/2012 19:09:48.23 - Error: Download failure for win glb

So, Wsus is broken. Please fix it.

Thanks
Peter

[WSUSUpdateAdmin]

Hi!

[...]So, Wsus is broken.

Yes, yours.

Please fix it.

Please delete ...\client\md\hashes*.txt and re-run download.

Regards
Torsten Wittrock

[IslandBoy77]

So you're telling me that after working with no problems for over a year, and having worked fine at the end of last week, Wsus just up and decided to stop working on my PC with no warning or explanation?

I did what you suggested, and it's still broken:

Code: Select all

Sat 18/08/2012  0:08:00.90 - Info: Starting WSUS Offline Update download (v. 7.4.2) for w60 glb
Sat 18/08/2012  0:08:00.90 - Info: Option /includedotnet detected
Sat 18/08/2012  0:08:00.92 - Info: Option /nocleanup detected
Sat 18/08/2012  0:08:00.93 - Info: Option /verify detected
Sat 18/08/2012  0:08:00.93 - Info: Option /exitonerror detected
Sat 18/08/2012  0:08:00.95 - Info: Option /skipiso detected
Sat 18/08/2012  0:08:01.01 - Info: Set time zone to LOC-12:00
Sat 18/08/2012  0:08:01.04 - Warning: Integrity database ..\client\md\hashes-wsus.txt not found
Sat 18/08/2012  0:08:01.77 - Info: Downloaded/validated most recent Windows Update Agent installation and catalog files
Sat 18/08/2012  0:08:01.77 - Info: Verified digital file signatures of Windows Update Agent installation and catalog files
Sat 18/08/2012  0:08:01.77 - Info: Created integrity database for Windows Update Agent installation and catalog files
Sat 18/08/2012  0:08:02.73 - Warning: Integrity database ..\client\md\hashes-dotnet.txt not found
Sat 18/08/2012  0:08:03.97 - Info: Downloaded/validated installation files for .NET Frameworks 3.5 SP1 and 4
Sat 18/08/2012  0:08:03.97 - Warning: Integrity database ..\client\md\hashes-dotnet-x86-glb.txt not found
Sat 18/08/2012  0:08:03.99 - Info: Determined static update urls for dotnet x86-glb
Sat 18/08/2012  0:08:04.57 - Error: Download failure for dotnet x86-glb

[WSUSUpdateAdmin]

So you're telling me that after working with no problems for over a year, and having worked fine at the end of last week,[...]

What I wanted and still want to tell you is, that this is a specific problem on your PC, not a general problem with the software, so we don't need to fix WOU, but your environment.

Wsus just up and decided to stop working on my PC with no warning or explanation?

If you pull the plug, the network will be down without warning, for example.

Please have a look at the download command window before you continue to post parts of the log file.
It will tell you what the problem is, I suppose.

[Denniss]

M$ recently moved some dotnet languange packs around and renamed them - did you manually add some dotnet 1.1/2.0 downloads?

[IslandBoy77]

So you're telling me that after working with no problems for over a year, and having worked fine at the end of last week,[...]

What I wanted and still want to tell you is, that this is a specific problem on your PC, not a general problem with the software, so we don't need to fix WOU, but your environment.

Wsus just up and decided to stop working on my PC with no warning or explanation?

If you pull the plug, the network will be down without warning, for example.

Please have a look at the download command window before you continue to post parts of the log file.
It will tell you what the problem is, I suppose.

I realise that you might think I'm some n00b who has no idea what he's doing. It would be a mistake to think that, given that I fix computers for a living. What you're telling me is this: Due to some "change" to my computer, WSUS (that's been working fine for the last year, despite numerous "changes" to my computer AND WSUS) has, on my computer only, just decided to stop working - AFTER WSUS had 2 changes (from 7.4 to 7.4.1 to 7.4.2) itself around 15/8/12. It's only since the 7.4.1 / 7.4.2 updates that I've problems - the last good update being 9/8/12. The only change of note to my computer were the automatic Microsoft Windows updates that happended on the 19th of August - 4 days AFTER WSUS broke itself. I've switched my AV off and UAC, and there's no block in the Windows firewall (in fact I added an exception just to be sure), and I'm not running any 3rd party firewall products (and haven't for many years).

There's nothing in the logs that tell me anything - other than the fact that WSUS isn't functioning properly like it did 2 weeks ago: it's no use blaming my system when everything else on it works fine and WSUS is the ONLY thing that doesn't. I've posted all the relevant information - why can't you work out from that what the problem is? The only "extra" bit of information from the command line window is "ERROR: Download failure for dotnet x86-glb" If I un-check the "Include C++ Runtime Libraries and .NET Frameworks" option, the fault simply "moves" to the next pack in the sequence (which in my case is win glb). The step that the failure is on appears to be either "Determined static update urls for dotnet x86-glb" or "Determined superseded updates". But whichever it is, you can see from the piece of the log below that it happens in less than a second:

Tue 21/08/2012 15:10:17.06 - Info: Determined static update urls for dotnet x86-glb
Tue 21/08/2012 15:10:17.89 - Error: Download failure for dotnet x86-glb

This is what it normally looks like:

Thu 09/08/2012 15:18:08.50 - Info: Determined static update urls for dotnet x86-glb
Thu 09/08/2012 15:18:48.42 - Info: Determined superseded updates

And no, I didn't manually add any dotnet downloads - since the idea of WSUS is to be streamlined and simple, I have never tinkered with any settings beyond the actual packs / OSes I want to have included in the updates.

[Denniss]

What's the last action/info visible in the cmd window ?
During the download run two files are downloaded from or checked against
http://download.wsusoffline.net/StaticD ... 86-glb.txt
http://download.wsusoffline.net/Exclude ... xclude.txt

->Do you have access to these files?

[IslandBoy77]

What's the last action/info visible in the cmd window ?
During the download run two files are downloaded from or checked against
http://download.wsusoffline.net/StaticD ... 86-glb.txt
http://download.wsusoffline.net/Exclude ... xclude.txt

->Do you have access to these files?

Here's the last entry in the cmd window:

Verifying integrity of existing updates for dotnet x86-glb...
hashdeep.exe: Audit passed
Input files examined: 0
Known files expecting: 0
Files matched: 55
Files partially matched: 0
Files moved: 0
New files found: 0
Known files not found: 0
Determining static update urls for dotnet x86-glb...
Extracting Microsoft's update catalog file package.xml...
11:54:56.03 - Determining superseded updates (please be patient, this will take
a while)...

ERROR: Download failure for dotnet x86-glb.

Press any key to continue . . .

I have both the files you mention and they matched what your files have - except the superceded file was missing kb967723 - which added to mine (before running WSUS again).

What I'm trying to avoid is having to re-download all 13GB of WSUS again - our "broadband" here (actually only ADSL) is quite expensive, so I have to parcel out my monthly 30gb usage carefully.

[boco]

What I'm trying to avoid is having to re-download all 13GB of WSUS again

As long as you keep the ./client directory (or, more precisely, the patch subdirectories therein), you won't lose the repository.

[WSUSUpdateAdmin]

Hi!

Reading your command window output, I had another idea:
Because Microsoft retracted msxsl.exe, which depended on MSXML4, I had to change the XSL transformation implementation and added XSLT.vbs to WOU v. 7.4.1/7.4.2, which depends on MSXML6 or (alternatively) on MSXML3.

So, we should check if MSXML6 or MSXML3 is present on your download system.
In a command window (cmd.exe), could you please run

Code: Select all

dir %SystemRoot%\system32\msxml*


On my Win7, the result is

Code: Select all

 Verzeichnis von C:\Windows\system32

06.06.2012  08:06         1.881.600 msxml3.dll
26.06.2010  05:55             2.048 msxml3r.dll
06.06.2012  08:06         2.004.480 msxml6.dll
14.07.2009  03:30             2.048 msxml6r.dll
               4 Datei(en),      3.890.176 Bytes


What system do you use for downloading (XP/Vista/7/...)?

Regards
Torsten Wittrock