incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver-Rainer Wittmann <>
Subject Re: AW: AW: Unable to install AOO on a clean Windows XP
Date Thu, 01 Mar 2012 11:40:00 GMT

On 01.03.2012 10:46, Hans Zybura wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: Oliver-Rainer Wittmann []
>> Gesendet: Mittwoch, 29. Februar 2012 16:56
>> An:
>> Betreff: Re: AW: Unable to install AOO on a clean Windows XP
>> Hi,
>> On 29.02.2012 15:56, Hans Zybura wrote:
>>>> Von: Ariel Constenla-Haile
>>>> Gesendet: Mittwoch, 29. Februar 2012 11:19 On Wed, Feb 29, 2012 at
>>>> 08:50:31AM +0100, Jürgen Schmidt wrote:
>>>>> On 2/28/12 8:30 PM, Hans Zybura wrote:
>>>>>> Like Oliver, I tried the same file now
>>>> Rev.1293550/win32/OOo_3.4.
>>>>>> 0_Win_x
>>>>>> 86_install_en-US.exe
>>>>>> on a clean English win xp professional sp3 vm and I'm still getting
>>>>>> "Error: An error occurred during registration of extensions!" at
>>>>>> the end of the installation process.
>>>>>> Both with installation option "install for all users" and "only for
>>> me".
>>>>>> With the error message still open, i.e. installation not rolled
>>>>>> back yet, there are no files in standard path
>>>>>> C:\Program Files\ 3\share\extensions
>>>>>> except for "package.txt"
>>>>> It is really strange, I had the chance to install it on a Win XP box
>>>>> with SP3 and where no office was installed before.
>>>>> Everything works as expected ...
>>>>> We need somebody with Win XP and a debugger and who is able to
>>>>> create at least a stacktrace
>>>> not that I'm taking the task here (I'm not building on Win right
>>>> now), but
>>> I
>>>> wonder how do you debug this? Do you have to attach the msiexec, the
>>>> installer, ...?
>>>> Google found some pointers:
>> windows-
>>>> installer-msi-using-visual-studio-2005.aspx
>>>> 793.aspx
>>> 1. I created an msi log file on the clean winxp sp3 vm, where the
>>> problem exists. I will send it via personal email if someone asks for
>>> it. And of course I can do it again, if need be.
>>> The last 3 lines before the error is thrown are:
>>> [HZ_1:] MSI (s) (44:04) [13:02:50:677]: Executing op:
>>> ActionStart(Name=RegisterExtensions,,)
>>> [HZ_2:] Action 13:02:50: RegisterExtensions.
>>> [HZ_3:] MSI (s) (44:04) [13:02:50:677]: Executing op:
>> CustomActionSchedule(Action=RegisterExtensions,ActionType=1025,Source
>> =
>>> Binary Data,Target=RegisterExtensions,CustomActionData=C:\Program
>>> Files\ 3\)
>>> 2. In the log file, I noticed the following lines:
>>> Property(C): DOTNET_SUFFICIENT = 0
>>> I took that as a hint and installed .Net Framework 2.0. This did NOT
>>> solve the problem, though.
>>> Side note: If .NET 2.0 really is required, than you should keep in
>>> mind, that .Net is not originally part of Win XP, any Service Pack, or
>>> standard security update. So it should either be part of the
>>> installation packet or not required. Developers using Visual Studio
>>> tend to forget that, because .Net is part of a Visual Studio
> installation.
>> .NET 2.0 should not be required from my point of view.
>> Currently, we have a couple of installations that worked on specific clean
>> Windows XP environments and a couple of installations that did not work.
>> BTW, do we already have an issue for this.
>> If not I am asking to submit one in order to have all information about
> this in
>> one place.
>> This issue should be also the right place to attach a such a created msi
> log file
>> from my point of view.
>> Best regards, Oliver.
> [HZ] Issue: see
> Please confirm. I could confirm it myself, because it happens on different
> clean machines, but still!
> Hans

Thx for submitted the issue to Bugzilla.

I tried to summarize some information about this defect - see my comment on this 
issue [1].

I am asking for some more information about the system on which the defect 
occurs and on which not. This will hopefully help us to find the root cause.

Thx in advance, Oliver.

--- Comment #4 from Oliver-Rainer Wittmann <> 
2012-03-01 11:34:21 UTC ---
Some summary from the mailing list:
- Raphael Bircher reported the issue on the mailing list and can still confirm
this issue.
-- system info: clean Win XP
- Rory O'Farell can not confirm this issue.
-- system info: clean Win XP SP2
- Oliver Brinzing can not confirm this issue.
-- system info: Win XP 32bit VM
- Jürgen Schmidt can not confirm this issue.
-- system info: Win XP SP3
- Olaf Felka can not confirm this issue.
-- system info: Win XP
- lou ql can not confirm this issue.
-- system info: Win XP
- Hans Zybura can confirm this issue and also submitted it to Bugzilla - Thx.
-- system info: English and German Win XP Pro SP3 VM

Thus, we have a strange situation:
On same Windows XP environments the defect occurs and on same not.

I am asking the people, esp. the ones above, to provide more information about
their system, if not already done - language, SPs, ... in order to find out
under which conditions the defect occurs. Otherwise it would be hard to fix it,
because it looks like that currently no developer could reproduce the defect.

View raw message