Hi G. Roderick, Dagmar,
I am using open office org 1.1 with windows nt
All of a sudden I get the following anouncement of fault concerning open office: GetStorage, name: "No Content!"
What do I have to do?
Thank you for your help
Dagmar Ambass
You can a solution in multiple places. 1. http://documentation.openoffice.org/faqs/index.html 2. http://tinyurl.com/5u8bt 3. http://tinyurl.com/5u8bt 4. http://www.oooforum.org/forum/viewtopic.php?t=3938 are just a few. The issue is http://qa.openoffice.org/issues/show_bug.cgi?id=34359 Please vote for it or add information so we can get this fixed.
If I may just say, there's not much point in voting for the issue. Trust me, this problem is taken very seriously, unfortunately the difficulty in its reproduction has prevented us from finding its root cause. It has however prompted a review of the configuration management in the 2.0 version so that such corruptions, whether caused by a fault in the program (as seems to be the case in this situation) or external causes, do not result in the application being unusable (though the loss of configuration data will not be avoided).
It can however be very useful if you can provide additional information (if you have any) regarding the environment surrounding the occurrence of the problem. As mentioned, our biggest problem is in reproducing it, even though the frequency of reports lead us to believe there must be some kind of specific trigger.
Regards,
Cyrille
Here's what I don't understand (among many things, unfortunately):
My take on this is that common.xcu is used to primarily to hold a user's configuration from one sesssion to the next -- correct? Things like the options one would set, the list of recently opened files, where toobars are docked, etc.
My other understanding is that this problem occurs when restarting after the program or operating system crashes.
Is the file being kept open during the user session? If so, why is that necessary?
Wouldn't it be sufficient to open the file, read in the configuration, and then close it again? Then open it and write the config during a normal shut-down?
This would seem to be a simple way of avoiding the file corruption. If the program or system crashes, you would lose any changes that would otherwise be written to the file, but hell, you do anyway. At least you would still have what you started with before that session. As it is, you have to start from scratch.
I'm probably just speaking out of turn here, but does it really matter to track down specifically what's happening? Just make it so the file can't get corrupted -- at least not as easily -- and leave it at that.
Rod
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
