GNOME Bugzilla – Bug 637373
can not book resource in 2.30: "Cannot send calendar objects"
Last modified: 2013-07-23 14:30:48 UTC
After upgrading to Ubuntu 10.10, several problems occur with evolution-exchange but part of them are (more or less) solved now. However, when trying to book a resource when organizing a new meeting, I received the following error message "Cannot send calendar objects" and the booking does not work. 1) ubuntu release Description: Ubuntu 10.10 Release: 10.10 2) version of package evolution-exchange: Installé : 2.30.3-0ubuntu2 Candidat : 2.30.3-0ubuntu2 evolution: 2.30.3-1ubuntu7.1 evolution-data-server: 2.30.3-2ubuntu2 3) what you expected to happen when trying to book a resource when organizing a new meeting, the invitation is correctly send and the resource (room) is booked 4) What happened instead received an error message "Cannot send calendar objects" and the resource is not booked This feature used to work under Lucid (evolution 2.28). This bug is rather problematic when using evolution in a production context. I also reported the bug on ubuntu launchpad but no response yet https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/669814 Hilaire
Do you use evolution-mapi or evolution-exchange?
Hi, I use evolution-exchange on an exchange 2003 server. Happy new year (with a little bit of advance)
Hi, I still have the same problem with evolution 2.32.2-0 and evolution-exchange 2.32.2-0. Can I provide further information to help resolving this bug? Yours truly, Hilaire
Hi Hilaire, if this is still a problem, you could try to provide debug output via E2K_DEBUG as described on http://projects.gnome.org/evolution/bugs.shtml
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers. If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible). There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX. Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
Hi, We are currently using an Exchange 2003 server, that why I use the evolution-exchange package. Cheers, Hilaire
In that case I'd recommend to stay with Evolution 3.4 (which works with "evolution-exchange") and only to upgrade to Evolution 3.6 (which will not receive testing with "evolution-exchange") after Exchange connectivity testing first, to avoid bad surprises.
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.