WS 2003 SP2 updates failed to install

Been having this problem forever it seems. I tried renaming the
windows\system32\catroot2\edb.log file and even the
windows\system32\catroot2\ directory but i am still unable to install
updates. there are no error codes anywhere. however, i think it has
something to do with WU not downloading the entire package. after the
updates have failed to install the first time, WU update reports that there
are 0kb to download and subsequent attempts to install the updates fail until
i search for the related KB article and manually download and install the
update. i have compared the size of the file when i manually download it to
the size initially reported by WU and the manual download is always larger.
maybe there is a clue in the log files for the updates. here is a sample:

[KB896428.log]
2.031:
================================================== =======================
=======
2.031: 2005/06/17 16:49:53.242 (local)
2.047:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\50f1f908ea761d81e0511c7
cbc21c03d\update\update.exe (version 6.1.22.4)
2.047: Hotfix started with following command line: /si
/ParentInfo:792ae71c8c274
c4b8ad47623278d573f
3.547: DoInstallation: CleanPFR failed: 0x2
3.563: SetProductTypes: InfProductBuildType=BuildType.IA
3.563: SetAltOsLoaderPath: No section uses DirId 65701; done.
3.672: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB896428$
3.672: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe00
00102
3.688: ref tag c:\windows\system32\sp4.cab does not exist
3.688: ref tag c:\windows\system32\sp3.cab does not exist
3.688: ref tag c:\windows\system32\sp2.cab does not exist
3.688: ref tag c:\windows\system32\sp1.cab does not exist
3.688: ref tag c:\windows\system32\driver.cab does not exist
3.688: ref tag c:\windows\system32\fp40ext.cab does not exist
3.688: ref tag c:\windows\system32\fp40ext1.cab does not exist
3.688: ref tag c:\windows\system32\wms4.cab does not exist
3.688: ref tag c:\windows\system32\wms41.cab does not exist
3.688: ref tag c:\windows\system32\ims.cab does not exist
3.688: ref tag c:\windows\system32\ims1.cab does not exist
3.688: ref tag c:\windows\system32\ins.cab does not exist
3.688: ref tag c:\windows\system32\ins1.cab does not exist
3.688: Starting AnalyzeComponents
3.688: AnalyzePhaseZero used 0 ticks
3.703: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
3.703: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
7.438:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem6.C
AT trusts inf c:\windows\inf\oem6.inf of device
HID\VID_051D&PID_0002\6&26251CE4
&0&0000
14.000:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem19
..CAT trusts inf c:\windows\inf\oem19.inf of device
PCI\VEN_1102&DEV_7003&SUBSYS_
00401102&REV_04\5&35CDC86&0&31F820
18.578: SetupVerifyInfFile failed with error 0x490 for oem17.inf of device
ROOT\
PROTOWALLMP_FD\0000
18.797: SetupVerifyInfFile failed with error 0x490 for
c:\windows\inf\oem17.inf
of device ROOT\PROTOWALLMP_FD\0000
18.828: SetupVerifyInfFile failed with error 0x490 for oem17.inf of device
ROOT\
PROTOWALLMP_FD\0001
18.984: SetupVerifyInfFile failed with error 0x490 for
c:\windows\inf\oem17.inf
of device ROOT\PROTOWALLMP_FD\0001
19.328: SetupVerifyInfFile failed with error 0x490 for oem3.inf of device
ROOT\S
YSTEM\0002
19.500: SetupVerifyInfFile failed with error 0x490 for
c:\windows\inf\oem3.inf o
f device ROOT\SYSTEM\0002
24.703: OEM file scan used 21000 ticks
24.719: AnalyzePhaseOne: used 21031 ticks
24.719: AnalyzeComponents: Hotpatch analysis disabled; skipping.
24.719: AnalyzeComponents: Hotpatching is disabled.
24.719: FindFirstFile c:\windows\$hf_mig$\*.*
25.563: AnalyzeForBranching used 47 ticks.
25.563: AnalyzePhaseTwo used 0 ticks
25.563: AnalyzePhaseThree used 0 ticks
25.563: AnalyzePhaseFive used 0 ticks
25.563: AnalyzePhaseSix used 0 ticks
25.563: AnalyzeComponents used 21875 ticks
25.563: Downloading 2 files
25.563: bPatchMode = TRUE
25.563: Inventory complete: ReturnStatus=0, 21891 ticks
25.563: Num Ticks for invent : 21891
25.578: [dumpDownloadTask] Update.exe posting request file to download a
total of 6758 bytes (6758 bytes in patches and 0 bytes in fallbacks)
25.578: dumpDownloadTask returned 0xf200 (more files to download)
25.641: KB896428 installation did not complete.
25.641: Update.exe extended error code = 0xf200
0.984:
================================================== =======================
=======

