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 443591 - evolution exchange backend repeatedly loses contact with evolution
evolution exchange backend repeatedly loses contact with evolution
Status: RESOLVED DUPLICATE of bug 498099
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
unspecified
Other All
: Normal major
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2007-06-03 15:21 UTC by Jonathan Kamens
Modified: 2007-12-09 00:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Jonathan Kamens 2007-06-03 15:21:19 UTC
Please describe the problem:
I'm using evolution-connector-1.11.2-2.fc8 from Fedora Core Development, and the same version of evolution.  I repeatedly and often get this message when attempting to access folders in my exchange mailbox: "Error while Refreshing folder.  Lost connection to Evolution Exchange backend process".  When I get this message, evolution-exchange-backend is still running.  This has made evolution essentially unuseable for me -- it repeatedly loses my backend connection and has to be started frequently.  This was also happening with evolution-2.10.1-4.fc7.i386.rpm; I thought upgrading might fix it, but it didn't.

Steps to reproduce:
Start Evolution, try to access Exchange mailbox, it might work for a little while, but then it stops with the message above.

Actual results:
See above.

Expected results:
It would keep working.

Does this happen every time?
At this point, yes, pretty much, a little while after I start Evolution it'll stop being able to communicate with the backend process.  This even happens when I do evolution --force-shutdown before starting evolution.

Other information:
If there's anything I can do to collect additional debugging information, please let me know what I should do.
Comment 1 Jonathan Kamens 2007-06-03 15:48:55 UTC
I discovered E2K_DEBUG.  When I run evolution with it set, I see that the backend process chugs merrily along and then suddenly I see "flush failed", and that's when evolution stops being able to communicate with it, even though it's still running.  Like this:

...
---
<<< 1
<<< 8937 bytes
<<< 0
>>> 9
>>> (personal/Archive)
>>> "000067212d49"
---
>>> 9
>>> (personal/Archive)
>>> "000067212d4a"
--- flush failed

I should mention that my Exchange server can be somewhat unreliable, so for all I know the "flush failed" above means that my Exchange server closed the connection or something, but shouldn't Evolution try to reconnect automatically, like Outlook does?

Is there some way to get Evolution to reset the connection without exiting and restarting?

  jik
Comment 2 Jonathan Kamens 2007-06-03 15:52:38 UTC
Another date point... I put Evolution into offline mode and back into online mode.  It reconnected with the Exchange server at that point, but it must have been doing something wrong, because it kept getting back "No such folder" in response to every request to the backend process.

Oh, and while I'm mentioning things, I see errors that look like this from evolution when I have a folder in my Exchange mailbox with an ampersand followed by a space in its name:

error : unterminated entity reference  voice mail wish lists

The string " voice mail wish lists" is the part of the folder name that comes after the ampersand.
Comment 3 André Klapper 2007-12-09 00:10:16 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 498099 ***