+ Reply to Thread
Results 1 to 3 of 3

Thread: Issues installing non-standard Office applications after Office 2003

  1. #1
    Join Date
    Jul 2010
    Posts
    2

    Question Issues installing non-standard Office applications after Office 2003

    Hi there,

    I used Office Integrator to create an installer for Office 2003 Standard. It works great, but if I install it on a computer and then install another Office 2003 program (Access, Publisher, etc.), I run into problems.

    For example, just the other day I tried to install Publisher after using my Office 2003 Standard installer that I built with Office Integrator. I then went to the Microsoft Update website to download and installer the latest updates for Publisher. There were around 10 updates, if I recall correctly. All of them required user interaction in order to install. They would show a window like this:



    I've tested this on multiple computers, so I know it's not a problem with the computer. I've also tried to recreate this scenario without using the installer that I made using Office Integrator and was unable to.

    Does anybody have a workaround for this? Thanks!
    Follow Siginet's latest software venture on Facebook!
    Just click on the LIKE button on his new website here:

    www.ITTechware.com

  2. #2
    Join Date
    Mar 2010
    Posts
    7

    Default

    One step at a time:

    WORKS632.msp is the actual patch contained in MS08-011 / "Vulnerabilities in Microsoft Works File Converter", which equates to KB943973 for Office 2003. From the download center, this would be known as office2003-KB943973-FullFile-ENU.exe

    I'm guessing that Office Integrator integrated this into your Office 2003 Standard install, then threw away the patch itself. However, the registry retains not only the patch details, but also should hold the folder the patch was kept in. When you come along with Publisher, the Installer is trying to fetch the patch location from the registry and then failing.

    For a workaround:

    Have you tried downloading the HotPack for Office 2003, unpacking the contents to a folder (with 7zip) and pointing the dialog to that folder?

    I suspect that you might have to do that for every patch. The alternative is to edit the Registry directly for all the patches, in order to put in the new source path. Or maybe you could make the original source path available again if you are actually networked.

    ---------- Post added at 04:03 PM ---------- Previous post was at 02:52 PM ----------

    Quote Originally Posted by James View Post
    .... Or maybe you could make the original source path available again if you are actually networked.
    Please disregard that suggestion. It seems the Office Integrator doesn't fill in the "LastUsedSource" value in the Registry, so that won't work at all. (That's not a criticism of the Office Integrator, BTW. It makes sense not to, if everything has already been integrated.)

    .
    Last edited by James; 10-29-2010 at 08:09 AM. Reason: Corrected typo
    Follow Siginet's latest software venture on Facebook!
    Just click on the LIKE button on his new website here:

    www.ITTechware.com

  3. #3
    Join Date
    Apr 2009
    Posts
    1

    Default

    Do a search and I think you wll find it on your drive. Then browse to the location.
    Follow Siginet's latest software venture on Facebook!
    Just click on the LIKE button on his new website here:

    www.ITTechware.com

+ Reply to Thread

Similar Threads

  1. Error 2920 installing Office 2003 Pro
    By clarkg888 in forum Office Integrator
    Replies: 4
    Last Post: 01-30-2010, 12:29 AM
  2. Office 2003 Standard
    By galileo in forum Office Integrator
    Replies: 1
    Last Post: 04-08-2008, 08:31 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts