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 655983 - MAPI errors when switching between screens
MAPI errors when switching between screens
Status: RESOLVED DUPLICATE of bug 653489
Product: evolution-mapi
Classification: Applications
Component: miscellaneous
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2011-08-04 15:03 UTC by rmeador
Modified: 2011-08-11 11:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rmeador 2011-08-04 15:03:00 UTC
Evolution 3.0.2 with evolution-mapi 3.0.2-2.1 on 64-bit Fedora 15, Exchange 2010.

When switching between different folders in the inbox or between Mail and Calendar, an error message is displayed at the top of the screen in red.

When switching among inbox folders:

Fetching items failed: QueryRows: MAPI error  (0x80040fff) occurred

When switching from inbox to calendar:

Failed to fetch changes from a server: QueryRows: MAPI error  (0x80040fff) occurred

Somewhere on the internet I found mention of errors like this happening when you switch an account from Exchange 2003 (which I think uses the OWA scraping connector) and Exchange 2007.  This is exactly what I had done, so I deleted the account and recreated it from scratch as a MAPI account, and it made a huge difference -- much fewer errors.  I can't be sure the errors that went away from recreating the account were these errors messages, it may have cured different errors.  Regardless, some errors still occur.

I discovered this website which mentions the error code, it seems that some Exchange 2007 ROPs don't exist in 2010: http://social.msdn.microsoft.com/Forums/en-CA/os_exchangeprotocols/thread/d3c860a8-f131-4c7a-aa11-b9ec328d06c4

Let me know if there's any more info I can provide to assist in debugging.
Comment 1 Milan Crha 2011-08-11 11:54:29 UTC
Thanks for a bug report. This got fixed very recently, within bug #653489, thus I'm marking this as a duplicate of it. Note this was evolution-mapi's issue, where older servers (before Exchange server 2010) were forgiving when evo-mapi requested 0 rows for QueryRows call.

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