Issue 2458 - Crash when trying to access LDAP Address book
Summary: Crash when trying to access LDAP Address book
Status: CLOSED OBSOLETE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 641
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks: 17159
  Show dependency tree
 
Reported: 2001-12-06 10:05 UTC by osavill
Modified: 2018-08-13 15:22 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description osavill 2001-12-06 10:05:40 UTC
Sorry if this has come through to the wrong department !

Set up the "Data Sources" so that LDAP 
tab has entries for an M$ Exchange server.

From the "Main Toolbar" select "Data Sources".
A 
dialog appears asking for the Addresses password.
Enter the password and press <RETURN>
   OO 
save sthe document and produces the "Something really horid has happened, but you'll probably 
be able to recover" dialog and dies ! No further information and no core dumps !
Comment 1 hennes.rohling 2001-12-06 18:28:03 UTC
I'm sorry but I don't understand what you're doing.
Comment 2 osavill 2001-12-06 18:41:35 UTC
It appears that some of our internal documents attempt to access details from the 
Address book from the companies Exhange server. By setting up the LDAP connection 
to point at the Exchange server it should be possible to access this information. 
The Data Sources LDAP tab has an Addresses entry. I have told this to look at 
EXCHANGE1/Owen Savill/osavill which is the access string (according to IT 
support !). Now when OO comes accross one of these fields it prompts for a password. 
Alternatively go to the Data Source button in the Main Toolbar, press it and duble 
click on the LDPA branch. I enter the password and OO says Accessing the LDAP 
Directory. As soon as this dissappears OO wil produce the Unrecoverable Error 
dialog and shutsdown. Beyond this I can tell you no more !
Comment 3 dirk.grobler 2001-12-11 17:25:52 UTC
Is that related to the current exchange problems we have, Frank?
Comment 4 Frank Schönheit 2002-01-10 13:15:26 UTC
Owen,

we definately had problems with accessing MS Exchange server addresses. This problem is known, and it is not completely 
fixed.
I don't know if your problem has the same reason (at the moment, I can't reproduce this, as I have no MS exchange server 
configured to act as LDAP server), but to me it sounds this way.

We fixed some problems in the MSE area (there was also a GPF which is fixed), but the problem is not really solved yet. A 
solution is to be found/implemented in mozilla (actually, OOo uses mozilla components to provide the address book 
functionallity), and there it is still pending (but the people are aware of the problem: 
http://bugzilla.mozilla.org/show_bug.cgi?id=111968).

So all we can do at the moment is waiting for the mozilla people ...

Frank
Comment 5 Frank Schönheit 2002-12-19 14:34:43 UTC
lost this from the radar a little bit ...
Owen, do you have a chance to check this with the latest 643 build?
Comment 6 Frank Schönheit 2003-01-28 15:08:46 UTC
Owen? Any chance to check this in a recent build?
Comment 7 osavill 2003-01-28 15:43:21 UTC
OOo 1.0.2 dies with the following output:
/opt/OpenOffice.org1.0.2/program/soffice.bin: relocation error:
/opt/OpenOffice.org1.0.2/program/libsvx641li.so: symbol
_ZN13FmGridControl6commitEv, version UDK_3_0_0 not defined in file
libcppuhelper3gcc3.so with link time reference
Comment 8 Frank Schönheit 2003-03-05 08:56:35 UTC
Owen, the "relocation error" is described in issue 11706. We'll have
to look for this separately.
Do you have a chance to verify this in the 644 build?
Comment 9 Frank Schönheit 2003-03-06 15:53:22 UTC
forced to set a target - as long is this is not reproducible, I'll use
"Later"
Comment 10 dankegel 2003-05-15 08:22:39 UTC
As Frank says, this is said to be a glibc bug.  
See issue 10210 and issue 11706.  
What version of glibc are you using?  
Also, does running openoffice with the command
  
  env LD_BIND_NOW=yes ooffice

help?
Comment 11 Frank Schönheit 2003-07-15 15:31:07 UTC
mass re-assign of address book integration bugs
Comment 12 Frank Schönheit 2003-12-05 14:18:52 UTC
responsibilities changed
Comment 13 hans_werner67 2004-02-02 12:52:22 UTC
change subcomponent to 'none'
Comment 14 wind.li 2004-02-10 06:11:06 UTC
Migrate to a new account for security reasons.
Comment 15 Frank Schönheit 2004-02-19 11:28:11 UTC
osavill, please give feedback whether this bug still happens for you.
Else, we'll close the issue as INVALID.
Comment 16 osavill 2004-05-26 12:10:55 UTC
Sorry about the delay, hadn't noticed you were trying to raise me. The  
situation is that I was made redundant from the company where I had noticed  
this problem. I no longer have access to an Exchange server, and even if I did  
I could not replicate the companies setup. So sadly I don't think I will be  
able to give any more help on this one.   
  
It does look like the actual crash was due to the "relocation" problems.  
  
As a feature integration with Exchange would definitely be a bonus. Are you  
still waiting on Mozilla ? The problems of accessing with the M$ proprietary  
username and password protocol have been addressed separately, can't remember  
who by now, but I used to use it after I had given up waiting for Mozilla !  
This whole issue has turned into a gigantic flame war on the Mozilla Bugzilla  
site, last time I looked anyway. The Evolution guys solved this by going the  
HTTP route which is designed to be used for Exchange's web page interface.  
Comment 17 osavill 2004-08-05 15:19:37 UTC
As I now longer have access to an LDAP source and given its age the Issue report
should probably be closed unless this is known to still ba a valid issue.

Thanks.
Comment 18 thackert 2005-01-01 12:28:37 UTC
I have seen that osavill has asked to close this issue in August. Would it be o.k. if  it  is closed now by the original 
reporter or someone else? Or does the problem also occur in newer versions of OOo? I also have no ldap environment 
here to test it ... :(
Comment 19 wind.li 2005-03-23 09:00:08 UTC
working transfer
Comment 20 Marcus 2017-05-20 10:44:35 UTC
Reset the assignee to the default "issues@openoffice.apache.org".
Comment 21 oooforum (fr) 2018-08-13 15:22:44 UTC
AOO needs a new LDAP driver:
https://bz.apache.org/ooo/show_bug.cgi?id=124987