After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 274321 - [PATCH] exchange: unable to connect to backend server
[PATCH] exchange: unable to connect to backend server
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.1
Other All
: Normal normal
: Future
Assigned To: Sushma Rai
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2005-04-01 16:14 UTC by ximian
Modified: 2006-08-07 08:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch - diff for the glade file (982 bytes, patch)
2006-08-02 11:59 UTC, Sushma Rai
committed Details | Review

Description ximian 2005-04-01 16:14:21 UTC
If an incorrect username is entered when connecting to an exchange
server, and it is then changed, clicking Send/Receive will show a
message about being unable to connect to backend process.

A "pkill evolution" is the workaround.
Comment 1 Krishnan R 2005-09-15 15:16:18 UTC
This looks more like a bug to me which should be fixed by 2.4.1.   Marking this
as  'Major'.
Comment 2 shakti 2005-09-20 06:36:11 UTC
I could not reproduce this.

I tried in the following way:
1) Tried to configure a new account.
2) Gave an incorrect user name and clicked on 'Authenticate' button. 
The authentication failed so the 'Forward' button doesn't get enabled. So,
configuring the account (with an incorrect username) is not possible.

I too tried in this way:

1) Clicked on Edit->Preferences->Mail Accounts->Edit
2) Clicked on 'Receiving Email' tab and changed the username to something else
(an incorrect name). Closed this dialog and clicked on 'Send/Receive'. An error
dialog shows "Could not connect to Evolution Exchange backend process". Expected .
3) Changed the username back to the original name and clicked on 'Send/Receive'.

It is working fine.

Please let me know if I missed something.
Comment 3 lsof 2005-10-14 12:37:48 UTC
It's half fixed :)

For the second method, you get the "file does not exist" error message. It's not
a friendly error message, it doesn't tell the user what the problem is.

If the error message was improved, the bug could go.
Comment 4 André Klapper 2006-07-26 13:21:04 UTC
removing old target milestone
Comment 5 Sushma Rai 2006-08-02 11:59:17 UTC
Created attachment 70068 [details] [review]
Patch - diff for the glade file
Comment 6 Sushma Rai 2006-08-07 07:13:41 UTC
Mistake in the above comment.
It is the patch to show error when there is a change socket file path.
Comment 7 Sushma Rai 2006-08-07 08:32:44 UTC
patch committed to CVS head.