After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 317601 - Cannot authenticate to exchange server
Cannot authenticate to exchange server
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.4.x
Other All
: Normal major
: 2.5
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks: 323345
 
 
Reported: 2005-09-30 13:47 UTC by John Ehrlinger
Modified: 2006-01-04 04:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
E2K_DEBUG=4 log of ximian-connector-setup-2.4 output (2.48 KB, text/plain)
2005-09-30 13:49 UTC, John Ehrlinger
Details

Description John Ehrlinger 2005-09-30 13:47:41 UTC
Please describe the problem:
When creating new account (within evolution or ximian-connector-setup-2.4,
cannot authenticate to create account. 

Error dialog:

Could not authenticate to the Exchange server.
Make sure the username and password are correct and try again.

No problem logging into web interface with same uname passwd. Either
<domain>\<uname> or <uname>@<domain> get same results.

Steps to reproduce:
Enter OWA, uname, passwd in xcs form. Click forward, error dialog comes up.

or

Add new exchange account, attempt to authenticate, fails with same message.

Actual results:


Expected results:


Does this happen every time?
Yes.

Other information:
Though we have had users in the same domain, install actually connect. I then
copied their .gconf/apps/evolution/mail/%gconf.xml entry into mine, and edited
username information. Still does not authenticate.

Attempt setting auth=Basic and auth=Plain and both fail.
Comment 1 John Ehrlinger 2005-09-30 13:49:29 UTC
Created attachment 52853 [details]
E2K_DEBUG=4 log of ximian-connector-setup-2.4 output
Comment 2 William Lovaton 2005-12-23 17:09:41 UTC
Well, I sort of have the same problem when I am trying to create an exchange account for the first time using the wizard.  I am using evolution-2.5.3-1 from Fedora Devel (as of 23 Dec 2005) on a VMWare 5.5.1 setup.

I give my user name and the OWA server, eg: http://<owa-server>/exchange/ (Note that the Auth type menu doesn't appear here) and then push the "Authenticate" button, the password dialog appears, enter the password, hit "Ok" and I get the following error:
   "Could not configure Exchange account because 
   an unknown error occurred. Check the URL, 
   username, and password, and try again."

Note that when I try to hit "Authenticate" again just after the previous error message I get the following error:
   "Could not locate server .
    
    Make sure the server name is spelled correctly and try again."

Trying again after this gets me back to the first error message.

In the end, I can make it work: I have to set the "Server Type" as "None" in the wizard and follow the rest of the setup.  Then in Evolution main window go to Edit -> Preferences -> Mail Accounts -> [Account item] -> Edit -> Receiving Email.  Once here, change the Server Type from "None" to "Microsoft Exchange" (note that this time I get the Auth type menu not present in the wizard), try moving the Auth type menu, restart evolution. It works now! it asks my password and I can see my mails.

May be this is not the same problem but it's very close.

BTW, evolution-alarm-notify hangs when started the first time hogging the CPU very badly.  Then it crash when adding the Connector meetings for notification but I should search for the respective bug reports.


-William
Comment 3 Sushma Rai 2006-01-02 08:23:44 UTC
John Ehrlinger,

do you have a set up where your user name and mail box path are different?
if yes try the url https://server-ip/exchange/<mail box path>.

also please try to set E2K_DEBUG=4 and run Evolution from that console 
and create account using evolution's account setup dialog
(edit->preferences->add).

William Lovaton,
for the evolution-alarm-notify hang please file a seperate bug, with the 
gdb stack traces of evolution-alarm-notify process when it hangs.
Comment 4 John Ehrlinger 2006-01-03 17:03:17 UTC
Actually, I solved my problem with a password change. I guess the authentication doesn't like the '_' character? Once I used a password without the '_' the system authenticated fine.

Comment 5 Sushma Rai 2006-01-04 04:52:05 UTC
Ok thanks. I am closing this bug.
For the _ character in password, I am updating #255726.