Issue 51911 - OOo 1.1.5RC fails on multiuserinstall
Summary: OOo 1.1.5RC fails on multiuserinstall
Status: CLOSED DUPLICATE of issue 51836
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.5
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: OOo 1.1.5
Assignee: atr
QA Contact: issues@installation
URL:
Keywords: oooqa, regression
Depends on:
Blocks:
 
Reported: 2005-07-13 19:23 UTC by andreschnabel
Modified: 2005-07-14 07:04 UTC (History)
9 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description andreschnabel 2005-07-13 19:23:37 UTC
during release testing we found, that the current 1.1.5RD fails doing a correct
multiuser installation. At least a mutliuser installation becomes damaged on
first start of OOo.

Installation was done with following steps:
- unzip the the install package
- call setup -net
- do a user defined installation with all components selected. Installpath is
not the default, but my own.
- after this install is finisched, start setup.exe from the path where you just
instaled OOo
- choose worksation setup and leave defaults for all other settings
- after setup finishes, OOo is going to be started -> DOS Box with error message
"responsefile could not be found" appears

The same issue exists at least on linux. The error message is displayed right
after staring OOo from a console window.

Following other problems occured:

- userinstall can not be removed by starting setup a second time (there should
be options to repair or remove the workstation installation .. instead setup
asks for a new installation)

- the file instdb.inf (in the OOo user config path) is replaced by
instdb.inf.orig on first program start

- qatesttool fails to start OOo due to missing dll's
http://www.openoffice.org/nonav/issues/showattachment.cgi/27840/testtooldll_error.png

All current rc's seem to be affected.
Set Prio to P1, as automated testing is hindered significantly.
Comment 1 grsingleton 2005-07-13 19:55:22 UTC
added to cc
Comment 2 lohmaier 2005-07-13 20:04:45 UTC
setting keywords, target milestone. Without this resolved, there will be no 1.1.5

It doesn't depend on a custom installation path. The same happens with the
default one.
Comment 3 Olaf Felka 2005-07-13 21:32:57 UTC
reassigned
Comment 4 atr 2005-07-14 07:03:22 UTC
ATR: Duplicate to issue 51836.

*** This issue has been marked as a duplicate of 51836 ***
Comment 5 atr 2005-07-14 07:04:04 UTC
.