Sorry if this is redundant, but I did try searching for relevant posts
without much luck. If anyone has any suggestions I am open to try anything.
Thank you.

I don't understand what the fix is?

"" wrote:

> Been having this problem forever it seems. I tried renaming the
> windows\system32\catroot2\edb.log file and even the
> windows\system32\catroot2\ directory but i am still unable to install
> updates. there are no error codes anywhere. however, i think it has
> something to do with WU not downloading the entire package. after the
> updates have failed to install the first time, WU update reports that there
> are 0kb to download and subsequent attempts to install the updates fail until
> i search for the related KB article and manually download and install the
> update. i have compared the size of the file when i manually download it to
> the size initially reported by WU and the manual download is always larger.
> maybe there is a clue in the log files for the updates. here is a sample:
>
> [KB896428.log]
> 2.031:
> ================================================== =======================
> =======
> 2.031: 2005/06/17 16:49:53.242 (local)
> 2.047:
> C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\50f1f908ea761d81e0511c7
> cbc21c03d\update\update.exe (version 6.1.22.4)
> 2.047: Hotfix started with following command line: /si
> /ParentInfo:792ae71c8c274
> c4b8ad47623278d573f
> 3.547: DoInstallation: CleanPFR failed: 0x2
> 3.563: SetProductTypes: InfProductBuildType=BuildType.IA
> 3.563: SetAltOsLoaderPath: No section uses DirId 65701; done.
> 3.672: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB896428$
> 3.672: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
> 0xe00
> 00102
> 3.688: ref tag c:\windows\system32\sp4.cab does not exist
> 3.688: ref tag c:\windows\system32\sp3.cab does not exist
> 3.688: ref tag c:\windows\system32\sp2.cab does not exist
> 3.688: ref tag c:\windows\system32\sp1.cab does not exist
> 3.688: ref tag c:\windows\system32\driver.cab does not exist
> 3.688: ref tag c:\windows\system32\fp40ext.cab does not exist
> 3.688: ref tag c:\windows\system32\fp40ext1.cab does not exist
> 3.688: ref tag c:\windows\system32\wms4.cab does not exist
> 3.688: ref tag c:\windows\system32\wms41.cab does not exist
> 3.688: ref tag c:\windows\system32\ims.cab does not exist
> 3.688: ref tag c:\windows\system32\ims1.cab does not exist
> 3.688: ref tag c:\windows\system32\ins.cab does not exist
> 3.688: ref tag c:\windows\system32\ins1.cab does not exist
> 3.688: Starting AnalyzeComponents
> 3.688: AnalyzePhaseZero used 0 ticks
> 3.703: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
> 3.703: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
> 7.438:
> C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem6.C
> AT trusts inf c:\windows\inf\oem6.inf of device
> HID\VID_051D&PID_0002\6&26251CE4
> &0&0000
> 14.000:
> C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem19
> .CAT trusts inf c:\windows\inf\oem19.inf of device
> PCI\VEN_1102&DEV_7003&SUBSYS_
> 00401102&REV_04\5&35CDC86&0&31F820
> 18.578: SetupVerifyInfFile failed with error 0x490 for oem17.inf of device
> ROOT\
> PROTOWALLMP_FD\0000
> 18.797: SetupVerifyInfFile failed with error 0x490 for
> c:\windows\inf\oem17.inf
> of device ROOT\PROTOWALLMP_FD\0000
> 18.828: SetupVerifyInfFile failed with error 0x490 for oem17.inf of device
> ROOT\
> PROTOWALLMP_FD\0001
> 18.984: SetupVerifyInfFile failed with error 0x490 for
> c:\windows\inf\oem17.inf
> of device ROOT\PROTOWALLMP_FD\0001
> 19.328: SetupVerifyInfFile failed with error 0x490 for oem3.inf of device
> ROOT\S
> YSTEM\0002
> 19.500: SetupVerifyInfFile failed with error 0x490 for
> c:\windows\inf\oem3.inf o
> f device ROOT\SYSTEM\0002
> 24.703: OEM file scan used 21000 ticks
> 24.719: AnalyzePhaseOne: used 21031 ticks
> 24.719: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> 24.719: AnalyzeComponents: Hotpatching is disabled.
> 24.719: FindFirstFile c:\windows\$hf_mig$\*.*
> 25.563: AnalyzeForBranching used 47 ticks.
> 25.563: AnalyzePhaseTwo used 0 ticks
> 25.563: AnalyzePhaseThree used 0 ticks
> 25.563: AnalyzePhaseFive used 0 ticks
> 25.563: AnalyzePhaseSix used 0 ticks
> 25.563: AnalyzeComponents used 21875 ticks
> 25.563: Downloading 2 files
> 25.563: bPatchMode = TRUE
> 25.563: Inventory complete: ReturnStatus=0, 21891 ticks
> 25.563: Num Ticks for invent : 21891
> 25.578: [dumpDownloadTask] Update.exe posting request file to download a
> total of 6758 bytes (6758 bytes in patches and 0 bytes in fallbacks)
> 25.578: dumpDownloadTask returned 0xf200 (more files to download)
> 25.641: KB896428 installation did not complete.
> 25.641: Update.exe extended error code = 0xf200
> 0.984:
> ================================================== =======================
> =======
>
> Sorry if this is redundant, but I did try searching for relevant posts
> without much luck. If anyone has any suggestions I am open to try anything.
> Thank you.

