Apache OpenOffice (AOO) Bugzilla – Issue 12695
Starting soffice error: GetStorage, name: "No Content!
Last modified: 2003-12-17 10:56:59 UTC
Installation of OpenOffice.org 1.1Beta works as expected. Attempting to start OOo results in a dialog: OpenOffice.org 1.1Beta cannot be started due to an error in accessing the configuration data. Please contact your system administrator. The following internal error has occurred: GetStorage, name: "No Content! [ OK ] Attempts to start OOo with soffice, scalc, swriter, etc. results in the same error. Environment: - Linux Kernel 2.2.22 - XFree86 4.2.1 - IceWM 1.2.7 - glibc 2.3.1
I also see this. Same glibc, same xfree, kernel 2.4.19, enlightenment 0.16.5. I've also seen this in 644_m4 and 643 and has just put it down to some silly environment issue.
This appears to be a duplicate of issue 11777. By exporting STAR_OVERRIDE_DOMAINNAME=mydomain.com, OOo 1.1 Beta starts successfully. *** This issue has been marked as a duplicate of 11777 ***
This task in status 'resolved duplicated' and will be closed now. If you don't think, that this task is fixed when the referenced bug is fixed, please re-open this task. If the referenced task is not fixed, please wait until it is fixed. It make no sense to have all duplicated task open. Out of this reason this task will be closed now.
... closed
I reopen this issue, since it look like not yet solved with issue 11777 and it is not only with Unix but also with Windows xp. and still reported in OOo 1.1 I hope we can investigate this. Maybe this issue is related to all GetStorage problem. Issue 20003 Issue 18545 Issue 23251 Issue 23220 Issue 22253 Issue 23251 Issue 13404 Issue 21983 Issue 20705 and maybe others issue too. Please check, and thanks
of. CCed me. I don't see this as a P1 issue: it's not a general problem. Nobody has described a way to reproduce.
This issue was closed by the original submitter as duplicate to another issue. The fix (or workaround) for the original issue fixed the original problem. That problem occurred in a Beta version that is long past. utomo, how does the issue 'look not yet solved' with that fix ? You don't state where (and how) you can reproduce the exact same problem. Note that the 'Get Storage, name "No Content"' message may be triggered by a number of different failures in the configuration system. In most (but apparently not all) cases, it indicates a corrupt "Common.xcu" file. We can only fix each case as it occurs. If the same symptom occurs due to a different cause, that is a different bug. In the given case, the configuration failure apparently was connected to some problem with looking up the domainname. Unless you can reproduce this, don't reopen this bug. Marking as duplicate again. *** This issue has been marked as a duplicate of 11777 ***
And closing again
utomo > Jb: I reopen this, because in 11777 it say it is solved in 1.1. but if you look at my list of issue, there issue about getstorage which is reported in 1.1. Please check again to make sure. maybe you correct that getstorage error message is caused by other problem, but maybe somethings which we can track from list of issue I make. Thanks