Apache OpenOffice (AOO) Bugzilla – Issue 5748
OOo 1.0.0 writer won't start anymore: "unrecoverable error" during load
Last modified: 2003-09-08 16:56:16 UTC
Yesterday the problem occured for the first time, after I used OpenOffice.org 1.0.0 for quite some time now without experiencing any problems. Upon start of the OOo writer, the splash screen pops up, and shortly after that a message window says: "An unrecoverable error has occured. All modified files have been saved and can probably be recovered at program restart." When I click the OK button, Win2k informs me that the application has caused an error and that an error log will be created. This is 100% reproducable. Opening an existing document with a double click allows me to start the application without any problems, by the way. Up to now I only work with the writer application, so it is hard for me to tell anything about the other applications. I tried it with the presentation application, which showed up the same message, after guiding me through the "new document" assistant. I tried to reinstall OOo several times, which did not help at all. The error remains the same. Besides the german version (which I normally use) I tried installation of the english version, but the problem is still there. The installation has been done in the following way: - removing of the old installation (using the setup tool, without deleting configuration files and files that have been created by me) - reboot - starting setup, choosing "custom installation", removing the following components: "Quickstarter", "Java Environment Installation", "English (US) Language Module", choosing my primary NTFS partition for installation, "install". - reboot - starting the "writer" application - cursing around a bit because of seeing the same error again :) There is only one thing I changed in my local configuration: I made an update to the Audiogalaxy satellite client to the current version 0.609w. Nothing else has been changed since the last usage of OpenOffice.org. My setup is the following: - Windows 2000 Professional, German Version, Service Pack 2 (5.00.2195) - Athlon 900 in Asus A7V-133 - 256 MB Ram - 40 GB Samsung hdd (SV4002H), connected to the ATA-100 controller of the board - installation of OOo on primary NTFS partition (33.3 GB) If you need additional information, please let me know.
Now even opening an existing document does not work any longer. :( I tried to use the 641d-build, which also ended up in the "an unrecoverable error occured" message. I'm getting into serious time problems now, because I started writing some business documents with OOo 1.0.0 which I have to finish during the next days. Restarting them will take up a whole lot more time, though. Now I think about "cheating" with Staroffice 6.0 beta, by setting up the wrong system date. But this is no real solution I can live with. So, if anyone could give a comment on this bug report (some hints, for example, which things I could try out) I would be very happy.
As additional information: I installed StarOffice 6.0 beta (tuned my system clock back one year). When I tried to start SO6 it gave the same error message as I know from OOo: unrecoverable error occured. :((
Michael, thank you for using and supporting OOo. I'm sorry no one has touch this case since you posted it. Have you found a resolution to this issue?
I'm sorry, too, as I didn't close this bug yet. Yes, I have found a solution. It was a problem with my hdd. It was slowly adding defective sectors, and magically the new installed programs were using those sectors. I guess that's another Murphy's... after exchanging the hdd for a new (and bigger ;) ) one now everything works perfectly. The problem never occured again. I'm not sure about the desired status for closing this bug... is it "invalid", or "fixed"? Therefor I leaving it open again, could you close it please with the correct resolution?
User had a bad HD.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.