Well frankly it doesn't matter what the fix is, since none of the fixes work
or have ever worked. I have always had to manually download and install them
myself. I just thought a log file from one of the failed attempts would be
helpful.

"frustrated" wrote:

> I don't understand what the fix is?
>
> "" wrote:
>
> > Been having this problem forever it seems. I tried renaming the
> > windows\system32\catroot2\edb.log file and even the
> > windows\system32\catroot2\ directory but i am still unable to install
> > updates. there are no error codes anywhere. however, i think it has
> > something to do with WU not downloading the entire package. after the
> > updates have failed to install the first time, WU update reports that there
> > are 0kb to download and subsequent attempts to install the updates fail until
> > i search for the related KB article and manually download and install the
> > update. i have compared the size of the file when i manually download it to
> > the size initially reported by WU and the manual download is always larger.
> > maybe there is a clue in the log files for the updates. here is a sample:
> >
> > [KB896428.log]
> > 2.031:
> > ================================================== =======================
> > =======
> > 2.031: 2005/06/17 16:49:53.242 (local)
> > 2.047:
> > C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\50f1f908ea761d81e0511c7
> > cbc21c03d\update\update.exe (version 6.1.22.4)
> > 2.047: Hotfix started with following command line: /si
> > /ParentInfo:792ae71c8c274
> > c4b8ad47623278d573f
> > 3.547: DoInstallation: CleanPFR failed: 0x2
> > 3.563: SetProductTypes: InfProductBuildType=BuildType.IA
> > 3.563: SetAltOsLoaderPath: No section uses DirId 65701; done.
> > 3.672: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB896428$
> > 3.672: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
> > 0xe00
> > 00102
> > 3.688: ref tag c:\windows\system32\sp4.cab does not exist
> > 3.688: ref tag c:\windows\system32\sp3.cab does not exist
> > 3.688: ref tag c:\windows\system32\sp2.cab does not exist
> > 3.688: ref tag c:\windows\system32\sp1.cab does not exist
> > 3.688: ref tag c:\windows\system32\driver.cab does not exist
> > 3.688: ref tag c:\windows\system32\fp40ext.cab does not exist
> > 3.688: ref tag c:\windows\system32\fp40ext1.cab does not exist
> > 3.688: ref tag c:\windows\system32\wms4.cab does not exist
> > 3.688: ref tag c:\windows\system32\wms41.cab does not exist
> > 3.688: ref tag c:\windows\system32\ims.cab does not exist
> > 3.688: ref tag c:\windows\system32\ims1.cab does not exist
> > 3.688: ref tag c:\windows\system32\ins.cab does not exist
> > 3.688: ref tag c:\windows\system32\ins1.cab does not exist
> > 3.688: Starting AnalyzeComponents
> > 3.688: AnalyzePhaseZero used 0 ticks
> > 3.703: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
> > 3.703: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
> > 7.438:
> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem6.C
> > AT trusts inf c:\windows\inf\oem6.inf of device
> > HID\VID_051D&PID_0002\6&26251CE4
> > &0&0000
> > 14.000:
> > C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem19
> > .CAT trusts inf c:\windows\inf\oem19.inf of device
> > PCI\VEN_1102&DEV_7003&SUBSYS_
> > 00401102&REV_04\5&35CDC86&0&31F820
> > 18.578: SetupVerifyInfFile failed with error 0x490 for oem17.inf of device
> > ROOT\
> > PROTOWALLMP_FD\0000
> > 18.797: SetupVerifyInfFile failed with error 0x490 for
> > c:\windows\inf\oem17.inf
> > of device ROOT\PROTOWALLMP_FD\0000
> > 18.828: SetupVerifyInfFile failed with error 0x490 for oem17.inf of device
> > ROOT\
> > PROTOWALLMP_FD\0001
> > 18.984: SetupVerifyInfFile failed with error 0x490 for
> > c:\windows\inf\oem17.inf
> > of device ROOT\PROTOWALLMP_FD\0001
> > 19.328: SetupVerifyInfFile failed with error 0x490 for oem3.inf of device
> > ROOT\S
> > YSTEM\0002
> > 19.500: SetupVerifyInfFile failed with error 0x490 for
> > c:\windows\inf\oem3.inf o
> > f device ROOT\SYSTEM\0002
> > 24.703: OEM file scan used 21000 ticks
> > 24.719: AnalyzePhaseOne: used 21031 ticks
> > 24.719: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> > 24.719: AnalyzeComponents: Hotpatching is disabled.
> > 24.719: FindFirstFile c:\windows\$hf_mig$\*.*
> > 25.563: AnalyzeForBranching used 47 ticks.
> > 25.563: AnalyzePhaseTwo used 0 ticks
> > 25.563: AnalyzePhaseThree used 0 ticks
> > 25.563: AnalyzePhaseFive used 0 ticks
> > 25.563: AnalyzePhaseSix used 0 ticks
> > 25.563: AnalyzeComponents used 21875 ticks
> > 25.563: Downloading 2 files
> > 25.563: bPatchMode = TRUE
> > 25.563: Inventory complete: ReturnStatus=0, 21891 ticks
> > 25.563: Num Ticks for invent : 21891
> > 25.578: [dumpDownloadTask] Update.exe posting request file to download a
> > total of 6758 bytes (6758 bytes in patches and 0 bytes in fallbacks)
> > 25.578: dumpDownloadTask returned 0xf200 (more files to download)
> > 25.641: KB896428 installation did not complete.
> > 25.641: Update.exe extended error code = 0xf200
> > 0.984:
> > ================================================== =======================
> > =======
> >
> > Sorry if this is redundant, but I did try searching for relevant posts
> > without much luck. If anyone has any suggestions I am open to try anything.
> > Thank you.

