NoOp wrote:
On 07/06/2007 05:29 PM, Manfred J. Krause wrote:
Hi,
Charles Burnell wrote:
Dear Mr. Fuchs,
I tried the solutions you suggested without success. Since my computer
does not seem to have a file named "openofficeorg20.msi" is there a way
to work around this? Thank you for your help with this problem.
Please, have a try with 'Windows Installer CleanUp Utility' ->
http://support.microsoft.com/?scid=kb%3Ben-us%3B290301&x=13&y=10
to get rid of
"error 1714 -
The older version of OpenOffice.org2.2 cannot be removed."
[Are you sure, it was 'OpenOffice.org 2.2'?
Isn't it 'OpenOffice.org 2.0'?].
After having removed the Windows Installer database entry of old
version 2.0.3, the installation of version 2.2 should work.
... and:
If none of the above helps, come back here
and we'll have another think.
Manfred
This seems to be a common occurence with 2.2x. The solution tends to be
to point the user to a registry cleaner (I prefer CCleaner for Windows)
to fix the problem. Could it be that OOo simply has a bug in that it is
not cleaning up the old install properly? Searching for
"openofficeorg20.msi" in
http://www.openoffice.org/issues/show_bug.cgi?id=73847 and a few others
dated 2006 and 2005 and 73847 suggests using
http://support.microsoft.com/kb/290301/EN-US/
However, that should not be necessary and OOo should clean itself up
properly.
Perhaps more windows install testing needs to be conducted on install
errors such as this so that this list doesn't keep getting the failure
to install queries as often. If a install test & 'burn-in' and/or
smoketest (similar to Mozilla) project with proper scripts etc were
readily available perhaps those of us with no life would be willing to
test and report our findings... :-)
There does seem to be a developers smoketest:
http://wiki.services.openoffice.org/wiki/SmokeTest
but nothing that I could find for 'users'.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
this is surely not a common occurance of any OOo version. This is a
problem of the Micrsoft Installer used by OOo. And the problem might be
that a newer OOo 2.x wants to update an older OOo 2.x version. So it
might be a solution that OOo doesn't update anylonger. But at last it
doesn't really solve the problem: If the user chooses to uninstall he'll
get the same error message.
If a user deletes OOo without using the system tools he is on his own risk.
And no, OOo is not registry cleaner. That is not the job of an Installer
(especially not the MSI) to clean up the registry of old and propably
unused keys.
Groetjes,
Olad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
