Bug 722880

Summary:	Lots of MAPI error MAPI_E_CALL_FAILED errors
Product:	[Fedora] Fedora	Reporter:	Peter Robinson <pbrobinson>
Component:	evolution-mapi	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	mbarnes, mcrha
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-08-04 12:31:46 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 Peter Robinson 2011-07-18 10:47:24 UTC

I get a lot of the following errors. Mostly when moving emails to folders.

OpenFolder: MAPI error MAPI_E_CALL_FAILED (0x80004005) occurred

When they happen the mapi account basically stops working. On occasion if I set evolution offline and then online it will start to work. Most of the time it requires a restart of evolution.

evolution-NetworkManager-3.0.2-3.1.fc15.x86_64
evolution-help-3.0.2-3.1.fc15.noarch
evolution-3.0.2-3.1.fc15.x86_64
syncevolution-gtk-1.1.1-6.fc15.x86_64
evolution-mapi-3.0.2-2.fc15.x86_64
evolution-data-server-3.0.2-1.fc15.x86_64
samba4-libs-4.0.0-25.alpha11.fc15.x86_64
openchange-0.9-18.fc15.x86_64

Comment 1 Milan Crha 2011-08-04 12:31:46 UTC

Thanks for a bug report. It seems to me like evo-mapi lost connection to the server, and since them everything got lost. One issue was with e-addressbook-factory, where weren't dropped connections to the server, thus, after certain period of time (and activity), the server rejected new connections. That's for the case when going offline/online didn't help. The other case, well, it depends. But I noticed something similar too, when I kept evolution running for two hours with no activity on evo-mapi account.

The issue with too many opened connections were fixed in openchange [1] and is part of 0.11.

Let's deal with the connection-lost part in an upstream bug [2].

[1] http://tracker.openchange.org/issues/361
[2] https://bugzilla.gnome.org/show_bug.cgi?id=608327

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