José M. Fandiño wrote:

Philip Washington wrote:

...

I appear to be having a problem with getting addresses from our LDAP server. I am currently using evolution 2.0.2 and can create the address

What ldap server? what version?

The openldap version is 2.0.21

...

list, but whenever I click on the list I get an error -------------------------------------- Error loading addressbook.

We were unable to open this addressbook. This either means you have entered an incorrect URI, or the LDAP server is unreachable. -------------------------------------------

where are the logs of the ldap server?

I was not able to find a log file on the ldap server. There does not appear to be one set in the configuration file.

...

I am able to connect to the LDAP server using KAddress and was able to connect using evolution 1.4 , but whenever I have tried a system with evolution 2.01 or 2.0.2 I get this message. Whenever I click "Find Possible Search Bases" it returns with the correct search base . I'm kind of at a loss as to why it seems to work in these other apps but not on evolution 2+

what bind versions are using evolution and KAdress? I am using bind 9.2.1

The problem seems to have corrected itself after shutting down evolution and restarting a couple of times all of a sudden it started working. I also ran into a problem with one of my pop3 servers. It appeared to connect then it would just stop after attempting to get the summaries of the emails. No error other than Fetch failed operation in progress. On 2 occassions I had to uninstall evolution and then reinstall before I could even get it to ask me for my password again. I then used ethereal to see if I could spot the problem and saw that the user name was wrong. Fixed this and set up a connection for another server, it also started having problems with the same symptoms. I used ethereal again and found that I had mistyped the password. I had to delete that server information and create a new one and enter the correct password and it began working fine. I think that both of these errors should have had a standard error message explaining to the user what the problem was. I still don't know why the LDAP server kept having problems , but it's been working all day without a problem. There is something not quite right with the way evolution is handling errors in these situations.