GNOME Bugzilla – Bug 395989
Evolution Mail: Lost Connection to Evolu...
Last modified: 2010-10-02 20:26:09 UTC
What were you doing when the application crashed? Lost Connection to Evolution Exchange Backend. Beginning two days ago, immediately after a prompted security update, everytime I start Evolution I get the error message above. My access to my Inbox is halted and outgoing mail stalls on my local machine. Sometimes I get the error message as soon as Evolution begins (before I even enter my mail password), and sometimes it does not occur until after I enter my mail password. I believe this error has something to do with the security updates that were prompted on my machine. How can I figure out what the problem is? I use Unbuntu 6.10 (edgy) and Evolution 2.8.1. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0
Created attachment 80283 [details] CAMEL_DEBUG=all evolution >& camel.out
Created attachment 80284 [details] E2K_DEBUG=4 evolution-exchange-storage >& exchange.out Actual commands used: evolution --force-shutdown env E2K_DEBUG=4 /usr/lib/evolution/2.8/evolution-exchange-storage >& /tmp/exchange.out Says there is another version of evolution-exchange-storage is running, but how can this be if I did evolution --force-shutdown?
Thanks for reporting the bug, Noble. I just checked the code that handles "--force-shutdown", and it doesn't work on Exchange process.. I am committing a fix by tomorrow, which should solve that part of the bug. Meanwhile, can you try to get us E2K_DEBUG traces of both evolution and evolution-exchange-storage process by manually killing the exchange-storage process?
I just checked running force-shutdown without my test patch and it still works and this is with 2.6.x. see When you do "evolution --force-shutdown", what do you see in the console? It would be something like: varadhan@vvaradhan-lap:~> evolution --force-shutdown Shutting down evolution-exchange-storage (Evolution Calendar Exchange backend / Evolution Addressbook Exchange backend) Shutting down evolution-data-server-1.6 (Evolution Calendar file and webcal backend / Evolution Addressbook file backend) Shutting down evolution-alarm-notify (Evolution Calendar alarm notification service)
(In reply to comment #3) <SNIP> > Meanwhile, can you try to get us E2K_DEBUG traces of both evolution and > evolution-exchange-storage process by manually killing the exchange-storage > process? > Hi -- thanks for quick response. I'm not sure I know exactly how to "manually kill the exchange-storage process", but here's what I've done: ======================================================================= ======================================================================= noble@USMANBDAMATH085:~$ evolution --force-shutdown Shutting down evolution-exchange-storage (Evolution Calendar Exchange backend / Evolution Addressbook Exchange backend) Shutting down evolution-alarm-notify (Evolution Calendar alarm notification service) Shutting down evolution-data-server-1.8 (Evolution Calendar file and webcal backend / Evolution Addressbook file backend) noble@USMANBDAMATH085:~$ /usr/lib/evolution/2.8/evolution-exchange-storage --force-shutdown Evolution Exchange Storage up and running ===================>>>>[Had to press Ctrl-C]<<<<======= noble@USMANBDAMATH085:~$ env E2K_DEBUG=4 /usr/bin/evolution >& evo_debug_try2.log ===================>>>>[Evolution opened, I received the "Error while refreshing folders: Lost connection to evolution exchange backend" error and I exited evolution]<<<<========= noble@USMANBDAMATH085:~$ evolution --force-shutdown Shutting down evolution-alarm-notify (Evolution Calendar alarm notification service) Shutting down evolution-data-server-1.8 (Evolution Calendar file and webcal backend / Evolution Addressbook file backend) noble@USMANBDAMATH085:~$ /usr/lib/evolution/2.8/evolution-exchange-storage --force-shutdown Evolution Exchange Storage up and running ===================>>>>[Had to press Ctrl-C]<<<<======= noble@USMANBDAMATH085:~$ env E2K_DEBUG=4 /usr/lib/evolution/2.8/evolution-exchange-storage >& exc_debug_try2.log ===================>>>>[Opened Evolution from icon/menu]<<<<======= ===================>>>>[Received "Error while refreshing folders: Lost connection to Evolution Exchange backend". Exited Evolution. In the terminal window, the prompt returned.]<<<<==== noble@USMANBDAMATH085:~$ ======================================================================= ======================================================================= I've uploaded the two files "evo_debug_try2.log" and "exc_debug_try2.log" files below. Let me know if I should do the "evolution-exchange-storage --force-shutdown" a different way. Anything I can do to help...
Created attachment 80836 [details] env E2K_DEBUG=4 /usr/bin/evolution >& evo_debug_try2.log This file (and exc_debug_try2.log) go with comment 3.
Created attachment 80837 [details] env E2K_DEBUG=4 /usr/lib/evolution/2.8/evolution-exchange-storage >& exc_debug_try2.log This file (and evo_debug_try2.log) go along with comment 3.
Created attachment 80840 [details] E2K_DEBUG=4 evolution &> evo_debug_try2a.log One more log file -- I wasn't sure if "evo E2K_DEBUG=4 evolution" would be the same as "E2K_DEBUG=4 evolution"... so I re-ran the debug command: ================================================================== ================================================================== noble@USMANBDAMATH085:~$ evolution --force-shutdown Shutting down evolution-alarm-notify (Evolution Calendar alarm notification service) Shutting down evolution-data-server-1.8 (Evolution Calendar file and webcal backend / Evolution Addressbook file backend) noble@USMANBDAMATH085:~$ /usr/lib/evolution/2.8/evolution-exchange-storage --force-shutdown Evolution Exchange Storage up and running ===================>>>>Had to press Ctrl-C<<<<======= noble@USMANBDAMATH085:~$ E2K_DEBUG=4 evolution &> evo_debug_try2a.log ===================>>>>Evolution started. Received "Error while refreshing folders: Lost connection to Evolution Exchange backend". Exited Evolution. In the terminal window, the prompt returned.<<<<==== noble@USMANBDAMATH085:~$ ======================================================================== ========================================================================
Hi -- it's been over a month now and it looks like no one's touched this since I uploaded more log files. I am still having this problem. Is there any hope of a solution? --Leigh
I'm getting the same error message constantly, evolution exchange has been almost unusable for me since I upgraded from 2.4.x to 2.8.2.1. I'm running Gentoo on an amd64 system. I installed the usual way, by doing: emerge evolution-data-server evolution-exchange evolution My currently installed versions are: gnome-extra/evolution-data-server-1.8.2 gnome-extra/evolution-exchange-2.8.1 mail-client/evolution-2.8.2.1 I occasionally manage to read and send some mail, but within a few minutes I get "Lost Connection to Evolution Exchange Backend". Sometimes as soon as I start Evolution, I get "Could not connect to Evolution Exchange backend process: Please restart Evolution". It does look like evolution-exchange-storage is running: pw@kermit ~ $ ps wax | grep evo 3781 ? Ssl 0:00 evolution 4049 ? Sl 0:00 /usr/libexec/evolution-data-server-1.8 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_InterfaceCheck --oaf-ior-fd=19 4052 ? Sl 0:00 /usr/libexec/evolution/2.8/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.8 --oaf-ior-fd=20 4059 ? Sl 0:00 /usr/libexec/evolution/2.8/evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory:2.8 --oaf-ior-fd=21 13322 pts/1 R+ 0:00 grep evo I've tried doing evolution --force-shutdown, it kills all the above processes but I get the same errors when restarting evolution.
I've discovered that if I click "Work offline" and then "Work online", I can get into my Inbox. But if I try to open ANY other folder, I get "Error while Opening folder exchange://username%40hostname;auth=Basic@exchangehostname/personal/foldername. Could not open folder" ... where username, hostname, exchangehostname, and foldername are of course standins for the actual values :-) Once this error happens, I can no longer get into the Inbox either, I get this: "Error while Refreshing folder. No such folder"
There seems to be a pattern here: when I first start evolution after a reboot, it's OK until I visit one particular folder. once I've done that I'm screwed. I can get back into Inbox using the work offline / work online trick, but then all other folders are unusable, as per the previous comment.
I'm also on Gentoo and this solution worked for me: http://www.buggy.id.au/2007/03/06/solved-evolution-loosing-connection-to-exchange/#comment-656 evolution –force-shutdown cd ~/.evolution cd mail/exchange ls (to see what directory is there - in my case only one as I only have one exchange server account) rm -rfv ./(name of directory) Restart Evolution - did not have to re-create account
03 Mar 2008 Los Angeles I am only adding another 'me too' to this bug report, confirming that it still is a problem. System: Slackware 12.0 Dropline Gnome Evolution 2.12.3 Until today, I could always get Evolution to stay connected to the backend after killing all evolution-related threads; it was a problem, but not a show-stopper. Today it is a showstopper: never stays connected to backend. ==Mel Strom
Can you please try in current stable 2.22.2, thanks in advance.
This seems to have been dormant for a while, but there has been some activity on Ubuntu's Launchpad: https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/119886 The problem seems to have gotten worse going from Ubuntu 8.10 to 9.04. Ubuntu 9.04 currently uses evolution 2.26.1.
This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it. Can you please check again if the issue you reported here still happens in a recent version of GNOME and update this report by adding a comment and adjusting the 'Version' field? Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE after 6 weeks.
Speaking for myself, I have no way to test this bug anymore as it's been 3 years since I changed jobs and no longer have access to that (or any) exchange server. I don't use Evolution anymore either. Sorry.
clarification: slinkp == Paul Winkler.
Closing as incomplete.