Office XP repair install

When I try and do a repair or reinstall or uninstall Office XP I get a prompt looking for this file ? "511691.vsdebugop.msp "

I tried a search for the file on google and am coming up empty handed.

Anybody know how to correct this?

Thanks
Rocket

 

I've tried doing a install from the cd and have steered it to the cd. Also have tried add / remove and repair from word (which works fine) but when I open Frontpage it wants to run the installer and asks for this file (511691.vsdebugop.msp) which I cannot find on the cd (officexp sp2 slipstreamed) or from a folder where I have extracted office xp sp3?

Thanks
Rockit

 

Can you uninstall the SP3 update, and then go from there?

 

I'm flying by the seat of my pants once again so please Rockit don't experiment with what I'm about to suggest. Wait for the really intelligent, cautious and experienced expert members (as opposed to myself on this issue) who can give advice and comments on the pitfalls and dangers of trying this as I'm not really familiar enough with all the dynamics to know what the results or dangers would be.

To all members
Theoretically speaking could the update as given here:
http://www.mail-archive.com/unattended-devel@lists.sourceforge.net/msg00133.html
be downloaded and extracted to a folder "name of choice" and the file vsdebugop.msp be renamed "511691.vsdebugop.msp ", Then any request for this file be directed to this folder? Am I just being a mad scientist about to blow up the Office...

 

Thanks
Finally got it to work by deleting all office folders and reg entries.

Rockit

 

Drats...Foiled again! (as evil mood music plays in the background).

No chance to blow up the Office you have bull dozed the project and rebuilt it.

Kidding aside, I'm glad you were able to figure this out and put this problem behind you. Thanks for the update.

 

goddez1,
I actually blew it up before I saw your post or I would have given your suggestion a try.

Thanks Allot
Rockit

Just so ya know Office XP had over 3,000 reg entries according to regseeker.

 

Same here

Got the same problem

When trying to do setup.exe
or add/remove of office (already
uninstalled..mostly except if you check show updates in
add/remove programs, there's still stuff there)

get this message
"Click OK to try again, or enter an alternate path to a
folder containing the installation package
'511691.VSDEBUGop.msp' in the box below.

I had installed all updates, SP3 and past, before I uninstalled
office, and wanted to reinstall it.

I tried the office update site Steve recommended. It failed
to update, but gave an important clue that pointed to a
microsoft problem...


http://support.microsoft.com/?kbid=251214


INFO: Windows Installer May Prompt for Install Source if Unavailable


SUMMARY
Microsoft Windows Installer may prompt for the original install source location during an uninstall or a modify operation the first time either option is chosen.

This prompt will occur if all of the following conditions are met:
• The original .msi package was installed with the 1.0 version of Windows Installer.
• Windows Installer was upgraded to version 1.1.
• The install source location is not available at the time of the uninstall or modify.


additionally

http://support.microsoft.com/kb/268800
FIX: Windows Installer Must Have Original Source Files When You Apply a Patch

SYMPTOMS
When you apply a patch for an existing program that was installed with the Windows Installer, you may be prompted for the source files from the original installation. You are prompted to provide the source files from the original disk even if they are not needed for the actual patch.
CAUSE
In most patching scenarios, the source will be necessary in order to reinstall necessary files. A patch uses the Windows Installer file versioning rules when deciding whether to reinstall a file contained in a feature that is being updated.

Being prompted for the source when no files are being reinstalled is due to a bug in the Windows Installer patching algorithm.


This behavior is caused by Windows Installer needing to recache the product's Installer package. The reason for the recaching is that Windows Installer has changed the registration of the cache location in order to track per user and per machine installations separately. Once the new package is cached, then the uninstall or modify operations should continue and complete successfully.

The cached packages that are used for maintenance mode operations are cached in the %windir%\Installer directory.

 

Solution: Fixed

I tried deleting registry entries and folders but that didn't fix things.
so I did a system restore to undo all those attempts...so I could
start from where I was hosed.

It's all about the installer cache, which is too hard to figure out.

This worked for me (found it at microsoft)

first I used add/remove programs to remove any office related
stuff that would uninstall (in my case, speech to text, html filter etc)

this left a microsoft office uninstall thing that wouldn't work (complains about the source installation)


I then used this tool to uninstall the rest of Office.
The link to the knowledgebase article is

http://support.microsoft.com/default.aspx?scid=kb;en-us;290301&Product=offxp


I first had to select
Microsoft Office Integration
as a thing to uninstall with this tool
then
Microsoft Office XP Professional with Frontpage
I also selected the
"Remove Hidden Data Tool"
that was something from Microsoft for Word.

Don't know if all 3 were important, or just the main
Microsoft Office XP Professional with Frontpage.

I was able to reinstall after this.

This kb article was hard to find at msoft...



Description of the Windows Installer CleanUp Utility
Article ID : 290301
Last Review : August 25, 2004
Revision : 1.0
This article was previously published under Q290301
Important Warning

The Windows Installer CleanUp Utility is provided "as is" to help resolve installation problems for programs that use Microsoft Windows Installer. If you use this utility, you may have to reinstall other programs. Caution is advised.

SUMMARY
Microsoft has updated the Windows Installer CleanUp Utility. With the Windows Installer CleanUp Utility, you can remove a program's Windows Installer configuration information. You may want to remove the Windows Installer configuration information for your program if you experience installation (Setup) problems. For example, you may have to remove a program's Windows Installer configuration information if you have installation problems when you try to add (or remove) a component of your program that was not included when you first installed your program.

The Windows Installer CleanUp Utility does not:
• Remove Windows Installer.
• Remove files of any programs that are installed by Windows Installer, such as Microsoft Office 2003.
The Windows Installer CleanUp Utility does:
• Provide a dialog box where you can select one or more programs that were installed by Windows Installer. You select the programs on the Installed Products list in the Windows Installer CleanUp dialog box. After you make this selection, the utility removes only the Windows Installer configuration information that is related to those programs.
• Remove the files and registry settings that make up the Windows Installer configuration information for programs that you select.
If you use this utility to remove the Windows Installer configuration information for your program and you plan to reinstall the program, you should reinstall the program in the same folder where you originally installed it. This prevents duplication of files on your hard disk or disks.