Issue 31080 - GetStorage, name:"No Content!
Summary: GetStorage, name:"No Content!
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1.1
Hardware: PC Linux, all
: P5 (lowest) Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-05 00:34 UTC by dilbot
Modified: 2005-01-14 14:06 UTC (History)
1 user (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 dilbot 2004-07-05 00:34:34 UTC
I got the following error popup message opening up OpenOffice:

>> Openoffice.org cannot be started due to an error in accessing the
   Openoffice.org configuration data.  Contact your system administrator.  The
   following internal error has occurred: GetStorage, name:"No Content!

Looking at past but reports, it looks like this was reported in 1.1.0, and then
marked as resolved.   I'm getting it in 1.1.1.

The problem was corruption of this file:
     ./user/registry/data/org/openoffice/Office/Common.xcu

The original file had been overwritten by gtk_widget code.  After removing this
file, and restarting, OOffice came up OK.

I am not sure what could have contributed to this happening.  I installed new
fonts on the day before the error came up, but nothing else out of the ordinary.

Cheers
Comment 1 mci 2004-07-08 10:32:29 UTC
Hi dilbot,

thanks for using and supporting OpenOffice.org...

please have a look at issue 23220

there you can find at least two comments which may be usefull in your case:
- Additional comments from rags Thu Feb 5 08:14:02 -0700 2004
     ==> hardware problem
- Additional comments from jb Wed Dec 17 04:21:20 -0700 2003
     ==> some steps you can try (written for an installation on windows but I'm
sure you can use this 
        description on Linux, too)

*** This issue has been marked as a duplicate of 23220 ***
Comment 2 dilbot 2004-07-08 17:25:01 UTC
Yes, I saw 23220 before I posted this bug report, and as I mentioned in my
original post this was for 1.1.0 and was marked resolved.

If you look at 23220, it was resolved because there was no response to a request
for additional information.   The symptoms were isolated (corrupted Common.xcu
file), but the cause was not determined in 23220.   There was some mention of
hardware problems in 23220, but this wasn't the case in 31080.

This problem is not fixed, and occurs in 1.1.1.  Marking 31080 as a duplicate of
23220 and having 23220 marked as closed will just mean that the problem isn't
addressed.  I'm going to reopen the issue since there needs to be a real
solution to this outstanding problem. 
Comment 3 remkou 2004-07-28 15:23:58 UTC
I experienced a similar problem. Im using OO 1.1.0 on a windows ME machine.
After using OO for some time it suddendly (for no apparent reason) didnt start.
It showed the following error message:
>> Openoffice.org cannot be started due to an error in accessing the
   Openoffice.org configuration data.  Contact your system administrator.  The
   following internal error has occurred: GetStorage, name:"No Content!

I resolved the problem by deleting:
./user/registry/data/org/openoffice/Office/Common.xcu

curiously I had to delete it twice. After deleing it the first time, OO stil
showed the same error message. After deleting the file again OO started up just
fine. 
Comment 4 roijmh 2004-08-06 20:24:51 UTC
I had the same error on an XP Home OS

greetz
Hans
Comment 5 roijmh 2004-08-06 20:36:28 UTC
Sorry the following is probably also helpful
Windows reports
Error occurredin
Appname soffice.exe
Appver 6.0.8784.500
ModName: Wrp645mi.dll
Modver 7.0.0.8784 offset 000428e

The deletion of common.xcu didn't help for me.

Greetz 
Hans

Comment 6 roijmh 2004-08-06 20:55:19 UTC
Removed OO and reinstalled
Everything back to normal.
Only thing that changed lately is de partition size.

Comment 7 thorsten.martens 2004-10-27 11:19:19 UTC
Looks like this one occured due to corrupted configuration data and is solved
after reinstall. Closed as worksforme due to being not reproducible in a recent
680 build.
Comment 8 mci 2005-01-14 14:06:04 UTC
.