GNOME Bugzilla – Bug 374810
Evolution will not connect to Exchange 2007 server
Last modified: 2009-05-10 21:25:16 UTC
Please describe the problem: When trying to configure Evolution to use an Exchange server connection the following error message is received: "The Exchange server URL you provided is for an Exchange 5.5 server. Ximian connector supports Microsoft Exchange 2000 and 2003 only." The Exchange servers the mailbox is hosted on are Exchange 2007 servers. Steps to reproduce: 1. Try to setup an Exchange account on a Exchange 2007 server. Actual results: The error message "The Exchange server URL you provided is for an Exchange 5.5 server. Ximian connector supports Microsoft Exchange 2000 and 2003 only." is received Expected results: I would like to have the exchange-connector updated to recognize an Exchange 2007 server. Does this happen every time? Yes. The old Ximian connector used on a Sun box running Evolution 1.* works fine. Other information: I tried to run E2k_DEBUG = 4 but I did not receive any logs that I could pass along. When trying to setup the Exchange account I am prompted for authentication before I receive the error messsage. The Ximian connector and Entourage for a Mac work prefectly well.
I can confirm that my current version of the exchange-connector does not work since our application group upgraded to exchange 2007. I am running Fedora Core 6 with all the latest updates (exchange-connector-2.8.2-2.fc6). I have created a bug report on Redhat's bugzilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220092 I also included several attachments with error messages. I will attach those here as well.
Created attachment 79278 [details] Bug Buddy Output
Created attachment 79281 [details] E2K_DEBUG=5 startup log
I can also confirm that exchange-connector does not work with Exchange 2007. I get the "The Exchange server URL you provided is for an Exchange 5.5 server" error message if forms-based authentication is used on the Exchange 2007 client access server. Here is the response of an Exchange 2007 client access server: HTTP Status Code: HTTP/1.1 302 Moved Temporarily Location: https://myserver.tkk.fi/owa/auth/logon.aspx?url=https://myserver.tkk.fi/owa/&reason=0 I think that Exchange 2007 is identified as Exchange 5.5 because of "logon.asp" part at the URL (see e2k-autoconfig.c) If basic authentication is used and I type the right password, I get the error message "Could not configure Exchange account because an unknown error occurred. Check the URL, username, and password, and try again". Other information. Accessing mailbox has changed in Exchange 2007. I think that the correct URL is: https://myserver.tkk.fi/owa/firstname.lastname@tkk.fi/ instead of https://myserveroldserver.tkk.fi/exchange/username/ where "firstname.lastname@tkk.fi" is your email address.
(In reply to comment #0) > > Expected results: > I would like to have the exchange-connector updated to recognize an Exchange > 2007 server. > > Does this happen every time? > Yes. The old Ximian connector used on a Sun box running Evolution 1.* works > fine. Can you run the old Ximian connector with E2K_DEBUG=4 and attach the log here? (if you are not comfortable attaching the log, you can mail it to me).
(In reply to comment #3) > Created an attachment (id=79281) [edit] > E2K_DEBUG=5 startup log > The attached log is truncated. Can you attach a complete log?
Comment on attachment 79281 [details] E2K_DEBUG=5 startup log Log is incomplete.
(In reply to comment #7) > (From update of attachment 79281 [details] [edit]) > Log is incomplete. > I assume you are talking about my attachment (I'm not the original author of the bug report). Actually that log contains everything I get. Remember, mine crashes which might explain why the log is incomplete. I also attached the bugbuddy output. Void
(In reply to comment #5) > (In reply to comment #0) > > > > Expected results: > > I would like to have the exchange-connector updated to recognize an Exchange > > 2007 server. > > > > Does this happen every time? > > Yes. The old Ximian connector used on a Sun box running Evolution 1.* works > > fine. > Can you run the old Ximian connector with E2K_DEBUG=4 and attach the log here? > (if you are not comfortable attaching the log, you can mail it to me). Are you looking for the log from the Ximian 1.* connector? I have forwarded this request onto one of our Sun admins and he has been unable to generate a log from his Evolution client. Are there different instructions for Evolution 1.*?
(In reply to comment #8) > (In reply to comment #7) > > (From update of attachment 79281 [details] [edit] [edit]) > > Log is incomplete. > > > > I assume you are talking about my attachment (I'm not the original author of > the bug report). Actually that log contains everything I get. Remember, mine > crashes which might explain why the log is incomplete. I also attached the > bugbuddy output. > > Void > How frequent does it crash for you? Can you apply the attached patch, build e-d-s and attach the screen-dump when it crashes?
Created attachment 82216 [details] [review] enables debug
(In reply to comment #10) > (In reply to comment #8) > > (In reply to comment #7) > > > (From update of attachment 79281 [details] [edit] [edit] [edit]) > > > Log is incomplete. > > > > > > > I assume you are talking about my attachment (I'm not the original author of > > the bug report). Actually that log contains everything I get. Remember, mine > > crashes which might explain why the log is incomplete. I also attached the > > bugbuddy output. > > > How frequent does it crash for you? Can you apply the attached patch, build > e-d-s and attach the screen-dump when it crashes? It crashes every time I try to start Evolution with an exchange-connector account enabled. In fact the only way I can start Evolution after creating/enabling an Exchange account is by starting evolution with the --disable-eplugin option and then disabling the Exchange account. What I don't understand at this point is if I am an anomaly or can everyone else connect to Exchange 2007 with no problems? Regarding the patch you want me to apply would you like that patch applied to the source RPM of the latest evolution RPMS for my FC6 installation (which I am currently running) or would you like me to check out a cvs/svn version? I will assume you want it applied to the latest FC6 version that I am running. Will check back as soon as I get a chance to do this. Thanks for the help!
The patch should apply neatly in 2.8.x as well, as nothing has changed in e2k-context.c (IIRC). In case of FBA, OWA presents us with a HTML page that asks for username and password and has "action" property set to a URL that will be used to send/receive authentication details. In your case, this "action" seems to be something not in the expected format and the patch will print the value of "action" once it decodes it.
Hmmm, I can't seem to build the FC6 RPM with the patch (it does build without it). Here is the build log: http://voidmain.is-a-geek.net/files/misc/evds.log Your patch is named "tst.patch" and is Patch #19 in the log. I guess I'll have to download the cvs source. Thanks for the help so far!
I got the same error after applying the patch to the current cvs evolution-data-server source and trying to build it. I would build fine without the patch. I saw your thread about Exchange 2007 on the Evolution mailing list including the little jab from the brutus guy and for the record, we can't get evolution-brutus to work with our setup either. However, that could very possibly be a configuration problem as we have not found a lot of documentation on exactly how to configure the client. We do get prompted for a password but no matter how we have tried to configure things we are not able to successfully log in. I have used the Evolution Exchange connector since Ximian first released it with little trouble along the way. That is, until our Exchange group decided to upgraded to 2007. One other note, I just upgraded to the latest FC6 updates and there is no change. Evolution crashes immediately upon start if an evolution-exchange account is configured. The current versions I am running: evolution-data-server-1.8.3-1.fc6 evolution-connector-2.8.2-2.fc6 evolution-webcal-2.7.1-6 evolution-devel-2.8.3-1.fc6 evolution-2.8.3-1.fc6 evolution-data-server-devel-1.8.3-1.fc6
(In reply to comment #14) > Hmmm, I can't seem to build the FC6 RPM with the patch (it does build without > it). Here is the build log: > > http://voidmain.is-a-geek.net/files/misc/evds.log > > Your patch is named "tst.patch" and is Patch #19 [edit] in the log. I guess I'll have > to download the cvs source. Thanks for the help so far! > Ah!!.. I missed to attach another hunk that is required.. attaching the same. This time it should compile without any issues.
Created attachment 82477 [details] [review] Second hunk Apply both the patches to compile.
(In reply to comment #17) > Created an attachment (id=82477) [edit] > Second hunk > > Apply both the patches to compile. > That got it. I applied both patches to the FC6 evolution-data-server source and I will attach the E2K_DEBUG=5 output.
Created attachment 82482 [details] E2K_DEBUG=5 log post debug patches E2K_DEBUG=5 log post debug patches
Created attachment 82485 [details] Bug Buddy Output - post patches Bug Buddy Output post patches. One new thing I noticed that as soon as Bug Buddy appeared when trying to start Evolution it said the "calendar" application had crashed.
(In reply to comment #20) > Created an attachment (id=82485) [edit] > Bug Buddy Output - post patches > > Bug Buddy Output post patches. One new thing I noticed that as soon as Bug > Buddy appeared when trying to start Evolution it said the "calendar" > application had crashed. > Timo provided me a test account in his Exchange-2007 setup and with that, the crash is fixed, however, Exchange 2007 seems to have changed quite a bit of semantics. I am able to authenticate, however, beyond authentication bits have changed and I am working on it. Will try to close it for next beta.
Awesome! I know of a few people who are standing by in anticipation. :)
Good to know that. It may just miss the coming RC release, I guess. However, let me try my best.
I can't say Evolution-Exchange crashes because I have't gotten beyond authentication, but I am not able to access Evolution 2007 and the message I get is that the URL I have is for an Exchange 5.5 server. Thanks, Michael
what is the timeline for the next RC? this Evolution-Exchange connectivity would seem to be a very inclusive development release, expanding the clients in many Exchange deployments. on behalf of our team here, we are very interested in progress on this initiative!
With Ubuntu 7.04 (Evolution 2.10) - and overnight once my mail server migrated to Exchange 2007, I am now not able to login to the mailserver Same basic auth. gives - error message as above posts. Just wanted to check and see if this progressed -
I can concur to this as well. The office's email upgraded to Exchange 2007 and now, I can't get access to the webmail (from the internet), surprisingly, the internal webmail (OWA) still works.(although I'm not sure how or perhaps its just not been upgraded yet???) Anyway, I'm also curious as to how this has progressed with Veerapuram Varadhan stating over 4 months ago that it will be in the next RC release. Unfortunately. I am unsure which is that RC candidate. I've just upgraded from 2.8.2 to 2.10.1 (in gentoo) along with all the needed stuffs and the error still persists. I've tried to do an E2K_DEBUG=10 /path/to/exchange-connector but there doesn't seem to be anything spewing out (for X reasons) as debug messages. Does anyone know what those X reasons may be?? I would really like to see this fixed. These sort of (lack of) interoperatability sucks, but knowing the software world, I guess there isn't much of a choice.
(In reply to comment #27) > Anyway, I'm also curious as to how this has progressed with Veerapuram > Varadhan stating over 4 months ago that it will be in the next RC release. > Yes, and it is targetted for 2.12 release. MS has changed quite a lot of things in Exchange 2007 and there are some issues that I am working on to speed up my work progress. > > I've tried to do an E2K_DEBUG=10 /path/to/exchange-connector but there doesn't > seem to be anything spewing out (for X reasons) as debug messages. > The maximum value that E2K_DEBUG takes is 5. See http://www.gnome.org/projects/evolution/bugs.shtml for all the values. > I would really like to see this fixed. > > These sort of (lack of) interoperatability sucks, but knowing the software > world, I guess there isn't much of a choice. > Well, Yes - but, MS normally is not worried about such things and Yes, everyone of us want this to be fixed ASAP.
I see. So, I won't even see anything on the 2.11 branch nor the SVN one. Well, that is to say, really sad. Just want to make it clear that everyone of us really appreciates your work and anything we can do to make it easier, we will gladly do it. BTW, when the 2.12 release cycle due? If you're done or if any of the major fixes are already in the SVN branch, do let us know, at least then, some of us can be your Bug-Buddy and (bother) you with additional bug infos. (hehe) Thanks again. One more thing, yeah, I tried a variation of E2K_DEBUG=1 to 5 and even m5 but nothing interesting ever comes up much like some of the startup logs posted here.
Oh.. One more thing.. during start up, I always get this error ** (evolution-exchange:2982): WARNING **: Unexpected kerberos error -1765328164 and looking at the krb5.h file, It's REALM_ERROR I'm logging in as domain\username
(In reply to comment #29) > I see. So, I won't even see anything on the 2.11 branch nor the SVN one. Well, > that is to say, really sad. > > > Just want to make it clear that everyone of us really appreciates your work and > anything we can do to make it easier, we will gladly do it. > > BTW, when the 2.12 release cycle due? If you're done or if any of the major > fixes are already in the SVN branch, do let us know, at least then, some of us > can be your Bug-Buddy and (bother) you with additional bug infos. (hehe) > By 2.12, it means the fix/feature will hit 2.11 branch may be in another couple of dot releases and Yes, users like you are our/my inspiration to work more and make it solid like a concrete. > Thanks again. > > One more thing, yeah, I tried a variation of E2K_DEBUG=1 to 5 and even m5 but > nothing interesting ever comes up much like some of the startup logs posted > here. > With Exchange 2007, the progress that I had so far is I am able to authenticate successfully and able to retrieve some basic information. However, Evolution needs some more information in-order-to show the mailbox and Exchange 2007 seems to have changed that interface. My MS-Exchange-2007 support work will resume from there, once I am done with my current optimization work to improve Exchange performance, which is hitting lots of Exchange connector users (irrespective of Exchange server versions). Thanks again and keep watching here... I may go crazy and do some-quick-hack to get it working. ;-)
>Thanks again and keep watching here... I may go crazy and do some-quick-hack to >get it working. ;-) Well, I'm piqued already. Good Luck.. and tell me where to send the Starbucks Coffee to.. :-)
Just want to get on the CC list as our server just upgraded and now I'm stuck using a browser to access my mail. I get the same error: libsoup-CRITICAL **: file soup-message.c: line 273 (soup_message_set_request): assertion `SOUP_IS_MESSAGE (msg)' failed I use the ebrowse interface.
Getting on the cc: list. I really need this connector to work. Otherwise I'll have to run Outlook on Wine at my workplace. And no one wants to do that.
Funny thing with mine though.. In the workplace, I can access it fine. (Thank goodness). it's only when I need to access it from home which is the problem. (https interface etc) At the workplace, I just use the existing (no change in Ip address etc) and I can login and use it fine. Send / receive email via it w/ no issues. I have not much idea why except that it doesn't work when it's on a HTTPS interface and when its outside of the workplace LAN. Having said that, I would still like for this to get fixed as I'm afraid my luck may run out soon.
I see evolution 2.12 has been released without this update. Has this bug been re-targeted? -Jared
This doesn't seem to be present in 2.12. Do I have a misconfigured client, or has the patch not been applied?
Not sure why this is taking so long. I've abandoned Evolution for a Perl script that pulls my email out of Exchange. Sorry, I can't share the whole thing, it's not all mine. Above you mention you need to know what to do to show the mailbox. Here's what it takes in Perl: $search_req = HTTP::Request->new ( "SEARCH", $inbox_url, [ content_type => "text/xml", Range => "rows=0-99", Brief => "t", ], &get_list_mail_msg () ); sub get_list_mail_msg { my $s = <<"EOF"; <?xml version="1.0" encoding="utf-8" ?>\r <searchrequest xmlns="DAV:">\r <sql>\r SELECT "urn:schemas:httpmail:fromemail", "urn:schemas:httpmail:read" \r FROM ""\r WHERE "DAV:iscollection" = False AND "DAV:ishidden" = False \r EOF if (!$read_unread_too) { $s .= " AND \"urn:schemas:httpmail:read\"= False\r\n"; } $s .= <<"EOF"; ORDER BY "DAV:creationdate"\r </sql></searchrequest>\r EOF } You can contact me directly if you need more info. I can show you what works but I don't want to send the whole script. It seems odd that you'd be hung up on this, I thought Novell and MS had an agreement to share information to increase interoperability.
They moved us to Exchange 2007 too. They didn't even tell us about it, I had to find out the hard way. I would really like to see this working again, as the web interface is clunky. Any idea when you might be able to release something for testing?
Veerapuram, thanks for your work on this. It is much appreciated, and many, many people very much want to see this work. I know you have heard that this functionality is very important, and that people have complained that updates on your end haven't really been frequent. I think instead of promising that it will be out soon, you should start saying, "well, it'll be done when it's done." Then people can get realistic and move ahead with other alternatives to Evolution in the meantime. Like me. I'm realizing I can't rely on Evolution right now since we're moving to Exchange 2007. It just won't work. For those of you who are interested, I also found this update today: Veerapuram Varadhan, the Connector maintainer, wrote at the end of September 2007 that it would be part of the 2.14 release: http://vvaradhan.blogspot.com/2007/09/exchange-connector-evolution-212.html Later, in an October 2007 comment on this post, he noted that it would be part of the 2.22 release: http://vvaradhan.blogspot.com/2007/10/healthcare-cio-pats-evolutionexchange.html Again, thanks for your work. Keep it coming.
I don't know what you are thanking Veerapuram for. This thing has been broken for a year now. Veerapuram hasn't posted here since June. In September I offered to supply code snippets and got no response. If Novell has any other developers on this they don't appear to have any interest in getting this to work. Looks to me like they are happy to let Evolution die.
The Novell Evolution team has communicated privately that they are testing two different solutions. I would certainly prefer if those code commits and some "chatter" on progress were made on this bug to make the process a bit more transparent to the community. Dan, if there are no license issues with the perl script you are using, why don't you attach it to this bug? Also, for reference, Nirav Kumar <KNirav@novell.com> is apparently in charge of the Exchange integration for Evolution right now, and should now be CC'd on this bug.
I didn't write the script so I wouldn't publish it without permission. I can contact the author and see what he thinks. I'm pretty sure the Perl was derived from a Java interface found on Source Forge. I'm willing to supply parts if there is a specific function that they can't reverse engineer. I did a bit of reverse engineering and expanded the script myself. It doesn't seem that hard. Anyway, I published what I thought was needed and never got any response.
Just getting on the CC list. I'm now facing this problem too, as my office just "upgraded" to Exchange 2007.
i sometimes wonder what people complain about. do you have a service level agreement with novell? evolution is not owned by novell, it's a community product, as gnome is. sure, it's nice to get serious bugs fixed as soon as possible. and a lot of the evolution folks are currently working on getting exchange 2007 support done, hopefully for gnome 2.22, definitely for gnome 2.24.
Hi Andre, Are people complaining? I'm guessing you mean me. I didn't mean to complain, all I did was question why the dev team was being thanked in a thread that is still an unresolved problem. As you can see, I offered to help (2007-09-22), then offered to help again (2007-11-19) but haven't heard anything. This problem was first reported here 2006-11-13, well over a year ago. So how do you know that the Evolution folks are currently working on Exchange 2007 support?
There's a separate SVN branch for Exchange 2007 support.
yepp, i know it from the developers' blogs, the evolution-hackers mailing list and the weekly evolution team meetings, for example: http://blogs.gnome.org/sragavan/2007/12/04/evolution-222-progress-updates/ or http://www.mail-archive.com/evolution-hackers@gnome.org/msg02139.html
My evolution 2.22.1.1 under Ubuntu 8.04 on AMD64 architecture recently fell victim to Information Services (at my company) upgrading from Exchange 2003 to Exchange 2007. Thus, I join the ranks of those wishing for Exchange 2007 support. As a software engineer, I am willing to hack code if there is anything I can do to help. I obviously have a decent test case.
My university will not support MAPI for Exchange, at least not for non Outlook clients, so the evolution-mapi lib will not help me. Our Exchange admin suggest that Evolution should look to support EWF (sp??) for the Evolution<->Exchange 2007 connection.
@mike.basinger: The only thing i found by googling is "Enhanced Write Filter (EWF)" which does not seem to be related. Please provide at least a link what "EWF" should be, never heard of it. I strongly suggest that your exchange admin adds MAPI support for Exchange. Evolution 2.26 will use the libmapi 0.8 library by openchange for accessing Exchange 2007 servers. Patches welcome though.
I'm sorry, I misheard him, it is Exhcnahe 2007 EWS. http://msdn.microsoft.com/en-us/library/bb204119.aspx
libmapi has been accepted as an official dependency for GNOME 2.26. evolution-mapi has been accepted as an official desktop module for GNOME 2.26. Hence this bug is FIXED. For specific issues you face when using evolution-mapi please file seperate bug reports.
*** Bug 570191 has been marked as a duplicate of this bug. ***
After using for some days (Ubuntu 9.04 and Exchange 2007), Exchange-MAPI works only through MAPI in Exchange 2007. It does not work through OWA!!! If you need to connect using OWA with Exchange 2007 YOU CANNOT, neither through Exchange connector nor through Exchange-MAPI. Please unmark this bug as 'Fixed' because Exchange-MAPI DOES NOT fix the problem, only gives another way to connect to Exchange that is not always possible to use (MAPI), as Exchange-MAPI configuration is very poor, only valid for local Exchange servers. Proxy access is not possible, and using OWA with Exchange-MAPI is impossible, so if MAPI is not activated and only OWA access to Exchange is possible, non of both connectors work. IMHO, both connector should merge into one, after fixing the OWA<->Exch2007 bug.
I don't think that OWA is supported. evolution-exchange will be completely removed when evolution=mapi provides more or less feature parity. It will not be merged.
Public Exchange servers (like Mail2web, f.i.) need OWA for access. Using only MAPI will drop Evolution from being an Exchange client of these services. Many companies are also reluctant to activate MAPI in their servers for non-local access, so OWA is still going to be used in the next future. Not supporting, IMHO, will decrease Evolution and Linux use in desktops, both home and enterprise. Outlook2007 allows also OWA (with many configuration options), so Microsoft don't seem to stop OWA access in next versions of Exchange. Please consider these situations and the above related to solve exchange-connector bug when accessing Exch2007.