Issue 10458 - OpenOffice has ceased working after a couple of other application installs
Summary: OpenOffice has ceased working after a couple of other application installs
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-05 00:12 UTC by Unknown
Modified: 2003-02-13 15:07 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 Unknown 2003-01-05 00:12:59 UTC 
In the last 2 days, OpenOffice stopped working for me.

The only differences in my computer that I can recall since it last worked are 
that I installed a music program called 'MUSICMATCH Jukebox 7.50.1026' and I 
applied several recent windows 2000 updates to my system (I could not list what 
I installed unfortunately, but they were the several most recent updates). 
Repairing the application does not work, nor does re-installing it. 

The symptoms are that on starting up OpenOffice the following gets put in the 
windows applciation log

Event Type:	Information
Event Source:	Application Popup
Event Category:	None
Event ID:	26
Date:		04/01/2003
Time:		23:11:01
User:		N/A
Computer:	SETHHOME
Description:
Application popup: soffice.exe - Application Error : The exception unknown 
software exception (0xe06d7363) occurred in the application at location 
0x77eab2f0.
 

the last paragraph of this appearring as a popup
Comment 1 thorsten.martens 2003-02-05 15:18:22 UTC 
Problem wasn´t as easy reproducible as described here when using a OO
1.0.2. running under Win2000. We need more Infos about how to let this
bug occur. Like installation type (Net/Workstation or single user,
standard, custom or minimal), who did the installation (Administrator
or user), who tries to work with the office (Administrator or user), etc.
A Dr.Watson debug output or a stacktrace would be very helpful !!!
Comment 2 thorsten.martens 2003-02-13 14:09:23 UTC 
Due to the fact, that this problem wasn´t reproducible when using a
1.0.2. and missing further information about which steps led to those
misbehaviour, this issue is set to "worksforme".
Comment 3 thorsten.martens 2003-02-13 15:07:41 UTC 
.