Apache OpenOffice (AOO) Bugzilla – Issue 49765
time out on LDAP queries
Last modified: 2017-05-20 09:36:06 UTC
I register my ldap server as database for OOo. The settings seems good: when I try to connect, the connection succeds. But every query i tried, I got a message box saying 'The data content could not be loaded. Timeout waiting for result'. This happens either on data source interface (on Writer docs) and on Base interface. Trying to make a query using the wizard, I can get the field labels and the query definition is saved, so I assume that the connection is working... The ldap server is correctly working, as i can use it as addressbook in my Mozilla Thunderbird profile.
I just discovered that OOo doesn't test correctly the connection on my ldap server: whatever I write in the username field (on Database properties box) or in the password field (on the 'User Name and Password Required' box), the program ever says 'The connection was established successfully'.
hi ttissino, >> "I just discovered that OOo doesn't test correctly the connection on my ldap server:" could you provide a verbose log of the LDAP communication as your server sees it? thanks, Max
Hello ttissino, *, could you attach a log from your LDAP server, as maxweber has requested on May 29th 2005? And could you try it with a newer version of OOo (like the stable 2.4.1 or one of the developer builds) if your problem also appears there? TIA Thomas.
Sorry, but I does not remember anything about this bug. However, I tried to replicate it, but it seems there is no database type for a generic ldap server (there is an item called 'LDAP evolution' but I guess is not for me...).
This Issue requires more information ('needmoreinfo'), but has not been updated within the last year. Please provide feedback as requested and re-test with the the latest version of OpenOffice - the problem(s) may already be addressed. You can download Apache OpenOffice 3.4.1 from http://www.openoffice.org/download Please report back the outcome of your testing, so this Issue may be closed or progressed as necessary - otherwise the issue may be Resolved as Invalid in the future.
Additional information was needed to reproduce this bug, but none was provided.