Issue 6212 - Saving sxw document under XP crashes and deletes file (Access denied, object not accessible, insufficient user rights)
Summary: Saving sxw document under XP crashes and deletes file (Access denied, object ...
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.0.0
Hardware: PC Windows XP
: P2 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-06-28 23:55 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
sxw file saved with OO 642, causes crash when trying to save modification with OO 1.0 under Windows XP (78.97 KB, application/octet-stream)
2002-06-28 23:59 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-06-28 23:55:49 UTC
Windows XP (NT 5.1 Build: 2600)
User X in groups "Administrators + Users"
Common "network" installation as user X
Workstation installation as user X
Installation works fine, no errors, programs can be started
Open bar.sxw document, which was originally saved with OO642
Modify bar.sxw and press "save" button
->
"Error saving the document bar.sxw:
 Access to C:\foo\bar.sxw was denied"
[ no reason why this should not work, write permissions OK ]
->
"Error saving the document bar.sxw:
 Object not accessible.
 The object cannot be accessed
 due to insufficient user rights."
->
Then OO hangs and Windows XP offers to send a report to MS.

Strange: Sometimes I can save a first change to the document
and only the second attempt to save will cause the crash.
When the crash occurs the ORIGINAL DOCUMENT IS GONE! This is
not a desirable behaviour.
Comment 1 Unknown 2002-06-28 23:59:19 UTC
Created attachment 2109 [details]
sxw file saved with OO 642, causes crash when trying to save modification with OO 1.0 under Windows XP
Comment 2 Unknown 2002-06-30 09:22:55 UTC
Mysterious: I had a similar problem under Windows 2000 (most recent
patches). "Common" installation as Administrator then workstation
installation as user X.
Trying to save a *.sxw document as user X caused Writer to crash with
some privilege problem. I played around with this to write a bug
report and then the error stopped. I don't see that I have changed
anything relevant, the only special thing I did was to run Writer as
Administrator repeatedly (where I could not reproduce the error). Then
I logged back in as user X and the error had gone there, too. Can it
be that some "initialization" work is required when OpenOffice runs
first and that this has to be done as Administrator?

Remark: I tried the documents in question under Linux (workstation
installation, non-root user) and they worked fine from the start. So
this does not look like a problem in the format of the documents.
Seems to be some privilege-related issue one Windows NT machines.

Issue 5692 could be related to this one.
Comment 3 Unknown 2002-07-09 12:22:02 UTC
Tools, Options..., Paths, Temporary files
 is set to:
C:\DOCUME~1\rmx\LOCALS~1\Temp

This directory exists and I can read/write to it. Looks OK. I removed
all content from that temporary directory and tried again. Here is
what happens:

- Open document "Java Summary.sxw" and insert a blank somewhere.
- Press "save" icon.
  -> Error saving the document Java Summary.sxw:
     Access to C:\KAPPERT\NEW_FILES\Java Summary.sxw was denied.
- Click OK
  -> Error saving the document Java Summary.sxw:
     Object not accessible.
     The object cannot be accessed
     due to insufficient user rights.
- Click OK
  -> MS "Send Error Report" box appears and OpenOffice is terminated.
- After this I have two empty (nested) subdirectories in the
  "Temporary files":
  C:\DOCUME~1\rmx\LOCALS~1\Temp\soffice.tmp\sv1ai.tmp
- The original file is lost and unfortunately no copy can be found in
  the "Temporary files".

Comment 4 Unknown 2002-07-09 12:40:01 UTC
I did a workstation installation for the real Windows "Administrator"
and could reproduce the same error as Administrator. It is strange
that you get permission problems as the unrestricted Administrator
when accessing the local disk.

I had a somewhat similar problem under Windows 2000 Pro, which seemed
to solve when I worked as Administrator (or it was some coincidental
change of the configuration which happened at the same time).
Anyway, on Windows XP the problem is different and does not go away as
user Administrator.
Comment 5 Unknown 2002-07-10 12:17:54 UTC
I removed all workstation installations from my XP machine and deleted
the common directory C:\Program Files\OpenOffice.org1.0 (is there an
uninstall?).

Then I removed some suspicious registry entries "OpenOffice" and
"soffice".

Then I did a new "/net" install, this time as Windows "Administrator"
followed by a workstation install, again as "Administrator".

I am sorry to say that the same error persists after installation as
Administrator and when using the application as Administrator.

Can anybody reproduce this problem on Windows XP? I don't think there
is anything special with my installation. XP came pre-installed on a
Compaq Evo D300.

What is strange is that sometimes I can save on the first attempt and
only the second or third one fails. Something rather fishy must be
going on behind the scenes here... maybe related to Windows rather
than OpenOffice itself.
Comment 6 Unknown 2002-07-18 18:54:50 UTC
I start to doubt that this is an installation issue. Could it have
something do with fonts?
If somebody has access to a regular OpenOffice installation on XP I
would appreciate the following experiment:

Open the document that I have provided earlier (Java Summary).
Open/create an empty new document.
Copy/paste the content of my document into the fresh, new document
(without table of contents).
Save the new document.
Try small editing changes in the new document.

When I did the above I could reproduce the crash with the new
document. Other documents on the other hand work fine. This looks
(strange enough) like it has something to do with the content. Note
that this document was migrated from MS Word earlier on and that it
might contain strange constructs (I had some problems with MS Word,
kept doing strange things for simple tasks like different fonts in a
bulleted list).
Comment 7 prgmgr 2002-09-09 02:13:56 UTC
Beat, thanks for all your time and effort with this issue.

Note to reviewers, the "Java Summaries.sxw" file is the 
attached "bar.sxw" file.

Beat, I tried the following:

1.  Open bar.sxw
2.  Copy contents of bar.sxw, without the table of contents.
3.  Paste into a new OOo text doc.
4.  Save the new OOo text doc.
5.  Edit and save the new OOo text doc.

I repeated step 5 several times and OOo did not crash.


Do you have any error logs we can take a look at?

Unable to duplicate on Win NT 4.0 SP6a, OOo 1.0.1.


Thank you for using and supporting OOo.
Comment 8 Unknown 2002-09-18 19:25:50 UTC
Thanks for trying it out!

> Unable to duplicate on Win NT 4.0 SP6a, OOo 1.0.1.

So you tried with NT 4 only, not with XP?

I can use that document under Windows 2000, problems are only with XP
(at work). Linux is fine as well.

When I have more time I will download the most recent OpenOffice and
give it another try. XP has had several updates in the meantime as
well. If nobody else complains about similar problems then this issue
can be safely ignored for the moment.
Comment 9 Unknown 2002-11-14 22:09:08 UTC
I finally got around to update Windows XP to the latest and greatest
patches (SP 1 and more, don't ask me for details... just everything
that was available on November 12 2002).

I removed everything detectable of my old OpenOffice 1.0 installation,
including sversion.ini and user60.rdb. I also cleaned the registry
from "OpenOffice" entries. I don't think this really made a
difference, I just mention it for the records.

Then I installed my newly downloaded OpenOffice 1.0.1 as Administrator
(/net), followed by a workstation installation as a regular user. I
could not reproduce the bug anymore and everything looks OK now.

So I am closing this issue.

Keep up the good work! OO rocks!
Comment 10 eric.savary 2003-04-19 23:01:39 UTC
closed