GNOME Bugzilla – Bug 653489
QueryRows fails on exchange 2010 servers
Last modified: 2011-08-11 11:54:29 UTC
Sometimes while trying to access the Exchange Calendar on Exchange 2011 we get this error on several popup messages in a row Erro em mapi://user1@w2k8.testead.intranet/ Falha ao obter alterações de um servidor: QueryRows: Ocorreu o erro MAPI MAPI_E_NOT_IMPLEMENTED (0x80040fff) Environment: evolution 2.32 evolution-mapi 0.32.2 Ubuntu 10.04 Lucid
Thanks for a bug report. I suppose you meant Exchange Server 2010, because 2011 is not provided by Microsoft yet. Nonetheless, I noticed same issue with exchange 2010 servers, but it seems like 2010 server specific. I'll see what I can do as soon as I'll have a 2010 server available.
Aha, I just found a corresponding commit in openchange which explains the issue: http://tracker.openchange.org/projects/openchange/repository/revisions/2087 > When Queryrows is called on Exchange 2010 and no rows are available, > QueryRows returns MAPI_E_NOT_IMPLEMENTED error (0x8004FFFF).
Hi Milan, Yes I meant Exchange 2010. That commit is 11 months old. I wonder why my openchange package didn't get it. This is what I have; libexchange-storage1.2-3 2.28.3.1-0ubuntu5 libexchangemapi-1.0-0 0.32.2-0ubuntu1~10.04prevu1
Created attachment 190914 [details] [review] ema patch for evolution-mapi; This is related to commit 1609b6516 in evolution-mapi, which is basically fixing this issue, it only doesn't do it quite right on two places, thus this patch is making it working right there too.
Created commit 2429f2b in ema master (3.1.3+) Created commit c5f83e7 in ema gnome-3-0 (3.0.3+)
(In reply to comment #3) > Hi Milan, > > Yes I meant Exchange 2010. > > That commit is 11 months old. I wonder why my openchange package didn't get it. The commit I mentioned from openchange wasn't for its change in their code, but for the explanation. The openchange commit itself, the code change, is unrelated for evolution-mapi, in a sense that it doesn't influence it. The evolution-mapi commits are doing same changes as the openchange commit, though.
> > The commit I mentioned from openchange wasn't for its change in their code, but > for the explanation. The openchange commit itself, the code change, is > unrelated for evolution-mapi, in a sense that it doesn't influence it. The > evolution-mapi commits are doing same changes as the openchange commit, though. Thank you for the explantion Milan. Can you comment on the backporting current fixes to GNOME 2.x vs backporting GNOME 3.x to a current LTS enterprise distro? Current distros need the fixes but they have GNOME 2.x (with evolution-mapi 2.3x , etc).
Backporting this commit to evolution-mapi 2.32.x should be enough to fix this issue: http://git.gnome.org/browse/evolution-mapi/commit/?id=c5f83e7d27
Evolution asks the password for each component: mail, calendar, notes, tasks, contacts, GAL,.... The stdout is full of the following messages: (evolution:8452): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: erro de programação: A aplicação enviou dados inválidos) The latest part translates to: "programming error. The application sent invalid data" The password was saved on the keyring while running the account wizard on evolution. It was saved "insecurely" without a keyring password.
Please ignore or delete my previous comment: it was meant for a different bug report.
*** Bug 655983 has been marked as a duplicate of this bug. ***