"" <> wrote in message
news:29EFFBB8-8EA3-4E78-80FD-
> [Subject: WS 2003 SP2 updates failed to install]
....
> C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\50f1f908ea761d81e0511c7
> cbc21c03d\update\update.exe (version 6.1.22.4)

The path is a surprise to me for your OS.
Does it mean that you are using WUv5 or WUv6?
In any case I think it means that you could use bitsadmin
to monitor your downloads. That might give you more clues.
E.g. in a cmd window before starting a download enter:

bitsadmin /wrap /monitor /allusers

You need to press Ctrl-c to end the monitor.


> i have compared the size of the file when i manually download it to
> the size initially reported by WU and the manual download is always larger.

The bitsadmin /monitor will show you another aspect of file sizes
during the download phase.


So, do you have a WindowsUpdate.log too?

> there are no error codes anywhere.

Even so, it would give you some clues about the size of the download
and how it was extracted. BTW if you are trying to download
more than one update at a time it could be a good idea to just
do one at a time, since there is some evidence that loops and
other errors can occur when trying to extract more than one update
from a common download package.

Also, to supplement all these diagnostics what I like to do is Run...
FileMon (freeware from SysInternals) filtering on writes to
SoftwareDistribution;Update;CatRoot
E.g. that can clarify what the log messages really mean.


