Issue 113494 - postgresql-sdbc-076a driver cause OOo to not start
Summary: postgresql-sdbc-076a driver cause OOo to not start
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO330m1
Hardware: Unknown Windows 7
: P3 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: AOO issues mailing list
QA Contact:
: 128092 (view as issue list)
Depends on:
Reported: 2010-07-28 13:21 UTC by r4zoli
Modified: 2019-04-16 07:55 UTC (History)
8 users (show)

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

installation error (34.81 KB, image/png)
2010-07-28 14:02 UTC, r4zoli
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description r4zoli 2010-07-28 13:21:43 UTC
OOO330_m2 problem, can not set in versions.

I installed OOO330_m2, into separate (parallel to  OOo 3.2.1, and DEV300_m85)
folder(C:\Program Files\OOO330\) with russian langpack.

Added some extensions as administrator for all users, mysql native driver 1.0.1
(from qa-upload)- without problem,
postgresql 076a (from page)- some cache error message, but later 
And hu_HU dictionary- without problems.

Restarted OOo as normal user.

Changed UI language to Russian tested with database odb files, connected to
external servers, to find a missing translations. 
Restarted OOo.
Tested connections, and other dba issues.
When finished changed back UI settings to English (USA), closed OOo.

When I tried to start OOo I get error: 
The application cannot be started. A general error occurred while accessing your
central configuration.
Comment 1 r4zoli 2010-07-28 14:01:47 UTC
I figured out if I delete user profile OOo starts.
The postgresql-sdbc-076a driver cause OOo to not start. 

It is independent from language settings.

When installed with extension manager for all user, or current user, get error
message attached as screen shot.

If you close OOo, try to restart OOo I get error: 
The application cannot be started. A general error occurred while accessing your
central configuration.

I don't know who is responsible for it.
Comment 2 r4zoli 2010-07-28 14:02:57 UTC
Created attachment 70861 [details]
installation error
Comment 3 marc.neumann 2010-07-28 14:22:07 UTC

please have a look.

bye Marc
Comment 4 Olaf Felka 2010-08-02 10:31:47 UTC
How to proceed since jbu isn't reacting on this issue?
Comment 5 joergbudi 2010-08-03 20:07:04 UTC
Please retry with, 

I have removed the DataAccess.xcu, which was only there to support OOo 3.1 and
earlier builds. In 3.2, a new configuration scheme for sdbc drivers was
introduced (postgresql.xcu), however the older file didn't do any harm, this
seems to change with the current builds.

When this works, I will change the drivers homepage accordingly.



I won't be able to support the driver in the next  years anymore, simply no
spare time left anymore, that's why it took so long ...
Comment 6 r4zoli 2010-08-04 14:04:39 UTC
I tested the, and can install it without any further
I think the issue fixed.
Comment 7 Olaf Felka 2010-08-04 14:10:15 UTC
Thanks for fixing and testing!
Comment 8 joergbudi 2010-08-12 20:33:17 UTC
updated drivers homepage 
Comment 9 rene 2010-11-15 15:19:21 UTC
jbu: but you didn't commit it. did you? I only see 0.7.6a tagged. How should
people packaging this then get the identical source code to what your version
gets from (I can remove all the DataAccess pieces myself, but...)

As long as it's only somewhere else, it's not fixed *in the tree*. Reopen.
Comment 10 rene 2010-11-15 15:30:29 UTC
(and before you say that it is not in the tree - if it should be do then you
need to update your docs on how to get the source code and build it.

(I now assumed
Comment 11 ftoth 2011-05-17 22:32:42 UTC
It is great that it installs, but does it work?

I am not able to add /edit records using this driver either directly in a table or through a form.

The add record icon in the record selector is disabled, and changing an existing record is just not possible.

Note that using the jdbc driver I can edit/add records, our postgres server is running unchanged for over 2 years.

Note, this problem occurs with OO 3.3 (from OO downloads on linux x32), LO 3.3 ( amd64, x32) and LO winxp.

The driver 0.7.6a with OO 3.2.1 and LO 3.2.1 works fine.

This is pretty bad because the alternative jdbc is pretty slow or even d*mned slow depending on the java version used (this is no exaggeration, I mean retrieving 10 records per second using SUN jre 1.6.24. Don't believe me? Try it!).

Please, pretty please fix this, we do use this for serious stuff (billing).

Comment 12 Rob Weir 2013-07-30 02:41:23 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.
Comment 13 oooforum (fr) 2019-04-16 07:43:51 UTC
*** Issue 128092 has been marked as a duplicate of this issue. ***