Bugzilla – Bug 113097
Evolution Exchange connector hangs
Last modified: 2007-08-22 07:57:40 UTC
I set up the exchnage connector to use my exchange server folder, logged in. With varying results, I get: 1) Hang in scanning folders. 2) Hang in retrieving new items in inbox, anywhere from 10 to 60 % complete, then never changes, even after an hour. 3) Hangs when retrieving messages. cannot use this in it's current form. As a side note: Version 2.0.4 of Evolution and the exchange connector worked, slowly, but was reliable. Versions 2.1 and 2.2 broke and showed constant hanging. Version 2.3.7 also is constantly hanging. thanks Leo
Leo: Can you please provide some more info ? When hanging can you please get a stack trace with debugging symbols ? Also provide your server details. If possible the console message ? http://www.gnome.org/projects/evolution/bugs.shtml http://live.gnome.org/GettingTraces
Sorry, I don't have that machine anymore, The only one I have is Suse 9.3 with evolution 2.2 which has the same issues. Our server is just an Exchange 2000 server, pretty standard setup as far as I know. I ran it under gdb, but it didn't behave the same, it started to bring up the UI, and then hung, here is the backtrace for it: Hope this helps. (gdb) run Starting program: /opt/gnome/bin/evolution (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1094968128 (LWP 7690)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) es menu class init adding hook target 'source' (evolution:7690): camel-WARNING **: Invalid root: '/home/lstutzma/.evolution/mail/local/Inbox.ibex.index' (evolution:7690): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:7690): camel-WARNING **: block size: 1024 (1024) OK (evolution:7690): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:7690): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:7690): camel-WARNING **: flags: unSYNC (evolution:7690): camel-WARNING **: Invalid root: '/home/lstutzma/.evolution/mail/local/Drafts.ibex.index' (evolution:7690): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:7690): camel-WARNING **: block size: 1024 (1024) OK (evolution:7690): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:7690): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:7690): camel-WARNING **: flags: unSYNC (evolution:7690): camel-WARNING **: Invalid root: '/home/lstutzma/.evolution/mail/local/Outbox.ibex.index' (evolution:7690): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:7690): camel-WARNING **: block size: 1024 (1024) OK (evolution:7690): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:7690): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:7690): camel-WARNING **: flags: unSYNC (evolution:7690): camel-WARNING **: Invalid root: '/home/lstutzma/.evolution/mail/local/Sent.ibex.index' (evolution:7690): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:7690): camel-WARNING **: block size: 1024 (1024) OK (evolution:7690): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:7690): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:7690): camel-WARNING **: flags: unSYNC [New Thread 1114446768 (LWP 7704)] [New Thread 1116548016 (LWP 7705)] QPixmap: Invalid pixmap parameters QPainter::begin: Cannot paint null pixmap QPainter::setPen: Will be reset by begin() QPainter::setBrush: Will be reset by begin() QPainter::setBrush: Will be reset by begin() QPainter::setPen: Will be reset by begin() Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1094968128 (LWP 7690)] 0x40725132 in XSetTile () from /usr/X11R6/lib/libX11.so.6 (gdb) thread apply all bt Thread 3 (Thread 1116548016 (LWP 7705)): #0 0xffffe410 in ?? () #1 0x428d2408 in ?? () #2 0x00000006 in ?? () #3 0x00000000 in ?? () #4 0x410eaa56 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #5 0x4030273a in e_msgport_wait () from /opt/gnome/lib/libedataserver-1.2.so.4 #6 0x40302c33 in e_msgport_reply () from /opt/gnome/lib/libedataserver-1.2.so.4 #7 0x410e8aa7 in start_thread () from /lib/tls/libpthread.so.0 #8 0x41392c2e in clone () from /lib/tls/libc.so.6 Thread 2 (Thread 1114446768 (LWP 7704)): #0 0xffffe410 in ?? () #1 0x426d1408 in ?? () #2 0x00000006 in ?? () #3 0x00000000 in ?? () #4 0x410eaa56 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #5 0x4030273a in e_msgport_wait () from /opt/gnome/lib/libedataserver-1.2.so.4 ---Type <return> to continue, or q <return> to quit--- #6 0x40302c33 in e_msgport_reply () from /opt/gnome/lib/libedataserver-1.2.so.4 #7 0x410e8aa7 in start_thread () from /lib/tls/libpthread.so.0 #8 0x41392c2e in clone () from /lib/tls/libc.so.6 Thread 1 (Thread 1094968128 (LWP 7690)): #0 0x40725132 in XSetTile () from /usr/X11R6/lib/libX11.so.6 #1 0x41791d6b in QPainter::drawTiledPixmap () from /usr/lib/qt3/lib/libqt-mt.so.3 #2 0x41dd7355 in Keramik::GradientPainter::renderGradient () from /opt/kde3/lib/kde3/plugins/styles/keramik.so #3 0x41de5e32 in KeramikStyle::drawPrimitive () from /opt/kde3/lib/kde3/plugins/styles/keramik.so #4 0x41ddc0a8 in KeramikStyle::drawComplexControl () from /opt/kde3/lib/kde3/plugins/styles/keramik.so #5 0x415ad0f4 in drawToolButton () from /opt/gnome/lib/gtk-2.0/2.4.0/engines/libqtengine.so #6 0x415a6382 in qtengine_style_register_type () from /opt/gnome/lib/gtk-2.0/2.4.0/engines/libqtengine.so #7 0x40e7297c in gtk_paint_box () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #8 0x40045b8a in e_combo_button_new () from /opt/gnome/lib/evolution/2.2/libemiscwidgets.so.0 ---Type <return> to continue, or q <return> to quit--- #9 0x40e2281e in gtk_marshal_BOOLEAN__VOID () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #10 0x41224279 in g_closure_ref () from /opt/gnome/lib/libgobject-2.0.so.0 #11 0x412248db in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0 #12 0x41234179 in g_signal_chain_from_overridden () from /opt/gnome/lib/libgobject-2.0.so.0 #13 0x41234ff2 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0 #14 0x41235626 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0 #15 0x40f09f14 in gtk_widget_get_default_style () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #16 0x40d92a19 in gtk_container_propagate_expose () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #17 0x40d92a41 in gtk_container_propagate_expose () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #18 0x40d53c2c in gtk_button_box_set_child_size () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #19 0x40d934ad in gtk_container_forall () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #20 0x40d95635 in gtk_container_child_type () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #21 0x40f1edad in gtk_window_new () from /opt/gnome/lib/libgtk-x11-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #22 0x406a05e4 in bonobo_plug_new () from /opt/gnome/lib/libbonoboui-2.so.0 #23 0x40e2281e in gtk_marshal_BOOLEAN__VOID () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #24 0x41224279 in g_closure_ref () from /opt/gnome/lib/libgobject-2.0.so.0 #25 0x412248db in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0 #26 0x41234179 in g_signal_chain_from_overridden () from /opt/gnome/lib/libgobject-2.0.so.0 #27 0x41234ff2 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0 #28 0x41235626 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0 #29 0x40f09f14 in gtk_widget_get_default_style () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #30 0x40e1d853 in gtk_main_do_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #31 0x4113036d in gdk_window_is_viewable () from /opt/gnome/lib/libgdk-x11-2.0.so.0 #32 0x411304df in gdk_window_process_all_updates () from /opt/gnome/lib/libgdk-x11-2.0.so.0 #33 0x40f1ea0a in gtk_window_new () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #34 0x412318a6 in g_cclosure_marshal_VOID__VOID () from /opt/gnome/lib/libgobject-2.0.so.0 #35 0x41224279 in g_closure_ref () from /opt/gnome/lib/libgobject-2.0.so.0 #36 0x412248db in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #37 0x41234179 in g_signal_chain_from_overridden () from /opt/gnome/lib/libgobject-2.0.so.0 #38 0x4123513b in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0 #39 0x41235626 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0 #40 0x40d935b5 in gtk_container_check_resize () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #41 0x40d9365b in gtk_container_check_resize () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #42 0x4127b051 in g_list_push_allocator () from /opt/gnome/lib/libglib-2.0.so.0 #43 0x4127c967 in g_main_context_dispatch () from /opt/gnome/lib/libglib-2.0.so.0 #44 0x4127ece2 in g_main_context_acquire () from /opt/gnome/lib/libglib-2.0.so.0 #45 0x4127fcf7 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0 #46 0x40aa5cf0 in bonobo_main () from /opt/gnome/lib/libbonobo-2.so.0 #47 0x080641d2 in main () (gdb) Quit (gdb) Quit (gdb)
Please re-test this with SLP 10 Beta 4 and confirm again.
(In reply to comment #3) > Please re-test this with SLP 10 Beta 4 and confirm again. Is there evidence that the hangs in scanning folders, and scanning new headers in the inbox are fixed in B4?
Yes, I have tested this in Beta 4 and it doesn't hang. In fact, there are others too who aren't facing this problem. So, it would help if you could confirm this.
I can confirm. Just installed 10.0 beta4 last night. Mine seems to hang on message retrieval, most consistently just after I have deleted another message. I will attach the results of E2K_DEBUG=4 evolution >& /tmp/evo.log
Created attachment 49061 [details] E2K_DEBUG=4 output
Attachment seems to show a problem with something called D-BUS? Vo ist das? P.S. I run KDE, not Gnome.
Well, it looks to me that evolution is hanging since evolution-exchange process got killed. Can you attach gdb to evolution-exchange process when this happens and get the backtrace for it ? That should give us more clues.
I got rid of the D-BUS message by installing dbus-gtk and dbus-mono and evolution-sharp, but the exchange-storage backend is still crashing. Will try a gdb today, but I'm new to it so God only knows what will happen.
http://live.gnome.org/GettingTraces .. This has steps to get the traces. Hope that helps.
Stack Trace on latest versions: evolution-pilot-2.4.0-3.2 evolution-exchange-2.4.1-3 evolution-data-server-1.4.1-3 evolution-sharp-0.10.1-4 evolution-2.4.0-3.2 Now, If the exolution-exchange-storage does stay running long enough to connect, deleting a message will cause it to crash. Here is the gdb info: Thread 8 (Thread 1153854384 (LWP 9553)): #0 0xffffe410 in __kernel_vsyscall () #1 0x40b7fa76 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #2 0x404add3a in e_msgport_wait () from /opt/gnome/lib/libedataserver-1.2.so.4 #3 0x404ae4c3 in e_thread_busy () from /opt/gnome/lib/libedataserver-1.2.so.4 #4 0x40b7d297 in start_thread () from /lib/tls/libpthread.so.0 #5 0x415ab37e in clone () from /lib/tls/libc.so.6 #6 0x44c66bb0 in ?? () Thread 7 (Thread 1151753136 (LWP 9547)): #0 0xffffe410 in __kernel_vsyscall () #1 0x40b7fa76 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #2 0x404add3a in e_msgport_wait () from /opt/gnome/lib/libedataserver-1.2.so.4 #3 0x404ae4c3 in e_thread_busy () from /opt/gnome/lib/libedataserver-1.2.so.4 #4 0x40b7d297 in start_thread () from /lib/tls/libpthread.so.0 #5 0x415ab37e in clone () from /lib/tls/libc.so.6 #6 0x44a65bb0 in ?? () Thread 6 (Thread 1149651888 (LWP 9546)): #0 0xffffe410 in __kernel_vsyscall () #1 0x415a1482 in poll () from /lib/tls/libc.so.6 #2 0x4122557c in g_main_context_check () from /opt/gnome/lib/libglib-2.0.so.0 #3 0x41225a47 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0 #4 0x40b51e50 in link_thread_io_context () from /opt/gnome/lib/libORBit-2.so.0 #5 0x08483848 in ?? () #6 0x41280a68 in ?? () from /opt/gnome/lib/libglib-2.0.so.0 #7 0x44864458 in ?? () #8 0x41240aaf in g_static_private_free () from /opt/gnome/lib/libglib-2.0.so.0 #9 0x41240aaf in g_static_private_free () from /opt/gnome/lib/libglib-2.0.so.0 #10 0x40b7d297 in start_thread () from /lib/tls/libpthread.so.0 #11 0x415ab37e in clone () from /lib/tls/libc.so.6 #12 0x44864bb0 in ?? () Thread 4 (Thread 1146579888 (LWP 9527)): #0 0xffffe410 in __kernel_vsyscall () #1 0x40b7fa76 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #2 0x404add3a in e_msgport_wait () from /opt/gnome/lib/libedataserver-1.2.so.4 #3 0x404ae4c3 in e_thread_busy () from /opt/gnome/lib/libedataserver-1.2.so.4 #4 0x40b7d297 in start_thread () from /lib/tls/libpthread.so.0 #5 0x415ab37e in clone () from /lib/tls/libc.so.6 #6 0x44576bb0 in ?? () Thread 3 (Thread 1144478640 (LWP 9526)): #0 0xffffe410 in __kernel_vsyscall () #1 0x40b7fa76 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #2 0x404add3a in e_msgport_wait () from /opt/gnome/lib/libedataserver-1.2.so.4 #3 0x404ae4c3 in e_thread_busy () from /opt/gnome/lib/libedataserver-1.2.so.4 #4 0x40b7d297 in start_thread () from /lib/tls/libpthread.so.0 #5 0x415ab37e in clone () from /lib/tls/libc.so.6 #6 0x44375bb0 in ?? () Thread 2 (Thread 1142377392 (LWP 9525)): #0 0xffffe410 in __kernel_vsyscall () #1 0x40b7fa76 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #2 0x404add3a in e_msgport_wait () from /opt/gnome/lib/libedataserver-1.2.so.4 #3 0x404ae4c3 in e_thread_busy () from /opt/gnome/lib/libedataserver-1.2.so.4 #4 0x40b7d297 in start_thread () from /lib/tls/libpthread.so.0 #5 0x415ab37e in clone () from /lib/tls/libc.so.6 #6 0x44174bb0 in ?? () Thread 1 (Thread 1097014976 (LWP 9509)): #0 0xffffe410 in __kernel_vsyscall () #1 0x415a1482 in poll () from /lib/tls/libc.so.6 #2 0x4122557c in g_main_context_check () from /opt/gnome/lib/libglib-2.0.so.0 #3 0x41225a47 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0 #4 0x40a91c83 in bonobo_main () from /opt/gnome/lib/libbonobo-2.so.0 #5 0x0805ef70 in main ()
Stack traces are not useful :(
I would suggest to remove existing following rpms of evolution, evolution-data-server, evolution-exchange, gtkhtml2 and libsoup. Backup contents of ~/.evolution. Then remove .evolution contents. Install .evolution contents from http://ftp.ximian.com/pub/evolution-snapshot/suse-100-i586/ Update bugzilla if the problem is still existing.
Perhaps that would work if I didn't already have libsoup-2.2.6 installed, and your snapshot is trying to install 2.2.4. Shall I override the dependancy of the evolutionand evolution-data-server rpm's and install them anyhow?
I followed the above instructions. Still no fix. EVERY time I start Evolution now, I get "Application Evolution-exchange-storage has crashed unexpectedly" (as opposed to an expected crash?).
Can you paste the stack traces? Is it same as above ? Also can you start evolution-exchange-storage and evolution form seperate consoles and see if there are any related debug messages printed on the console?
Same stack trace. As soon as I realized that the snapshot wasn't fixing it, I went back to the one from apt-get (SuSE + updates).
I am not able to get any hint from those traces. I don't see any hang with 2.6 I am using. Is it possible to install debug packages? Poornima, do you have any idea where he can get debug packages from?
*** Bug 115590 has been marked as a duplicate of this bug. ***
Evolution 2.6 rpm's with debug rpm is available at http://kirk.provo.novell.com/dist/full/full-10.0-i386/suse/i586/
Getting a timeout trying to load that url
Jonathon Robison, can you try the URL? It is working for me. Poornima, any other links?
Still can't get in. However, I am now on 10.1 running the latest updates from that load. Excange connector still crashes, no rhyme nor reason. I have once again given up on using Evolution for exchange connectivity and now use an ICA client to a Citrix server.
And on 10.1 you are getting the same gdb stack?
Didn't do gdb, but did do the E2K_DEBUG. Same thing as before.
Can you try to get the gdb traces for Evolution also? The traces above doesn't give much information, I am hoping we might get some better traces.
Here's the deal folks - I have been filing bugs on this crash for well over 2 years now, on the last 3 versions of SuSE. I'm done with Evolution/Exchange, and sticking with Citrix ICA Client to get at Outlook on the Citrix server. There's only so much banging my head against a brick wall I can do before I quit. It's ALWAYS the exchange-storage back-end that crashes, one way or another. On one bug I even traced it to which sub-routine was causing the crash, and what line in the source code, but that was ignored. [hint - it was an error routine that was being fed unexpected data and the sub didn't take into account unexpected input]. I'll stay on this as a CC, just in case it gets fixed, but I can no longer help with it.
Either(In reply to comment #28) > Here's the deal folks - I have been filing bugs on this crash for well over 2 > years now, on the last 3 versions of SuSE. Thanks for your continued efforts and time. > It's ALWAYS the exchange-storage back-end that crashes, one way or > another. On one bug I even traced it to which sub-routine was causing the > crash, and what line in the source code, but that was ignored. Can you point me to it - any bugzilla entry in bugzilla.gnome.org or any older mails? > I'll stay on this as a CC, just in case it gets fixed, but I can no longer help > with it. > Thanks again for interest in getting the issue solved. However, I would request you to help me resolve this issue once for all. E2K_DEBUG gives almost *same information* for all the versions. They are helpfull in identifying any protocol issues and other communication issues. However, for solving crashes, stack traces help a lot. BTW, are you running i386 or x86_64 packages? Were you getting any of the issues resolved in Bug#189926? http://gnomebangalore.org/~vvaradha/evo-snapshots/sled-10/aug-28-2006/ has SLED10 packages, that should get installed on top of 10.1 without any error. Please Try the following: 1) Create a new user in your system. 2) Run evolution and configure your exchange account. 3) If you have FBA enabled in your setup, you will have to enter the username as "domain\username" 4) Perform various operations and report back. Note: Hope you would have installed bug-buddy, if not, please install it and it will get the traces for you in case of crashes. Just attach those traces to the bug. All the packages in the link have in-built debug symbols, so no need for installing debuginfo RPMs. Thanks again for your time and efforts.
I've installed your rpm files. Added a new mail account to evolution (did not add a new user). When I select MS Exchange, there is no place to enter a server, and the OK button is still gray. I switched to IMAP, entered the server there, then switched it back to MS Exchange. Worked fine. First tests seem fine, both email and Calendar. Will continue testing tomorrow and through to next Friday and I will let you know how it goes. P.S. What is FBA?
(In reply to comment #30) > I've installed your rpm files. > > Added a new mail account to evolution (did not add a new user). When I select > MS Exchange, there is no place to enter a server, and the OK button is still > gray. Can you attach a screenshot? Also, please verify whether you have Edit->Plugins->"Exchange Operations" enabled for any exchange related operations to work. > First tests seem fine, both email and Calendar. Will continue testing tomorrow > and through to next Friday and I will let you know how it goes. > Thanks. > P.S. What is FBA? > FBA is "Form Based Authentication" - a setting in Exchange server that when enabled, requires domain name along with user name for authentication. More information can be found in http://www.msexchange.org/tutorials/OWA2003Forms-based-Authentication-default-domain.html
OK, you were right about the plugin - it was disabled. When I started up today (after fixing the plugin yesterday) I got no errors. The setup for the exchange server is also fixed now. So far, it's still going strong. Whatever has made it fail for almost 3 years now must have finally been fixed. Now, can we get this version out into the 10.1 updates? If we can/will do that, I'll mark this as resolved.
Closing as per comment#33. Exchange connector has been improved a lot in last six months.
Feel free to report issues.