Issue 65126 - Basic-Error messages when saving documents
Summary: Basic-Error messages when saving documents
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.2
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: joerg.skottke
QA Contact: issues@sw
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2006-05-06 02:44 UTC by areweall
Modified: 2006-05-08 11:27 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description areweall 2006-05-06 02:44:03 UTC 
Error messages:

Error loading BASIC of document file:///c:/Documents%20and %20Settings/Areweall/
Application%20Data/OpenOffice.org2/user/basic/dialog.xlc/:
General Error
General input/output error

Error loading BASIC of document file:///c:/Documents%20and %20Settings/Areweall/
Application%20Data/OpenOffice.org2/user/basic/dialog.xli/:
General Error
General input/output error
Comment 1 Rainer Bielefeld 2006-05-06 09:06:58 UTC 
This might be DUP of issue 56914 or issue 59890, I can't decide.
WFM with "2.0.2  German version WIN XP: [680m5(Build9011)]"

@areweall:
You really tested with all OS?
You really only see that when saving a WRITER-Document?
Comment 2 michael.ruess 2006-05-08 09:52:07 UTC 
MRU->JSK: this came from a faulty config of OO 2.0,  didn't it?
Comment 3 joerg.skottke 2006-05-08 11:27:07 UTC 
Hi areweall,

this can happen when you migrate from a previous version of OOo (1.x series).
The office then tries to preserve some information from your old installation.
But as some information is stored with absolute paths you will run into this error.

Suggestion:
Back up your OOo 1.x and 2.x profiles, remove the userconfiguration and start
with a fresh config.

I close the issue as Invalid, this has been reported and discussed a number of
times. We cannot possibly fix this. 
If this still happens to you with a fresh configuration feel free to reopen the
issue (you can do this at any time). We will then investigate more thoroughly.
Comment 4 joerg.skottke 2006-05-08 11:27:20 UTC 
close