Bug 194574

Summary:	Lost connection to Evolution Exchange backend process
Product:	[Fedora] Fedora	Reporter:	Eugene Roux <eroux>
Component:	evolution-connector	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	5	CC:	john.horne
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:	evolution-connector-2.6.3-1.fc5.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-08-10 11:59:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eugene Roux 2006-06-14 07:01:53 UTC

Description of problem:

Note: This was logged as Bug ID 194592 before the DB crash.

When attempting to use Evolution Connector 2.6.2 under FC5 I get the dreaded:

> Error while Scanning folders in "Exchange server foo.bar.baz".
> 
> Lost connection to Evolution Exchange backend process

dialog.

Running "E2K_DEBUG=4 `locate evolution-exchange-storage`" seems to indicate the
the connector, itself, if quite cheerily keeping on chatting to the Exchange
server while scanning the public folders (of which the Exchange Server seems to
have quite a couple).

Running "E2K_DEBUG=m evolution", on the other hand, complains about a couple of
cases of "camel_exception_get_id called with NULL parameter." before it hands me
the following two entries:

> (evolution-2.6:5621): evolution-mail-WARNING **: Error occurred while existing
dialogue active:
> Lost connection to Evolution Exchange backend process

and 

> (evolution-2.6:5621): evolution-mail-WARNING **: Error getting folder info
from store: Lost connection to Evolution Exchange backend process

Strangely enough, forcing a downgrade to Connector 2.6.1 and creating the
required links to libraries required by it allows Evolution to run just fine,
barring the occational run-away proccess.

Version-Release number of selected component (if applicable):

evolution-2.6.2-1.fc5.5
evolution-connector-2.6.2-1.fc5.4
evolution-data-server-1.6.2-1.fc5.1
evolution-sharp-0.10.2-9.3
evolution-webcal-2.4.1-3.4

Comment 1 Eugene Roux 2006-06-14 07:57:58 UTC

The Ubuntu Launchpad bug:
  https://launchpad.net/distros/ubuntu/+source/evolution-exchange/+bug/34199

Comment 2 John Horne 2006-06-14 10:41:24 UTC

Re comment 1 - No I think that is a separate problem. This bug connects to the
server and then fails, in your case it doesn't connect. Look at some of the
duplicated evolution bugs listed in this bugzilla. The problem has been referred
to the people at gnome and is being worked on.

I too have *this* bug. However, our evolution server has a lot of public
folders, and when yum upgraded evolution to the latest release it started to
download all the folders. My home .evolution folder is currently almost a
gigabyte in size because of this!

I have downgraded evo to the previous version and it works fine.



John.

Comment 3 Eugene Roux 2006-06-14 13:10:18 UTC

On further investigation I concur, the bugs are similar on a superficial level only.

What seems to be happening in my case is that the connector is trying to sync
the public folders of the exchange connector to a local cache (not a good idea
as mentioned by <a
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=194574#c2">#2</a>,
since there is no guarantee that the local system's capable of handling the
potential amount of data) and that Evolution then times out waiting for the
connector.

I've reverted Evolution back to 2.6.1 in totality (which upset gnome-panel
slightly) and all seems well again.

Comment 4 Eugene Roux 2006-08-10 09:19:03 UTC

I've installed Evolution 2.6.3 from Updates-Testing and it seems to have
resolved the issues completely. From my perspective this bug has now been resolved.

Comment 5 John Horne 2006-08-11 09:53:11 UTC

Agreed, the updates-testing repo versions of evolution, evolution-data-server,
and evolution-connector install fine and seem to have resolved the problem. The
calendaring between evolution and Exchange also seems to work again :-)

Many thanks to the people involved.

John.