> 25.578: dumpDownloadTask returned 0xf200 (more files to download)

FWIW my guess is that the install phase is getting started too soon.
BTW what kind of update is this? E.g. WU (in which case unfortunately
install is automatic) or AU with prompt (which allows you to control
how install phase is done)?

Also, something which would probably be worthwhile if you have done
this install somewhere successfully and somwhere not is to compare
the two install logs. Even when we don't know exactly what it all means
making inferences about the differences is often worthwhile.


Good luck

Robert Aldwinckle
---

Thank you. (i meant to have "SP1" in the topic... obviously there is no WS
2003 SP2 yet. I must've been confusing it with WinXP.) WS 2003 SP1 does
indeed use WU v6

I don't have this "bitsadmin" cmd, why not? Is there some package i can get
that has it? I have since manually downloaded the updates from the WU
catalog, so the troubleshooting will have to wait until the next updates are
released.

My WindowsUpdate.log contains quite a bit of information, too much to post
here. So, here is the logged data from the 17th to today:
http://150.135.84.18/~scar/WindowsUpdate.log I ran WU on the 17th, the
19th, and today, the 22nd. You can see that I had problems on the 17th and
then more problems on the 19th. I also manually downloaded from WU Catalog
on the end of the 19th, and then did not need any updates on the 22nd. It
looks like a lot of valid clues are contained within. sorry I didn't know
about this log earlier.

"Robert Aldwinckle" wrote:

> "" <> wrote in message
> news:29EFFBB8-8EA3-4E78-80FD-
> > [Subject: WS 2003 SP2 updates failed to install]
> ....
> > C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\50f1f908ea761d81e0511c7
> > cbc21c03d\update\update.exe (version 6.1.22.4)
>
> The path is a surprise to me for your OS.
> Does it mean that you are using WUv5 or WUv6?
> In any case I think it means that you could use bitsadmin
> to monitor your downloads. That might give you more clues.
> E.g. in a cmd window before starting a download enter:
>
> bitsadmin /wrap /monitor /allusers
>
> You need to press Ctrl-c to end the monitor.
>
>
> > i have compared the size of the file when i manually download it to
> > the size initially reported by WU and the manual download is always larger.
>
> The bitsadmin /monitor will show you another aspect of file sizes
> during the download phase.
>
>
> So, do you have a WindowsUpdate.log too?
>
> > there are no error codes anywhere.
>
> Even so, it would give you some clues about the size of the download
> and how it was extracted. BTW if you are trying to download
> more than one update at a time it could be a good idea to just
> do one at a time, since there is some evidence that loops and
> other errors can occur when trying to extract more than one update
> from a common download package.
>
> Also, to supplement all these diagnostics what I like to do is Run...
> FileMon (freeware from SysInternals) filtering on writes to
> SoftwareDistribution;Update;CatRoot
> E.g. that can clarify what the log messages really mean.
>
>
> > 25.578: dumpDownloadTask returned 0xf200 (more files to download)
>
> FWIW my guess is that the install phase is getting started too soon.
> BTW what kind of update is this? E.g. WU (in which case unfortunately
> install is automatic) or AU with prompt (which allows you to control
> how install phase is done)?
>
> Also, something which would probably be worthwhile if you have done
> this install somewhere successfully and somwhere not is to compare
> the two install logs. Even when we don't know exactly what it all means
> making inferences about the differences is often worthwhile.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>

Thank you. (i meant to have "SP1" in the topic... obviously there is no WS
2003 SP2 yet. I must've been confusing it with WinXP.) WS 2003 SP1 does
indeed use WU v6

I don't have this "bitsadmin" cmd, why not? Is there some package i can get
that has it? I have since manually downloaded the updates from the WU
catalog, so the troubleshooting will have to wait until the next updates are
released.

My WindowsUpdate.log contains quite a bit of information, too much to post
here. So, here is the logged data from the 17th to today:
http://150.135.84.18/~scar/WindowsUpdate.log I ran WU on the 17th, the
19th, and today, the 22nd. You can see that I had problems on the 17th and
then more problems on the 19th. I also manually downloaded from WU Catalog
on the end of the 19th, and then did not need any updates on the 22nd. It
looks like a lot of valid clues are contained within. sorry I didn't know
about this log earlier.

"Robert Aldwinckle" wrote:

> "" <> wrote in message
> news:29EFFBB8-8EA3-4E78-80FD-
> > [Subject: WS 2003 SP2 updates failed to install]
> ....
> > C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\50f1f908ea761d81e0511c7
> > cbc21c03d\update\update.exe (version 6.1.22.4)
>
> The path is a surprise to me for your OS.
> Does it mean that you are using WUv5 or WUv6?
> In any case I think it means that you could use bitsadmin
> to monitor your downloads. That might give you more clues.
> E.g. in a cmd window before starting a download enter:
>
> bitsadmin /wrap /monitor /allusers
>
> You need to press Ctrl-c to end the monitor.
>
>
> > i have compared the size of the file when i manually download it to
> > the size initially reported by WU and the manual download is always larger.
>
> The bitsadmin /monitor will show you another aspect of file sizes
> during the download phase.
>
>
> So, do you have a WindowsUpdate.log too?
>
> > there are no error codes anywhere.
>
> Even so, it would give you some clues about the size of the download
> and how it was extracted. BTW if you are trying to download
> more than one update at a time it could be a good idea to just
> do one at a time, since there is some evidence that loops and
> other errors can occur when trying to extract more than one update
> from a common download package.
>
> Also, to supplement all these diagnostics what I like to do is Run...
> FileMon (freeware from SysInternals) filtering on writes to
> SoftwareDistribution;Update;CatRoot
> E.g. that can clarify what the log messages really mean.
>
>
> > 25.578: dumpDownloadTask returned 0xf200 (more files to download)
>
> FWIW my guess is that the install phase is getting started too soon.
> BTW what kind of update is this? E.g. WU (in which case unfortunately
> install is automatic) or AU with prompt (which allows you to control
> how install phase is done)?
>
> Also, something which would probably be worthwhile if you have done
> this install somewhere successfully and somwhere not is to compare
> the two install logs. Even when we don't know exactly what it all means
> making inferences about the differences is often worthwhile.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>

"" <> wrote in message
news:B1B597AB-A8EC-44D2-92D3-...
> Thank you. (i meant to have "SP1" in the topic... obviously there is no WS
> 2003 SP2 yet. I must've been confusing it with WinXP.) WS 2003 SP1 does
> indeed use WU v6
>
> I don't have this "bitsadmin" cmd, why not? Is there some package i can get
> that has it?

<title>KB892777 - Windows Server 2003 Service Pack 1 Support Tools</title>

(MSKB Boolean search for
bitsadmin AND "Windows Server 2003"
)



> I have since manually downloaded the updates from the WU
> catalog, so the troubleshooting will have to wait until the next updates are
> released.

Good plan. Get in some practice with FileMon before then too.
I expect it will really help clarify what is going on if not actually pinpoint
what is wrong.


>
> My WindowsUpdate.log contains quite a bit of information, too much to post
> here. So, here is the logged data from the 17th to today:
> http://150.135.84.18/~scar/WindowsUpdate.log I ran WU on the 17th, the
> 19th, and today, the 22nd. You can see that I had problems on the 17th and
> then more problems on the 19th. I also manually downloaded from WU Catalog
> on the end of the 19th, and then did not need any updates on the 22nd. It
> looks like a lot of valid clues are contained within. sorry I didn't know
> about this log earlier.


Somehow all the lineends are being ignored by Notepad.
Makes it much harder to scan quickly.
I'll try to have another look at it some time when I have restored
all my tools. (I'm still in the process of rebuilding a working partition.) ;]


Robert
---

"" <> wrote in message
news:B1B597AB-A8EC-44D2-92D3-
....
> WS 2003 SP1 does indeed use WU v6

> My WindowsUpdate.log contains quite a bit of information, too much to post
> here. So, here is the logged data from the 17th to today:
> http://150.135.84.18/~scar/WindowsUpdate.log I ran WU on the 17th, the
> 19th, and today, the 22nd. You can see that I had problems on the 17th and
> then more problems on the 19th. I also manually downloaded from WU Catalog
> on the end of the 19th, and then did not need any updates on the 22nd. It
> looks like a lot of valid clues are contained within. sorry I didn't know
> about this log earlier.

The code you are getting is 80240018 but the message you are getting
with it (Failed to find token for SID) was previously associated in WUv5
with codes 0x800704dd or (less frequently) 0x800706dd. 0x80240018
was then usually the code associated with the message "Could not impersonate
the user".

We have guessed from this that it could be a symptom of having
overly restrictive permissions on the accounts being used to do
the downloads or installs.

So far the best suggestion seems to be from Torgeir Bakken [MVP]
to use the secpol.msc tool to verify user rights.

http://groups-beta.google.com/group/...9d8a58483a0319


HTH

Robert
---

"Robert Aldwinckle" wrote:
<snip>
> So far the best suggestion seems to be from Torgeir Bakken [MVP]
> to use the secpol.msc tool to verify user rights.
>
> http://groups-beta.google.com/group/...9d8a58483a0319
>

Thanks i checked this out. Some of the rights did not include the
"Administrators" group, but just the user "Administrator". Do you think this
was an issue? i added the "Administrators" group anyway.

However, i have been reading around and read someplace about an error code
related to not accepting the license agreement before downloading updates.
That error might be in my log somewhere, because i notice that i am not asked
whether i agree or not to the license agreement. No window ever pops up
asking me. The first thing that happens is the download begins. Sorry i
didn't mention this earlier, but it's not exactly an easy thing to catch when
you have been using WU for so many years. i think this might be the root of
the problem. So what has happened that is preventing the agreement from
being shown? And how to fix this? Thank you

sorry i also wished to add that if i use the WU catalog to manually download
my updates, the agreement _is_ displayed.