Apache OpenOffice (AOO) Bugzilla – Issue 52426
Tries to uninstall previous version, fails, and will not install.
Last modified: 2006-02-20 08:00:42 UTC
The installer starts up and starts installing, but in the middle of installation, says that it cannot uninstall the previous version and fails to install.
After deleting all instances of openoffice from the registry and reinstalling windows installer a couple times, it seems to have fixed the problem.
*** Issue 52405 has been marked as a duplicate of this issue. ***
I've tried to install OOo 1.1.8 beside OOo 1.1.6 -> no problem I've tried to install OOo 1.1.8 over OOo 1.1.6 (wich doesn't make sense in a developer version!) -> no problem As you have written, cleaning up the registry helps out. Maybe that this tool will help also: http://support.microsoft.com/kb/290301/en
Not reproducible.
reopened for reassigning
of: The current version is uninstalling a previous version. That's a new behavior. We shouldn't do this without a warning. @ xxjack12xx: Sorry, I should have had a deeper look.
reassign
Why reassign? This task needs to be clarified together with 123962 (also yours :-) ) . Which is the desired update behaviour for OOo (Windows) ? On the Unixes we replace old versions with the new versions. For example openofficeorg-core01-1.9.122-1.i586.rpm replaces an existing older version of this package. With the new process, the mechanism on the Windows platform is similar.
cc'ing
*** Issue 52697 has been marked as a duplicate of this issue. ***
One comment for clarity - the issue is that in the windows world, if the uninstall fails (thank windows?), then the user can't finish the install (easily) and may not be able to use the old (that was my situation). I don't know what the OO / Windows UI philosophy is, concerning fixing MS cleaniless issues, but it was openoffice spoor that stops the installation. IMHO, it would solve help issues before they occur if there is an override to overinstall. I like to think this would allow "my mom" to re-install. BTW, the the suggested MS Tool pointed to by the knowledge base article suggested above worked for me (I'm not stuck inbetwixt anymore): http://support.microsoft.com/kb/290301/en
sorry for the traffic, but forgot to add, it showed up as OpenOffice error # 1714 before I removed the old OpenOffice entry with the MS tool. And I had to remove 1.9.100 (after running & uninstalling 1.9.104 - I don't know how I/we got there)
I'm not sure what I'm seeing is the same issue, but I didn't want to open a dup without checking first... since 680m118, if I attempt to install the new beta versions over the top of the previous beta version (user only install, not all users...haven't tried that), the install seems to be successful (i.e. no errors are reported, a new program group shows up in the start menu, etc.), but things do not work properly (e.g. executing anything in that program group doesn't work, file associations are lost, etc.). Running the installation again offers me the chance to "repair" the installation, which completes fine and resolves all of the issues.
@is: yes, we agreed to uninstall the old version and than to install the new version. but what if, as described the uninstall fails and the result that there is no usable installation at all. what is the proposed way out ?
There is no proposed way out. It must not happen, that the deinstallation fails. But this is part of the Windows Installer. We can only offer tooling that cleans the Windows regisry after a failed deinstallation.
Setting new target ( for the creation of such tooling ? )
That tool is ready: http://support.microsoft.com/kb/290301/en
You are absolutely right. Microsoft supports the "Windows Installer Clean Up Tool" for such problems. If this is sufficient for our problems, we can close this task.
@xxjack12xx: Sending back to you for closing. Or do you see another solution than using the tooling already supported by Microsoft?
Somebody on the Windows installer team has posted some information that may help in tracking down some of the Windows installer issues: http://blogs.msdn.com/windows_installer_team/archive/2005/10/04/477098.aspx
xxjack12xx: what is the status of this issue? Can we close it?
xxjack12xx: no answer -> I'm closing this issue as WONTFIX. The problem seems to be solvable using tool provided by Microsoft. if it is not, please feel free to reopen the issue to bring it to OOo developers attention.
Closing.