Failure of Security Updates for Office 2003 KB914455 & KB917151

Discussion in 'Windows Update' started by JPL, Jul 14, 2006.

  1. JPL

    JPL Guest

    I am very disappointed with the poor quality of the Microsoft security patch
    update process. For the second time this year I have had to reinstall Office
    in order to attempt to install an update, and this time even that step was
    unsuccessful. I see from other threads that the finger is being pointed at
    registry cleaners and Windows Live Safety Center, but have used neither of
    these.

    All the July updates installed correctly except Security Updates for Office
    2003 KB914455 & KB917151, which failed as follows:
    Installation Failure: Windows failed to install the following update with
    error 0x80070643

    I followed the usual checking/diagnostic measures suggested here. As Per
    KB903774 I checked that OSE was running correctly. It is.

    Office Detect & Repair was run successfully, but did not correct the
    problem.

    KB906602 suggests looking at the MSP error list, but in this case the list
    says, "No messages in the MSP error list."

    I therefore reinstalled Office 2003 Pro completely, even though there had
    been no problems or unexpected behaviour at all (with the exception of this
    update failure) in using Office since it was installed in April.
    The process I followed was:
    1. uninstalled Office via Add/Remove Programs and then rebooted PC
    2. installed Office and then rebooted PC
    3. installed SP2 and then rebooted PC
    4. deleted previously downloaded files for KB914455 & KB917151
    5. ran Microsoft Update

    In this run of Microsoft Update, 6 of the 8 Office updates installed
    correctly and only KB914455 & KB917151 failed (yet again).

    Reinstalling Office failed to correct the problem. The problem is clearly
    with these two updates rather than with the update process per se.

    ------------------------------

    The Windows update log shows the follwing details:

    4 12:38:31 2844 cb0 Handler :::::::::::::
    2006-07-14 12:38:31 2844 cb0 Handler :: START :: Handler: MSI Install
    2006-07-14 12:38:31 2844 cb0 Handler :::::::::
    2006-07-14 12:38:31 2844 cb0 Handler : Updates to install = 2
    2006-07-14 12:38:31 2844 cb0 Handler Extracting MSP file stored in CAB MSO.CAB
    2006-07-14 12:38:31 2844 cb0 Handler MSI update
    {7C997700-2131-441C-A59C-6E8EC23190B3}.100 using full-file patch
    2006-07-14 12:38:31 2844 cb0 Handler Extracting MSP file stored in CAB
    PVMSO.CAB
    2006-07-14 12:38:31 2844 cb0 Handler MSI update
    {EABB9B5B-CEDD-409D-834D-243D78D2BE3A}.100 using full-file patch
    2006-07-14 12:38:31 2844 cb0 Handler : Batch installing 2 updates
    2006-07-14 12:38:36 792 328 Report REPORT EVENT:
    {C964A41E-0B86-4750-AD88-AB8500CFF858} 2006-07-14
    12:38:31+0100 1 182 101 {872266B6-1140-446A-8778-3E2987DF94B3} 100 80070643 MicrosoftUpdate Failure Content
    Install Installation Failure: Windows failed to install the following update
    with error 0x80070643: Security Update for Office 2003 (KB914455).
    2006-07-14 12:38:39 2844 cb0 Handler List of MSPs in transaction:
    2006-07-14 12:38:39 2844 cb0 Handler
    C:\WINDOWS\SoftwareDistribution\Download\2355c51bee71ef53c3f183731949b7f5\MSO.MSP
    2006-07-14 12:38:39 2844 cb0 Handler MSP final command line:
    DISABLESRCPROMPT=1 LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1
    REBOOT=REALLYSUPPRESS
    2006-07-14 12:38:43 2844 cb0 Handler MSP Error List:
    2006-07-14 12:38:43 2844 cb0 Handler No messages in the MSP error list.
    2006-07-14 12:38:43 2844 cb0 Handler : MSI transaction completed. MSI:
    0x80070643, Handler: 0x8024200b, Source: No, Reboot: 0
    2006-07-14 12:38:43 2844 cb0 Handler : WARNING: First failure for update
    {7C997700-2131-441C-A59C-6E8EC23190B3}, transaction error = 0x8024200b, MSI
    result = 0x80070643, MSI action = StartCache
    2006-07-14 12:38:43 2844 cb0 Handler : WARNING: Operation failed at update
    0, Exit code = 0x8024200B
    2006-07-14 12:38:43 2844 cb0 Handler :::::::::
    2006-07-14 12:38:43 2844 cb0 Handler :: END :: Handler: MSI Install
    2006-07-14 12:38:43 2844 cb0 Handler :::::::::::::
     
    JPL, Jul 14, 2006
    #1
    1. Advertisements

  2. ....
    A newsgroup which specializes in updating Office Products? ; )

    (Cross-posting your complete post to one for you.)

    ....


    If your problem occurred during the install phase there should be
    a better log than just the WU log. If necessary search your harddrive
    for files which changed during the interval that the update was running
    to find one. E.g. search for files which changed that day and then
    sort the results list by Date Modified.

    Otherwise my approach to diagnosing this would be to use RegMon
    and FileMon to supplement any logs. Make sure that your FileMon
    filter includes any writes done to the logs. That way you can assign
    an accurate timestamp to each log record and correlate them
    with the two traces.

    Another common possibility is requesting a /verbose log (if available).
    However, I have had more luck with the FileMon approach.

    I notice that others with this symptom think that registry problems
    are at issue. In that case again, taking concurrent RegMon and FileMon
    traces would undoubtedly be useful. The FileMon trace in that case
    would only be needed to capture the writes of the log messages
    in order to assign a timestamp with millesecond granularity,
    so that you could then correlate the registry trace with the the update's log
    records. Make sure that you check the options Show Millesconds
    and Clock Time on both tools to make the correlation easiest.
    You have to do some inference based on the record size
    when assigning the timestamps. You can use Notepad's
    View Status Bar (with Word Wrap off) to test the log records
    for their size. Fortunately, the records in most logs are
    quite variable in size so finding a match in the two patterns
    is relatively easy.

    FYI RegMon and FileMon are both freeware from SysInternals.


    Good luck

    Robert Aldwinckle
    ---
     
    Robert Aldwinckle, Jul 16, 2006
    #2
    1. Advertisements

  3. Disable any form of anti-malware or anti-BHO application, then try these
    updates again.
     
    Robin Walker [MVP], Jul 16, 2006
    #3
  4. JPL

    JPL Guest

    This problem was not caused by an anti-malware application, and I always
    close down Zone Alarm Security Suite while applying the monthly updates. As
    for anti-BHO applications, I have no idea - what does BHO stand for?

    Please see my own reply to my posting in the Office Updates newsgroup.

    (I would have posted in the Office Updates newsgroup only, but posted here
    because this was the link provided by Microsoft.)
     
    JPL, Jul 16, 2006
    #4
  5. JPL

    lrp Guest

    I had the same problem with this update...searched and searched and finally
    found the following article: http://support.microsoft.com/?id=884298 which
    contains instructions to modify some registry values. I followed the steps
    exactly and was immediately able to successfully install the troublesome
    updates. Hope this helps.

    Lyle Pardee

     
    lrp, Jul 17, 2006
    #5
  6. JPL

    reghir Guest

    http://support.microsoft.com/?id=884298 solved my install.Found two entries
    under sources one contained a Path REG_EXPAND_SZ F:\
    and the other source did not even contain a path statement so edited it and
    added the same as first source and viola both KB14555 and KB91715.I have a
    funny suspension that when loading Micorsoft Office 2007 (beta) the second
    source was added without a Path and that's what confused these updates.
    Hope this helps and thanks for the research.


     
    reghir, Jul 18, 2006
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.