no error message when LDAP replication fails (on bad port) 1) set your LDAP port to 123 or something bogus 2) replicate looking at the UI, replication never starts. The progress dialog comes up, but its in an uninitialized state. we should be letting the user know what we failed to establish a connection or something. I bet we have similar problems if we fail to connect to the server if the server is down, or if the dns lookup failed.
Setting QA Contact to Yulian for now. Please change if incorrect.
QA Contact: nbaca → yulian
This is because currently the UI doesnot display any messages for either completion success or failure. We also need to return different error codes if we want to display different error messages but the first thing we should do is display a generic success or failure message. Will change the UI for that.
For generic success message: "Connection to the LDAP server succeeded." For generic failure message: "Connection to the LDAP server failed." For bad port error: "Connection to the LDAP server failed. Verify that you entered the correct port number for the directory server, and then try again."
taking - this needs to be driven forward, and we should display specific error messages.
Assignee: rdayal → bienvenu
Summary: no error message when LDAP replication fails (on bad port) → no error message when LDAP replication fails (e.g., on bad port)
I'll let Standard8 figure out what to do here...
Assignee: bienvenu → bugzilla
Assignee: bugzilla → nobody
Component: MailNews: Address Book & Contacts → LDAP Integration
Product: SeaMonkey → MailNews Core
QA Contact: address-book → ldap-integration
Comment on attachment 84334 [details] [diff] [review] a patch to fix this Patch has bitrotted, because mailnews/addrbook/prefs/resources/locale/en-US/replicationProgress.properties no longer exists, and the rest of the hunks also fail to patch.
Attachment #84334 - Attachment is obsolete: true
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
You need to log in before you can comment on or make changes to this bug.