WSUS3, Vista, Office2007 updates

I have a puzzling issue with one of two test boxes on our network,
part of a trial system before deploying more widely.

We've recently set up a small network running Vista (Business
Edition) clients, Office 2007 software and a WSUS3 server. One of
the client boxes is getting all updates perfectly normally. However,
the other one is consistently failing to download and install just
three Office 2007 updates.

The WindowsUpdate log file contains 0x80072ee7 errors, which I know
usually mean a DNS issue. However, there is no proxy in the
network, proxycfg shows direct access, no firewall, no HOSTS file
modifications - and _all other_ updates are being downloaded
successfully, so I fail to understand what relevance this has. The
errors terminate in a further 0x8024402c error.

The other box, with very similar network settings as far as I can
tell, has already downloaded the three updates in question, so they
are available.

Can anyone give me a starter on where to look for a cause? I'm
probably missing something really obvious, and would thank anyone
who could point it out for me.

>2007-05-30 16:23:59:592 1040 1524 DnldMgr *************
>2007-05-30 16:23:59:593 1040 1524 DnldMgr ** START ** DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
>2007-05-30 16:23:59:593 1040 1524 DnldMgr *********
>2007-05-30 16:23:59:593 1040 1524 DnldMgr * Call ID = {5455A62E-731D-4E27-8747-0D5ADFDEC6DF}
>2007-05-30 16:23:59:593 1040 1524 DnldMgr * Priority = 3, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
>2007-05-30 16:23:59:593 1040 1524 DnldMgr * Updates to download = 1
>2007-05-30 16:23:59:593 1040 1524 Agent * Title = Update for Word 2007 (KB934173)
>2007-05-30 16:23:59:593 1040 1524 Agent * UpdateId = {C51DDB20-A7BF-4420-B285-C88DA9798C0C}.100
>2007-05-30 16:23:59:593 1040 1524 Agent * Bundles 1 updates:
>2007-05-30 16:23:59:593 1040 1524 Agent * {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100
>2007-05-30 16:23:59:668 1040 1524 Agent *********
>2007-05-30 16:23:59:668 1040 1524 Agent ** END ** Agent: Downloading updates [CallerId = AutomaticUpdates]
>2007-05-30 16:23:59:668 1040 1524 Agent *************
>
>2007-05-30 16:23:59:818 1040 1524 DnldMgr *************
>2007-05-30 16:23:59:818 1040 1524 DnldMgr ** START ** DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
>2007-05-30 16:23:59:818 1040 1524 DnldMgr *********
>2007-05-30 16:23:59:818 1040 1524 DnldMgr * Call ID = {CCF6D355-EAB5-4975-A5B7-90384C045570}
>2007-05-30 16:23:59:818 1040 1524 DnldMgr * Priority = 3, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
>2007-05-30 16:23:59:818 1040 1524 DnldMgr * Updates to download = 1
>2007-05-30 16:23:59:818 1040 1524 Agent * Title = Security Update for Excel 2007 (KB934670)
>2007-05-30 16:23:59:818 1040 1524 Agent * UpdateId = {786A447D-2FCE-40FD-8320-26324F5524FF}.100
>2007-05-30 16:23:59:818 1040 1524 Agent * Bundles 1 updates:
>2007-05-30 16:23:59:818 1040 1524 Agent * {30310F0A-BE62-49CC-9230-77FD165D8C80}.100
>2007-05-30 16:23:59:910 1040 1524 Agent *********
>2007-05-30 16:23:59:910 1040 1524 Agent ** END ** Agent: Downloading updates [CallerId = AutomaticUpdates]
>2007-05-30 16:23:59:910 1040 1524 Agent *************
>
>2007-05-30 16:23:59:950 1040 1524 DnldMgr *************
>2007-05-30 16:23:59:950 1040 1524 DnldMgr ** START ** DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
>2007-05-30 16:23:59:950 1040 1524 DnldMgr *********
>2007-05-30 16:23:59:950 1040 1524 DnldMgr * Call ID = {028C7542-1956-4840-911D-85903714319F}
>2007-05-30 16:23:59:950 1040 1524 DnldMgr * Priority = 3, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
>2007-05-30 16:23:59:950 1040 1524 DnldMgr * Updates to download = 1
>2007-05-30 16:23:59:950 1040 1524 Agent * Title = Security Update for Office 2007 (KB933688)
>2007-05-30 16:23:59:950 1040 1524 Agent * UpdateId = {C78B09E7-C78D-4172-B944-2A2C69B578E3}.100
>2007-05-30 16:23:59:950 1040 1524 Agent * Bundles 1 updates:
>2007-05-30 16:23:59:950 1040 1524 Agent * {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100
>2007-05-30 16:24:00:129 1040 1524 Agent *********
>2007-05-30 16:24:00:129 1040 1524 Agent ** END ** Agent: Downloading updates [CallerId = AutomaticUpdates]
>2007-05-30 16:24:00:129 1040 1524 Agent *************
>
>2007-05-30 16:24:02:314 1040 9c0 DnldMgr BITS job {D1563B41-05EC-4F5A-919C-285F21A32DF6} hit a transient error, updateId = {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100, error = 0x80072EE7
>2007-05-30 16:24:02:315 1040 9c0 DnldMgr Attempt no. 1 to resume the job
>2007-05-30 16:24:04:557 1040 df4 DnldMgr BITS job {29D90A62-D402-4AAA-90E2-2FB42942264B} hit a transient error, updateId = {30310F0A-BE62-49CC-9230-77FD165D8C80}.100, error = 0x80072EE7
>2007-05-30 16:24:04:557 1040 df4 DnldMgr Attempt no. 1 to resume the job
>2007-05-30 16:24:06:849 1040 9c0 DnldMgr BITS job {BEA297BD-A456-4FAA-90F8-66B2D4CBD96C} hit a transient error, updateId = {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100, error = 0x80072EE7
>2007-05-30 16:24:06:849 1040 9c0 DnldMgr Attempt no. 1 to resume the job
>2007-05-30 16:24:09:102 1040 df4 DnldMgr BITS job {D1563B41-05EC-4F5A-919C-285F21A32DF6} hit a transient error, updateId = {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100, error = 0x80072EE7
>2007-05-30 16:24:09:102 1040 df4 DnldMgr Attempt no. 2 to resume the job
>2007-05-30 16:24:11:335 1040 1424 DnldMgr BITS job {29D90A62-D402-4AAA-90E2-2FB42942264B} hit a transient error, updateId = {30310F0A-BE62-49CC-9230-77FD165D8C80}.100, error = 0x80072EE7
>2007-05-30 16:24:11:335 1040 1424 DnldMgr Attempt no. 2 to resume the job
>2007-05-30 16:24:13:603 1040 9c0 DnldMgr BITS job {BEA297BD-A456-4FAA-90F8-66B2D4CBD96C} hit a transient error, updateId = {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100, error = 0x80072EE7
>2007-05-30 16:24:13:603 1040 9c0 DnldMgr Attempt no. 2 to resume the job
>2007-05-30 16:24:15:832 1040 df4 DnldMgr BITS job {D1563B41-05EC-4F5A-919C-285F21A32DF6} hit a transient error, updateId = {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100, error = 0x80072EE7
>2007-05-30 16:24:15:832 1040 df4 DnldMgr Attempt no. 3 to resume the job
>2007-05-30 16:24:18:200 1040 9c0 DnldMgr BITS job {29D90A62-D402-4AAA-90E2-2FB42942264B} hit a transient error, updateId = {30310F0A-BE62-49CC-9230-77FD165D8C80}.100, error = 0x80072EE7
>2007-05-30 16:24:18:200 1040 9c0 DnldMgr Attempt no. 3 to resume the job
>2007-05-30 16:24:20:388 1040 df4 DnldMgr BITS job {BEA297BD-A456-4FAA-90F8-66B2D4CBD96C} hit a transient error, updateId = {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100, error = 0x80072EE7
>2007-05-30 16:24:20:388 1040 df4 DnldMgr Attempt no. 3 to resume the job
>
>2007-05-30 16:24:22:602 1040 9c0 DnldMgr BITS job {D1563B41-05EC-4F5A-919C-285F21A32DF6} hit a transient error, updateId = {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100, error = 0x80072EE7
>2007-05-30 16:24:22:602 1040 9c0 DnldMgr Will not attempt to resume the job as it has reached the maximum number of attempts.
>2007-05-30 16:24:22:602 1040 9c0 DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
>2007-05-30 16:24:22:710 1040 17b4 AU >>## RESUMED ## AU: Download update [UpdateId = {C51DDB20-A7BF-4420-B285-C88DA9798C0C}]
>2007-05-30 16:24:22:710 1040 17b4 AU # WARNING: Download failed, error = 0x8024402C
>
>2007-05-30 16:24:24:854 1040 1424 DnldMgr BITS job {29D90A62-D402-4AAA-90E2-2FB42942264B} hit a transient error, updateId = {30310F0A-BE62-49CC-9230-77FD165D8C80}.100, error = 0x80072EE7
>2007-05-30 16:24:24:854 1040 1424 DnldMgr Will not attempt to resume the job as it has reached the maximum number of attempts.
>2007-05-30 16:24:24:854 1040 1424 DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
>2007-05-30 16:24:24:921 1040 17b4 AU >>## RESUMED ## AU: Download update [UpdateId = {786A447D-2FCE-40FD-8320-26324F5524FF}]
>2007-05-30 16:24:24:921 1040 17b4 AU # WARNING: Download failed, error = 0x8024402C
>
>2007-05-30 16:24:27:104 1040 df4 DnldMgr BITS job {BEA297BD-A456-4FAA-90F8-66B2D4CBD96C} hit a transient error, updateId = {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100, error = 0x80072EE7
>2007-05-30 16:24:27:104 1040 df4 DnldMgr Will not attempt to resume the job as it has reached the maximum number of attempts.
>2007-05-30 16:24:27:104 1040 df4 DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
>2007-05-30 16:24:27:146 1040 17b4 AU >>## RESUMED ## AU: Download update [UpdateId = {C78B09E7-C78D-4172-B944-2A2C69B578E3}]
>2007-05-30 16:24:27:146 1040 17b4 AU # WARNING: Download failed, error = 0x8024402C

you are getting a gernal network error in bits Please review ms article
http://support.microsoft.com/kb/836941 to troublehoot

In summary BITS is having issue resolveing the hostname or ip address of the
WSUS server

"Pete Murray" wrote:

> I have a puzzling issue with one of two test boxes on our network,
> part of a trial system before deploying more widely.
>
> We've recently set up a small network running Vista (Business
> Edition) clients, Office 2007 software and a WSUS3 server. One of
> the client boxes is getting all updates perfectly normally. However,
> the other one is consistently failing to download and install just
> three Office 2007 updates.
>
> The WindowsUpdate log file contains 0x80072ee7 errors, which I know
> usually mean a DNS issue. However, there is no proxy in the
> network, proxycfg shows direct access, no firewall, no HOSTS file
> modifications - and _all other_ updates are being downloaded
> successfully, so I fail to understand what relevance this has. The
> errors terminate in a further 0x8024402c error.
>
> The other box, with very similar network settings as far as I can
> tell, has already downloaded the three updates in question, so they
> are available.
>
> Can anyone give me a starter on where to look for a cause? I'm
> probably missing something really obvious, and would thank anyone
> who could point it out for me.
>
> >2007-05-30 16:23:59:592 1040 1524 DnldMgr *************
> >2007-05-30 16:23:59:593 1040 1524 DnldMgr ** START ** DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
> >2007-05-30 16:23:59:593 1040 1524 DnldMgr *********
> >2007-05-30 16:23:59:593 1040 1524 DnldMgr * Call ID = {5455A62E-731D-4E27-8747-0D5ADFDEC6DF}
> >2007-05-30 16:23:59:593 1040 1524 DnldMgr * Priority = 3, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
> >2007-05-30 16:23:59:593 1040 1524 DnldMgr * Updates to download = 1
> >2007-05-30 16:23:59:593 1040 1524 Agent * Title = Update for Word 2007 (KB934173)
> >2007-05-30 16:23:59:593 1040 1524 Agent * UpdateId = {C51DDB20-A7BF-4420-B285-C88DA9798C0C}.100
> >2007-05-30 16:23:59:593 1040 1524 Agent * Bundles 1 updates:
> >2007-05-30 16:23:59:593 1040 1524 Agent * {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100
> >2007-05-30 16:23:59:668 1040 1524 Agent *********
> >2007-05-30 16:23:59:668 1040 1524 Agent ** END ** Agent: Downloading updates [CallerId = AutomaticUpdates]
> >2007-05-30 16:23:59:668 1040 1524 Agent *************
> >
> >2007-05-30 16:23:59:818 1040 1524 DnldMgr *************
> >2007-05-30 16:23:59:818 1040 1524 DnldMgr ** START ** DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
> >2007-05-30 16:23:59:818 1040 1524 DnldMgr *********
> >2007-05-30 16:23:59:818 1040 1524 DnldMgr * Call ID = {CCF6D355-EAB5-4975-A5B7-90384C045570}
> >2007-05-30 16:23:59:818 1040 1524 DnldMgr * Priority = 3, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
> >2007-05-30 16:23:59:818 1040 1524 DnldMgr * Updates to download = 1
> >2007-05-30 16:23:59:818 1040 1524 Agent * Title = Security Update for Excel 2007 (KB934670)
> >2007-05-30 16:23:59:818 1040 1524 Agent * UpdateId = {786A447D-2FCE-40FD-8320-26324F5524FF}.100
> >2007-05-30 16:23:59:818 1040 1524 Agent * Bundles 1 updates:
> >2007-05-30 16:23:59:818 1040 1524 Agent * {30310F0A-BE62-49CC-9230-77FD165D8C80}.100
> >2007-05-30 16:23:59:910 1040 1524 Agent *********
> >2007-05-30 16:23:59:910 1040 1524 Agent ** END ** Agent: Downloading updates [CallerId = AutomaticUpdates]
> >2007-05-30 16:23:59:910 1040 1524 Agent *************
> >
> >2007-05-30 16:23:59:950 1040 1524 DnldMgr *************
> >2007-05-30 16:23:59:950 1040 1524 DnldMgr ** START ** DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
> >2007-05-30 16:23:59:950 1040 1524 DnldMgr *********
> >2007-05-30 16:23:59:950 1040 1524 DnldMgr * Call ID = {028C7542-1956-4840-911D-85903714319F}
> >2007-05-30 16:23:59:950 1040 1524 DnldMgr * Priority = 3, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
> >2007-05-30 16:23:59:950 1040 1524 DnldMgr * Updates to download = 1
> >2007-05-30 16:23:59:950 1040 1524 Agent * Title = Security Update for Office 2007 (KB933688)
> >2007-05-30 16:23:59:950 1040 1524 Agent * UpdateId = {C78B09E7-C78D-4172-B944-2A2C69B578E3}.100
> >2007-05-30 16:23:59:950 1040 1524 Agent * Bundles 1 updates:
> >2007-05-30 16:23:59:950 1040 1524 Agent * {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100
> >2007-05-30 16:24:00:129 1040 1524 Agent *********
> >2007-05-30 16:24:00:129 1040 1524 Agent ** END ** Agent: Downloading updates [CallerId = AutomaticUpdates]
> >2007-05-30 16:24:00:129 1040 1524 Agent *************
> >
> >2007-05-30 16:24:02:314 1040 9c0 DnldMgr BITS job {D1563B41-05EC-4F5A-919C-285F21A32DF6} hit a transient error, updateId = {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100, error = 0x80072EE7
> >2007-05-30 16:24:02:315 1040 9c0 DnldMgr Attempt no. 1 to resume the job
> >2007-05-30 16:24:04:557 1040 df4 DnldMgr BITS job {29D90A62-D402-4AAA-90E2-2FB42942264B} hit a transient error, updateId = {30310F0A-BE62-49CC-9230-77FD165D8C80}.100, error = 0x80072EE7
> >2007-05-30 16:24:04:557 1040 df4 DnldMgr Attempt no. 1 to resume the job
> >2007-05-30 16:24:06:849 1040 9c0 DnldMgr BITS job {BEA297BD-A456-4FAA-90F8-66B2D4CBD96C} hit a transient error, updateId = {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100, error = 0x80072EE7
> >2007-05-30 16:24:06:849 1040 9c0 DnldMgr Attempt no. 1 to resume the job
> >2007-05-30 16:24:09:102 1040 df4 DnldMgr BITS job {D1563B41-05EC-4F5A-919C-285F21A32DF6} hit a transient error, updateId = {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100, error = 0x80072EE7
> >2007-05-30 16:24:09:102 1040 df4 DnldMgr Attempt no. 2 to resume the job
> >2007-05-30 16:24:11:335 1040 1424 DnldMgr BITS job {29D90A62-D402-4AAA-90E2-2FB42942264B} hit a transient error, updateId = {30310F0A-BE62-49CC-9230-77FD165D8C80}.100, error = 0x80072EE7
> >2007-05-30 16:24:11:335 1040 1424 DnldMgr Attempt no. 2 to resume the job
> >2007-05-30 16:24:13:603 1040 9c0 DnldMgr BITS job {BEA297BD-A456-4FAA-90F8-66B2D4CBD96C} hit a transient error, updateId = {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100, error = 0x80072EE7
> >2007-05-30 16:24:13:603 1040 9c0 DnldMgr Attempt no. 2 to resume the job
> >2007-05-30 16:24:15:832 1040 df4 DnldMgr BITS job {D1563B41-05EC-4F5A-919C-285F21A32DF6} hit a transient error, updateId = {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100, error = 0x80072EE7
> >2007-05-30 16:24:15:832 1040 df4 DnldMgr Attempt no. 3 to resume the job
> >2007-05-30 16:24:18:200 1040 9c0 DnldMgr BITS job {29D90A62-D402-4AAA-90E2-2FB42942264B} hit a transient error, updateId = {30310F0A-BE62-49CC-9230-77FD165D8C80}.100, error = 0x80072EE7
> >2007-05-30 16:24:18:200 1040 9c0 DnldMgr Attempt no. 3 to resume the job
> >2007-05-30 16:24:20:388 1040 df4 DnldMgr BITS job {BEA297BD-A456-4FAA-90F8-66B2D4CBD96C} hit a transient error, updateId = {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100, error = 0x80072EE7
> >2007-05-30 16:24:20:388 1040 df4 DnldMgr Attempt no. 3 to resume the job
> >
> >2007-05-30 16:24:22:602 1040 9c0 DnldMgr BITS job {D1563B41-05EC-4F5A-919C-285F21A32DF6} hit a transient error, updateId = {0A0306C1-AAF8-469F-94BB-7091352A6B63}.100, error = 0x80072EE7
> >2007-05-30 16:24:22:602 1040 9c0 DnldMgr Will not attempt to resume the job as it has reached the maximum number of attempts.
> >2007-05-30 16:24:22:602 1040 9c0 DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
> >2007-05-30 16:24:22:710 1040 17b4 AU >>## RESUMED ## AU: Download update [UpdateId = {C51DDB20-A7BF-4420-B285-C88DA9798C0C}]
> >2007-05-30 16:24:22:710 1040 17b4 AU # WARNING: Download failed, error = 0x8024402C
> >
> >2007-05-30 16:24:24:854 1040 1424 DnldMgr BITS job {29D90A62-D402-4AAA-90E2-2FB42942264B} hit a transient error, updateId = {30310F0A-BE62-49CC-9230-77FD165D8C80}.100, error = 0x80072EE7
> >2007-05-30 16:24:24:854 1040 1424 DnldMgr Will not attempt to resume the job as it has reached the maximum number of attempts.
> >2007-05-30 16:24:24:854 1040 1424 DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
> >2007-05-30 16:24:24:921 1040 17b4 AU >>## RESUMED ## AU: Download update [UpdateId = {786A447D-2FCE-40FD-8320-26324F5524FF}]
> >2007-05-30 16:24:24:921 1040 17b4 AU # WARNING: Download failed, error = 0x8024402C
> >
> >2007-05-30 16:24:27:104 1040 df4 DnldMgr BITS job {BEA297BD-A456-4FAA-90F8-66B2D4CBD96C} hit a transient error, updateId = {9A7FB932-CD86-4D31-9FDB-6801D2FF5AE8}.100, error = 0x80072EE7
> >2007-05-30 16:24:27:104 1040 df4 DnldMgr Will not attempt to resume the job as it has reached the maximum number of attempts.
> >2007-05-30 16:24:27:104 1040 df4 DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
> >2007-05-30 16:24:27:146 1040 17b4 AU >>## RESUMED ## AU: Download update [UpdateId = {C78B09E7-C78D-4172-B944-2A2C69B578E3}]
> >2007-05-30 16:24:27:146 1040 17b4 AU # WARNING: Download failed, error = 0x8024402C
>

On Thu, 31 May 2007 17:09:00 -0700, chuck
<> wrote:

>you are getting a gernal network error in bits Please review ms article
>http://support.microsoft.com/kb/836941 to troublehoot
>
>In summary BITS is having issue resolveing the hostname or ip address of the
>WSUS server

Yes, that's what I thought at first. However, the client has and
continues to pick up other updates from the server, and none of the
issues in KB836941 seems to be relevant - no firewall, no proxy
server, no HOSTS table mods.

Why only these three updates, and why only this client?
--

Pete
KLV1000 - the IrnBru Special

"Pete Murray" <> wrote in message
news:...
> On Thu, 31 May 2007 17:09:00 -0700, chuck
> <> wrote:
>
>>you are getting a gernal network error in bits Please review ms article
>>http://support.microsoft.com/kb/836941 to troublehoot
>>
>>In summary BITS is having issue resolveing the hostname or ip address of the
>>WSUS server
>
> Yes, that's what I thought at first. However, the client has and
> continues to pick up other updates from the server, and none of the
> issues in KB836941 seems to be relevant - no firewall, no proxy
> server, no HOSTS table mods.
>
> Why only these three updates, and why only this client?


Have you tried clearing the SoftwareDistribution\Download directory?
Note that this is a common resolution step for various problem symptoms
associated with WU.


FWIW on XP I would try using verbose logging + ProcMon, bitsadmin,
fiddler and netcap (formatted by Ethereal) as diagnostics. Tdimon might
even be enough to see what the failing requests are but I haven't used it,
since I am used to the other tools I mentioned.


Good luck

Robert Aldwinckle
---

On Sat, 2 Jun 2007 12:26:08 -0400, "Robert Aldwinckle"
<> wrote:

>Have you tried clearing the SoftwareDistribution\Download directory?
>Note that this is a common resolution step for various problem symptoms
>associated with WU.
>
>
>FWIW on XP I would try using verbose logging + ProcMon, bitsadmin,
>fiddler and netcap (formatted by Ethereal) as diagnostics. Tdimon might
>even be enough to see what the failing requests are but I haven't used it,
>since I am used to the other tools I mentioned.
>
>
>Good luck
>
>Robert Aldwinckle
>---
>

Hmm, I think I should thank you for introducing me to a completely
new set of complications! I never knew about that folder and its
contents before.

The three 'missing' downloads were within the directory, so I
deleted them. Re-ran the update procedure, which successfully
managed to grab the latest Defender definitions - and then crashed
on the Office ones :-(

However, I suspect the answer to the problem still lies somewhere in
the SoftwareDistribution tree - mainly because there isn't anywhere
else relevant. I'm going to clear as much as I can, then leave the
box for another 22 hour cycle, and see if it picks up the downloads
by itself again.

If that fails, it's down to some of the diagnostic tools you
mention. We were trying to keep these test boxes clean, but that's
no use if the updates aren't working.

Thanks!

Pete

Bad form to follow up my own message, but in case anyone is
interested, here's the outcome:

The problem was resolved by removing the client from the WSUS3
database and letting it re-register itself. This led to an
automatic download and install of the missing updates.

Further investigation indicates that the three updates were at some
point updated themselves on the WSUS server, deleting the original
files. I'm presuming that the client picked up on the need for the
updates between the server downloads - when it came to request the
original files, they were no longer available, and hence the server
couldn't fulfil the request. By re-registering, a new client-server
sync took place and the updated updates were presented successfully.

Well, it works for me.

(cross-post added to WSUS)
"Pete Murray" <> wrote in message
news:...
> Bad form to follow up my own message, but in case anyone is
> interested, here's the outcome:
>
> The problem was resolved by removing the client from the WSUS3
> database and letting it re-register itself. This led to an
> automatic download and install of the missing updates.


Since the resolution occurred on the WSUS server
I guess it would have helped to have been posting there earlier.
I was just trying to help you get some diagnostics on the client side.

I still wonder if a verbose log would have given you any better clues
than that ambiguous error code. ; )

Thanks for sharing your solution.


Robert
---


>
> Further investigation indicates that the three updates were at some
> point updated themselves on the WSUS server, deleting the original
> files. I'm presuming that the client picked up on the need for the
> updates between the server downloads - when it came to request the
> original files, they were no longer available, and hence the server
> couldn't fulfil the request. By re-registering, a new client-server
> sync took place and the updated updates were presented successfully.
>
> Well, it works for me.


Full-thread:

http://www.microsoft.com/communities...e-2f4a86d5da3b

On Mon, 4 Jun 2007 16:00:26 -0400, "Robert Aldwinckle"
<> wrote:

>(cross-post added to WSUS)
>
>
>Since the resolution occurred on the WSUS server
>I guess it would have helped to have been posting there earlier.
>I was just trying to help you get some diagnostics on the client side.
>

As the other client machine had updated perfectly normally, I didn't
think there was a WSUS problem and assumed the issue had to lie on
the client side. These boxes aren't perfect replicas (desktop vs
laptop) and it seems natural to assume some intrinsic difference
might have caused the problem. In the end, it just came down to a
matter of timing, I guess. Only after researching the actual
history of these updates did I see the originals had had a short
lifespan on the server before being replaced - after that, it all
clicked into place.

>I still wonder if a verbose log would have given you any better clues
>than that ambiguous error code. ; )

You mean there is a _more_ detailed log than the update one I
(reluctantly) posted?

>
>Thanks for sharing your solution.
>

It only seemed fair to do so, in the hope that someone else might
avoid the three days of serious hair damage.

Thanks,

Pete

"Pete Murray" <> wrote in message
news:...
> On Mon, 4 Jun 2007 16:00:26 -0400, "Robert Aldwinckle"
> <> wrote:
>
>>(cross-post added to WSUS)
>>
>>
>>Since the resolution occurred on the WSUS server
>>I guess it would have helped to have been posting there earlier.
>>I was just trying to help you get some diagnostics on the client side.
>>
>
> As the other client machine had updated perfectly normally, I didn't
> think there was a WSUS problem and assumed the issue had to lie on
> the client side. These boxes aren't perfect replicas (desktop vs
> laptop) and it seems natural to assume some intrinsic difference
> might have caused the problem. In the end, it just came down to a
> matter of timing, I guess. Only after researching the actual
> history of these updates did I see the originals had had a short
> lifespan on the server before being replaced - after that, it all
> clicked into place.
>
>>I still wonder if a verbose log would have given you any better clues
>>than that ambiguous error code. ; )
>
> You mean there is a _more_ detailed log than the update one I
> (reluctantly) posted?


Supposedly. ; )

http://support.microsoft.com/kb/902093

<quote>
How to enable extended logging

Microsoft Product Support Services may ask you to turn on verbose logging.
To turn on verbose logging, add the following registry key with two values:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\Trace

Value name: Flags
Value type: REG_DWORD
Value data: 00000007

Value name: Level
Value type: REG_DWORD
Value data: 00000004

This registry key turns on an extended tracing to the %systemroot%\Windowsupdate.log file.
Additionally, this registry key turns on an extended tracing to any attached debuggers.
</quote>

As I noted I find the supplementary information provided by a ProcMon trace
especially useful for trying to decipher what the log messages are really implying... <eg>


>
>>
>>Thanks for sharing your solution.
>>
>
> It only seemed fair to do so, in the hope that someone else might
> avoid the three days of serious hair damage.


: )


>
> Thanks,
>
> Pete


You're welcome.


Robert
---