Issue 116210 - Internal Error 2203 with special administrative installation
Summary: Internal Error 2203 with special administrative installation
Status: ACCEPTED
Alias: None
Product: Installation
Classification: Application
Component: ui (show other issues)
Version: OOo 3.3 RC8
Hardware: PC Windows XP
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-23 00:05 UTC by Regina Henschel
Modified: 2013-01-29 21:52 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Regina Henschel 2010-12-23 00:05:12 UTC 
Unpack the file OOo_3.3.0rc8_20101214_Win_x86_install_de.exe file to a folder,
for example to folder OOo33RC8.
Call setup.exe with parameter -a
Set the installation target folder to the same folder as the unpack folder, for
me again folder OOo33RC8.
Installation stops with error (German)

Interner Fehler 2203.
E:\SoftwareArchiv\OOoDownloads\OOo33RC9\openofficeorg33.msi, -2147287008

The installation work fine, if I set a different target folder.

It seems, that installing into the same folder produces this error. The
installation routine should check this and forbid to set the same folder as
installation target as the folder with the unpacked installation files.
Comment 1 Olaf Felka 2011-01-10 11:33:39 UTC 
@ is: Please have a look. Error 2203 stand for "Database:. Cannot open database
file. System error."
Comment 2 ingo.schmidt-rosbiegal 2011-01-10 16:52:00 UTC 
This problem is not surprising, because the msi database is located in the
directory, where the administrative installation is done. There are some small
changes during administrative installation in the msi database, but its name is
not changed (openofficeorg33.msi). So if you want to make the administrative
installation exactly into that directory, where the installation set is located,
you will get a conflicts. Of course a CustomAction could check, if the
installation is done into a different directory, but this is not really a
realistic scenario for an administrative installation.
Comment 3 Regina Henschel 2011-01-10 17:32:20 UTC 
It's the scenario of testing developer snapshots: Put all things together in one
folder and delete or archive it, when the next one is out.

I will not object, when you decide this as "wontfix". The error can be easily
worked around and people, who do administrative installations, should be able to
find reason and workaround here in Issuezilla.
Comment 4 ingo.schmidt-rosbiegal 2011-01-11 09:54:45 UTC 
Hm, not sure yet, if I set this task to "Wontfix". But the scenario of testing
developer builds is invalid, if it is recommended to make the administrative
installation directly into the installation set. This cannot work.