Fix: Security updates fail to install for Office Viewers

Discussion in 'Windows Update' started by MowGreen [MVP], Aug 26, 2008.

  1. When attempting to install security updates to the Office Viewers
    [ Word, Powerpoint, Excel ] the update fails to install and the error
    code is 0x80070643 [1603]. The Application event log will show this for
    the installation failure:

    Product: Microsoft Office Excel Viewer 2003 - Update 'Security Update
    for Excel Viewer 2003 (KB918425): XLVIEW' could not be installed. Error
    code 1603. Additional information is available in the log file
    D:\DOCUME~1\MOWGRE~1\LOCALS~1\Temp\OfficeUpdate\OU(00003)_Msi.log.

    If the Office Source Engine service [Ose.exe] is started and Ose.exe is
    not corrupted, then the installation failure is related to the lack of
    the installation source file [ the file used to originally install the
    Office Viewer ].

    This lack of the installation source file can be caused by the User
    deleting it after a successful installation of the Office Viewer or by
    running a 'disk cleanup tool' that removed said installation file.

    To resolve the security update installation failure one *must* uninstall
    the Office Viewer it was intended for, download and *save* the Office
    Viewer installation file, move the installation file to a dedicated
    folder for it [name it Office Viewer; save it in My Documents, if so
    desired], and then reinstall the Office Viewer from *there*.

    * Do *not* delete this installation file *

    Subsequent security updates for the Office Viewer will now install
    successfully.


    MowGreen [MVP 2003-2008]
    ===============
    *-343-* FDNY
    Never Forgotten
    ===============
     
    MowGreen [MVP], Aug 26, 2008
    #1
    1. Advertisements

  2. Since you explicitly refer to the Excel Viewer 2003 let's stick to it:
    what is "the file used to originally install the Office Viewer"?

    From the MS Download Center you get XLVIEWER.EXE
    <http://www.microsoft.com/downloads/details.aspx?familyid=C8378BF4-996C-4569-B547-75EDBD03AAF0>,
    but that's not the file which is eventually missing: XLVIEWER.EXE is an
    self-extracting self-installing IExpress archive, containing SETUP.EXE,
    SETUP.INI, OSE.EXE, XLVIEW.MSI, XLVIEW.XML and XLVIEWER.CAB.

    When executed XLVIEWER.EXE unpacks itself to a subdirectory of %TEMP%
    and the "real" MSI setup is then started from there; check the uninstall
    registry entry

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90840407-6000-11D3-8CFE-0150048383C9}]
    "InstallSource"="D:\\DOCUME~1\\MOWGRE~1\\LOCALS~1\\Temp\\IXP000.TMP\\"

    (BTW: using an account with administrative rights for your everyday
    work is BAD!)

    or the Office product entries

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Registration\{90840407-6000-11D3-8CFE-0150048383C9}]
    "SmartSourceDir"="D:\\DOKUME~1\\MOWGRE~1\\LOKALS~1\\Temp\\IXP000.TMP\\"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\90840407-6000-11D3-8CFE-0150048383C9\Sources\90840407-
    6000-11D3-8CFE-0150048383C9]
    "Path"="D:\\DOKUME~1\\MOWGRE~1\\LOKALS~1\\Temp\\IXP000.TMP\\"
    "Priority"=dword:00000000

    No, that's wrong! The setup files unpacked from XLVIEWER.EXE are deleted
    upon exit/return from the setup to the unpacker.

    If the setup was successful then the XLVIEW.MSI as well as XLVIEWER.CAB
    are placed into the OSE cache:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\7040480900063D11C8EF10054038389C\SourceList]
    "PackageName"="XLVIEW.MSI"
    "LastUsedSource"=hex(2):6e,3b,31,3b,43,3a,5c,4d,53,4f,43,61,63,68,65,5c,41,6c,\
    6c,20,55,73,65,72,73,5c,39,30,38,34,30,34,30,37,2d,36,30,30,30,2d,31,31,44,\
    33,2d,38,43,46,45,2d,30,31,35,30,30,34,38,33,38,33,43,39,5c,00

    The REG_EXPAND_SZ translates to
    "n;1;C:\MSOCache\All Users\90840407-6000-11D3-8CFE-0150048383C9\"
    No, that's DEFINITELY NOT necessary!
    No, the installation file(s) can (and are!) safely be deleted.
    Only the XLVIEW.MSI and the XLVIEWER.CAB in the OSE cache have to be
    preserved.

    Now for the other 2003 viewers:

    * The original Word Viewer 2003 setup (WDVIEWER.EXE
    <http://www.microsoft.com/downloads/details.aspx?familyid=95E24C87-8732-48D5-8689-AB826E7B8FDF>)
    works the same.

    * The Word Viewer 2007^H3 with integrated SP3 (wordview_en-us.exe,
    <http://www.microsoft.com/downloads/details.aspx?FamilyID=3657ce88-7cfa-457a-9aec-f4f827f20cac>)
    uses the setup engine from Office 2007, which does NOT use the OSE,
    but places the WDVIEW.MSI, WORDVIEW.CAB and the WORDVIEWsp3.msp into
    %ProgramFiles%\MSECache\WordView\

    * The PowerPoint Viewer 2003 (PPVIEWER.EXE,
    <http://www.microsoft.com/downloads/details.aspx?familyid=428D5727-43AB-4F24-90B7-A94784AF71A4>)
    does NOT come with the OSE, there is just a PPVIEWER.MSI inside the
    IExpress archive.

    And this PPVIEWER.MSI will be missing, because it gets extracted to
    %TEMP%\IXP000.TMP\ during and deleted afterwards!

    It's a^Hjust the usual Microsoft mess!
    Stefan

    PS: If you but choose to unpack the XLVIEWER.EXE or WDVIEWER.EXE yourself
    and start their SETUP.EXE manually then no MSOCache will be created
    and YOU have to preserve the directory where you unpacked the
    installation files (and where the "LastUsedSource" registry entries
    point to).
    When you do so, you should know quite well what you are doing!
     
    Stefan Kanthak, Sep 15, 2008
    #2
    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.