Evolution Exchange connector : Cannot connect to server, URL error?

Bug #209438 reported by Naran K Patel
46
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution-exchange (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: evolution

I've fresh install of Hardy and copying my exchange folder to new home, setting up my exchange account with same settings as before now doesn't work, it complains, "Unable to connect to server" , "Error in URL"? I've checked my settings from before, I have the https://email.blah.com/exchange as my OWL url and domain\username as my login name, this used to work fine. Not sure what the problem is now. I'm used Hardy Beta 4 with latest updates applied. This makes the upgrade unuseable and for me email is extremely important or I have to drop the distribution release!

ProblemType: Bug
Architecture: i386
Date: Sun Mar 30 15:00:54 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: fglrx
Package: evolution 2.22.0-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
Uname: Linux 2.6.24-12-generic i686

Tags: apport-bug
Revision history for this message
Naran K Patel (narankpatel) wrote :
Revision history for this message
Naran K Patel (narankpatel) wrote :

Above should read copying my .evolution directory to my home.

Revision history for this message
David Staudt (dstaudt-usa) wrote :

Experiencing identical problem. Using Cisco vpn via vpnc plugin for network manager to connect to https OWA server.

Revision history for this message
james734 (james734) wrote :

Same problem here. I just upgraded installed 8.0.4 and cannot connect to Exchange. Get error when pressing the authenticate button. This is using the same settings I used in 7.10 and openSUSE 10.3.

Revision history for this message
james734 (james734) wrote :

Looks like might be a problem with authentication. I have a packet capture and I see a DNS query for a authentication server. Which all looks good. I then see a Kerberos error error KRB5KRB_ERR_RESPONSE_TOO_BIG. Of course I don't see a bunch of these so I'm not sure if that was just blip or what. But It looks like maybe the authentication credentials aren't being passed correctly. I do see what looks a few auth attempts. Of course I'm connecting to a HTTPS server so I cannot see any more information.

Again this was working in 7.10 and openSUSE 10.3. My Hardy install was a fresh install so It not a upgrade/update issue.

Revision history for this message
james734 (james734) wrote :

Okay. Turned on some debug. E2k_Debug=4 doesn't produce anything.

volution Exchange Storage up and running
E2K_DEBUG=4
> GET /exchange/jarosenf/ HTTP/1.1
> Soup-Debug-Timestamp: 1207362670
> Soup-Debug: SoupSessionSync 1 (0x80df8b8), SoupMessage 1 (0x80b0900), SoupSocket 1 (0x80eb608)
> Host: email.XXXXXX.com
> Accept-Language: en-US, en
> User-Agent: Evolution/2.22.0

But Camel_Debug=all produces some errors.

>CamelException.set(0x83a21ac, 2, 'Could not authenticate to server. (Password incorrect?)
>
>')
>Thread b5830b90 >
>Get folder info(0x836ca88:exchange://XXXXX%5cjarosenf;<email address hidden>/, '<null>') =
>< b5830b90 >
>CamelException.set(0x85abb84, 2, 'Could not authenticate to server. (Password incorrect?)

The password is correct as I use it everyday logging into other corp resources.

Revision history for this message
Praveen (ప్రవీణ్) Garlapati (గార్లపాటి) (praveengarlapati) wrote :

I can confirm the defect on hardy.

The evolution build from the Gutsy used to work fine. After the upgrade to hardy evolution never connected to exchange server. (Even tried a delete and fresh configuration)

The error I get is "Could not connect to server. Make sure the URL is correct and try again."

Even the latest updates as of today didn't solve the issue.

Revision history for this message
Matthew Tighe (tighem) wrote :

Can you

Revision history for this message
redwing629 (robbins629) wrote :

I also was using evolution with Ubuntu 7.10 but noticed that after some updates last weekend (April 26, 2008), don't ask me what they were, evolution could no longer connect to my exchange server. Same errors as reported here (could not connect to server). So I did some testing...In Vmware I created a fresh install of Ubuntu 7.10 with the default Evolution version 2.12.0 and all was fine. I then applied an update selecting only the Evolution updates which took the program up to version 2.12.1. All was fine. I believe that the weekend I had problems perhaps evolution was updated to the current 2.12 version of 2.12.3? Not sure but know that the current Evolution version of 2.20.1 is not working with Exchange. Please e-mail me if a fix is found and I will do the same to this location...robbins629 at aim dot com

Revision history for this message
msegal (mark-markanddonna-deactivatedaccount) wrote :

confirmed here in hardy final. Can not, I am getting a "could not connect to server" on account setup. works fine in firefox.. used to work in 7.10

Revision history for this message
menderes (menders) wrote :

Having the same issue with Hardy Heron. Oddly enough, I was playing around with Ettercap and noticed that if the connection was man-in-the-middle'd it worked without a problem.

$ E2K_DEBUG=4 evolution
e-data-server-ui-Message: Key file does not have key 'exchange:__*****;auth_Basic@*****.com_'
> GET /exchange/*****/ HTTP/1.1
> Soup-Debug-Timestamp: 1209669488
> Soup-Debug: SoupSessionSync 1 (0x85c8f10), SoupMessage 1 (0x83c86c8), SoupSocket 1 (0x85b2ee0)
> Host: *****.com
> Accept-Language: en-US, en
> User-Agent: Evolution/2.22.1

In Wireshark I see the server closing the connection immediately after the SSL Client Hello which is ACK'd. Don't know if this is of any help, but feel free to let me know if I can assist with any debugging.

Revision history for this message
msegal (mark-markanddonna-deactivatedaccount) wrote :

Some more details, ran evolution in debug mode, here is a copy of the file.

--
BBDB spinning up...
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have key 'exchange:__userl;<email address hidden>com_'
--

Seems as if evolution can not access they keyring for the exchange plugin only.. thoughts?

Revision history for this message
Matt (ubuntu-shop) wrote :

Still facing this issue in Hardy and had to regress to Gutsy.

Revision history for this message
Bryan Moore (moore-bryan) wrote :

compiling from cvs as per http://www.go-evolution.org/Compiling_Evolution_from_CVS solved this issue for me...

Lou Ruppert (louferd)
Changed in evolution-exchange:
status: New → Confirmed
Revision history for this message
Sebastian Martinez (tychocity) wrote :

confirmed same problem in intrepid ibex.

Revision history for this message
JasonBoissiere (jason-boissiere-gmail) wrote :

I hit this problem, or something very similar, immediately after changing my domain password. This discussion on the ubuntu forums proved useful to me;
http://ge.ubuntuforums.com/showthread.php?t=866735
Particularly the 7th entry talking about duplicated usernames in the OWA URL. I ran "EDK_DEBUG=5 evolution" and confirmed the same malformed URL in my output. Something like;
GET exchange/USERNAME/USERNAME HTTP/1.1
at the very start of the debug output.
Then "gconftool-2 --shutdown && evolution --force-shutdown" followed by editing ~/.gconf/apps/evolution/mail/%gconf.xml to change the "exchange/USERNAME" entries (I had 2) into plain "exchange" has resolved my problem. I'm now authenticating with exchange again.
Looks like evolution is duplicating the username when it builds the OWA URL, for some reason.

Revision history for this message
Timothy Alexander (dragonfyre13) wrote :

@Jason

What also works is going in and removing the current "Mailbox Name". Then, you simply click authenticate, it will fill it in (looks exactly the same to the user) but will also recreate that file. It builds it correctly for me if I do that. I did have the issue after changing my domain password though.

Revision history for this message
Daniel Castro (castromd) wrote :

So I am having this exact issue. The difference with me is that I am configuring an account from scratch, so the work arounds mentioned about removing the mailbox, and the problem about the evolution UI sending the username two times and all that will not work for me.
Is there another work around? Could I edit my setting on a file? Where is that file? Could someone give me an example file?
Thanks!

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try the same with Karmic or Jaunty ? Thanks in advance.

Changed in evolution-exchange (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → Low
Revision history for this message
MarkD (mark-daglish) wrote :

I'm still having this problem, but have switch to OpenSuSE 11.1 some time ago. The connection still doesn't work on version 2.27.92 from this repository: http://download.opensuse.org/repositories/GNOME:/Evolution:/snapshots/

Revision history for this message
Daniel Castro (castromd) wrote :

I stopped using Evolution several months ago. Too slow. And the exchange connector was always giving trouble. I use Thunderbird with DavMail now and it's much better.

Revision history for this message
MarkD (mark-daglish) wrote : Re: [Bug 209438] Re: Evolution Exchange connector : Cannot connect to server, URL error?

Daniel Castro wrote:
> I stopped using Evolution several months ago. Too slow. And the exchange
> connector was always giving trouble. I use Thunderbird with DavMail now
> and it's much better.
>
>
Thanks for the DavMail tip - very helpful.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for evolution-exchange (Ubuntu) because there has been no activity for 60 days.]

Changed in evolution-exchange (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.