"Sevec" <> wrote in message
news:8EBE7F49-5597-435B-ABD2-...
> Ok. Thank you for all information. I do Automatic Update on Win XP SP2 (build
> 2600). Update ends with "Some updates cannot be installed
> Update for Office 2003 (KB907417)
> Office 2003 Security Update for Microsoft Office Publisher 2003 (KB946254)
> Office 2003 Security Update for Microsoft Works Suite 2005 (KB943973)
> Office 2003 Update for Outlook Junk Email Filter 2003 (KB944941)
> Office 2003 Security Update for Office 2003 (KB945185)
> Office 2003 Security Update for Microsoft Office Word 2003 (KB943983)
> ."
Aha. So that code is related somehow to Office products. ; )
In that case you may get better assistance from a newsgroup
which specializes in them, in particular the Office Update NG.
Cross-posting so you can switch to it if you want.
>
> According to your post, I examined C:\windows\windowsupdate.log. It's very
> long. Maybe the interesting part is this one:
>
>
> 2008-02-19 14:18:30:932 884 c18 Agent WU client starts install in user
> context
> 2008-02-19 14:18:30:948 884 c18 DnldMgr Preparing update for install,
> updateId = {2631CB2A-8A93-496B-ADB8-731C6ED9E3BF}.101.
> 2008-02-19 14:18:30:948 884 c18 Agent WU client is installing update
> {2631CB2A-8A93-496B-ADB8-731C6ED9E3BF}.101
> 2008-02-19 14:18:30:948 1960 420 Misc =========== Logging initialized
> (build: 7.0.6000.381, tz: +0100) ===========
> 2008-02-19 14:18:30:979 1960 420 Misc = Process:
> C:\WINDOWS\system32\wuauclt.exe
> 2008-02-19 14:18:30:979 1960 420 Misc = Module:
> C:\WINDOWS\system32\wuaueng.dll
> 2008-02-19 14:18:30:948 1960 420 Handler :::::::::::::
> 2008-02-19 14:18:30:979 1960 420 Handler :: START :: Handler: MSI Install
> 2008-02-19 14:18:30:979 1960 420 Handler :::::::::
> 2008-02-19 14:18:30:979 1960 420 Handler : Updates to install = 1
> 2008-02-19 14:18:31:010 1960 420 Handler Extracting MSP file stored in CAB
> WINWORD.CAB
> 2008-02-19 14:18:31:135 1960 420 Handler MSP update
> {00000000-0000-0000-0000-000000000000}.0 using full-file patch
> 2008-02-19 14:18:31:135 1960 420 Handler : Batch installing 1 updates
> 2008-02-19 14:18:31:885 1960 420 Handler List of MSPs in transaction:
> 2008-02-19 14:18:31:885 1960 420 Handler
> C:\WINDOWS\SoftwareDistribution\Download\7e11c7880 aae143f9ddf9cebb76902bb\img\WINWORD.MSP
> 2008-02-19 14:18:31:885 1960 420 Handler MSP final command line:
> DISABLESRCPROMPT=1 LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1
> REBOOT=REALLYSUPPRESS
> 2008-02-19 14:19:23:240 1960 420 Handler MSP Error List:
> 2008-02-19 14:19:23:240 1960 420 Handler 1: 2932 2:
> C:\WINDOWS\Installer\{90110405-6000-11D3-8CFE-0150048383C9}\wordicon.exe 3:
> 23
> 2008-02-19 14:19:23:240 1960 420 Handler : MSI transaction completed. MSI:
> 0x80070643, Handler: 0x8024200b, Source: No, Reboot: 0
I suspect that this may be your best clue. For one thing it shows that the
install is MSI based, so that implies you could probably find supplementary
diagnostics associated with the install attempt *and* if you tried to do the
install of the update manually you could probably request verbose logging
(if it is not already available.)
To find such diagnostics simply search your harddrive(s) for all files which
were changed on that day. Then sort the results by Date Modified.
(E.g. use View, Details; make sure that you have Date Modified as one of the columns; and then either click on the Date Modified
column header
or use View, Arrange Icons By... to do that.) Then scroll to the files which
were changed about 14:19:23 (for example).
Secondly 0x8024000B is the only really specific error code you have so far.
The rest are really only things saying stuff like "there was an error" or "we really
didn't expect anybody to ever see this error..." <eg>
So let's do a search on that code. Unfortunately there is no consistency
about whether useful information will be found with it as being prefixed by 0x
or not, so I use a Boolean OR to find either in the all documents.
I first tried restricting my search to site:support.microsoft.com
but there were no hits there.
Unfortunately it seems that this one is a general code too:
(Live Search for
(0x8024000B OR 8024000B) site:microsoft.com
)
<quote>
0x8024000B
WU_E_CALL_CANCELLED
Operation was cancelled.
</quote>
I suspect in order to know _why_ the call was cancelled you are going
to have to get the corresponding verbose logging for the install attempt
(as described above.)
Otherwise it appears that any other hits from my last search involve
newsgroup queries or discussions. So let's try to find any which might
have had some suggestions in them...
http://search.msn.com/results.aspx?q...arch&form=QBRE
(Live Search for
(0x8024000B OR 8024000B) (MSFT OR MVP) site:microsoft.com
)
That whittled them down to 10 hits. Of the ones which are similar to yours
the suggestion has been to open a support case. There hasn't been much
feedback on that tack unfortunately.
> 2008-02-19 14:19:23:240 1960 420 Handler : WARNING: First failure for
> update {2631CB2A-8A93-496B-ADB8-731C6ED9E3BF}, transaction error =
> 0x8024200b, MSI result = 0x80070643, MSI action = PublishProduct
> 2008-02-19 14:19:23:240 1960 420 Handler : WARNING: Operation failed at
> update 0, Exit code = 0x8024200B
> 2008-02-19 14:19:23:240 1960 420 Handler :::::::::
> 2008-02-19 14:19:23:240 1960 420 Handler :: END :: Handler: MSI Install
> 2008-02-19 14:19:23:240 1960 420 Handler :::::::::::::
> 2008-02-19 14:19:23:240 884 480 AU >>## RESUMED ## AU: Installing update
> [UpdateId = {B0A19737-38A6-45AE-B2D9-B3B4874BA86B}]
> 2008-02-19 14:19:23:240 884 480 AU # WARNING: Install failed, error =
> 0x80070643 / 0x00000B74
> 2008-02-19 14:19:23:240 884 c18 Agent WU client finishes installing update
> {2631CB2A-8A93-496B-ADB8-731C6ED9E3BF}.101 with result 0x8024200b
>
>
> It would be great if you can examine this log and figure out what's happening.
>
> Thank you,
> Sev.
If you get some better clues from the verbose logging idea please post back.
It looks as if this is your chance to be a trailblazer... <eg>
Good luck
Robert
---