this should be filed under the Connector product

jamie: i checked in exchange server 2003 with FBA enabled, it works fine. Can
you confirm if FBA is enabled in your exchange server ? .I will recheck this in
exchange 2000. Does this ask for password twice ??. I dont see this problem of
'OK' button disabled. If FBA is enabled in 'username' field type
'domainname\username'(i.e in my case blr.novell.com\pnayak). 

That you for looking at this.  I will see if FBA is enabled on my Exchange
server.  It might be hard though, my companies IT department thives on obscurity
and makes it hard to get to someone who knows what they are doing.  My company
uses - so far - Exchange 2000. 

According to our Exchange person (who did not know what FBA was) OWA is working
fine there for I should have no problems.  Again my Exchange server is Exchange
2000.  We may have a werid set up though, OWA is running on a front-end server
that passes requests to a users real Exchange server.  The Exchange Admin says
OWA will not be enabled on the Exchange servers due to security reasons.  I can
connect with Evolution 2.0.4-4 (connector-2.0.4-1) without any problems.

When I press "Authenticate" the first time a window will prompt "Enter
password for domain\login_name".  I enter my user name (domain/username) and my
password.  At this point the authentication window goes away however the "Ok"
buttom is still grayed out - no error message

When I press "Authenticate" a second time the window will prompt "Enter
password for First_Last".  After typing my password again I get an error
window that reads

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

You may need to specify the Windows domain name as part of your username
(eg, "MY-DOMAIN\First_Last").
>>>>>>

However that is what I entered.  Is there a way to turn on debugging?

If you give the same user name and OWA url as you
provide in OWA (browser), should work.

Can you try 2.2.3?

can you please update the bug with 2.2.3.
Enter the user name and OWS url  as you enter in 
Outlook Web Access (in browser).

I am getting the exact same behavior with Connector 2.4.  I have tried all possible combinations with no luck.

Any clues anyone?

Carlos,

Try using 2.4.2 (or 2.5.91, developement version)

Set environment variable E2K_DEBUG=4 and run Evolution from that console
and try to create exchange account.
Get the traces when it fails to authenticate. 

Hi Sushma,

I installed SUSE 10.1 Beta 9 which contains Evolution 2.6 and I am still having the same problem.  I have tried to setup the E2K_DEBUG=4 environment variable but it is not giving me any output.  I am sure that I must be doing something wrong.  Do you have any instructions on how I can do this?    I have followed the steps in http://linuxart.com/projects/evolution/bugs.shtml and I am still not able to get any feedback.

Thank you for your help.

Actually, it seems that I did set the E2K_DEBUG=4 parameter right.  I tried to "trick" the account creator by doing a pass configuring another account type (IMAP) and before hitting Finish, I went back and changed it to Exchange.  This allowed me to complete the wizard but obviously it didn't setup the Exchange account right (for more on this see bug 331337).  Once that I was in Evolution, I was able to see my personal folder stored in Exchange, I was able to see my Out Of Office message setup on the server, so there is good communication between Evolution and the Exchange Server, the only problem is that the initial account creator wizard is not allowing me to continue when I click on the Authenticate button (as described in this thread).  The E2K_DEBUG doesnt seem to display any information at the account creation time, it displays once that the connector has established a connection with the Exchange server.

I hope it is not too confusing.  Having said all this, what should I do next?

Thanks,
Carlos

(In reply to comment #9)
> Hi Sushma,
> 
> I installed SUSE 10.1 Beta 9 which contains Evolution 2.6 and I am still having
> the same problem.  I have tried to setup the E2K_DEBUG=4 environment variable
> but it is not giving me any output.  I am sure that I must be doing something
> wrong.  Do you have any instructions on how I can do this?    I have followed
> the steps in http://linuxart.com/projects/evolution/bugs.shtml and I am still
> not able to get any feedback.
> 
> Thank you for your help.
> 

Hi again,

After some playing around with the wizard, at some point I was able to see the following error:

** (evolution-exchange-storage:7409): WARNING **: Unexpected kerberos error -1765328164

Does this means anything to you?  Coult it be that the connector is having some issue with kerberos and that is preventing the wizard from allowing me to move forward and click on continue?

-CC

(In reply to comment #8)
> Carlos,
> 
> Try using 2.4.2 (or 2.5.91, developement version)
> 
> Set environment variable E2K_DEBUG=4 and run Evolution from that console
> and try to create exchange account.
> Get the traces when it fails to authenticate. 
> 

Carlos,

Thanks for providing the details.
The kerberos error doesn't help much.

While creating the account, you need to set E2K_DEBUG=4
for *Evolution* process and not for evolution-exchange-storage.
The link http://gnome.org/projects/evolution/bugs.shtml says
how to do it with evolution-exchange-storage process.
Just confirming that your are doing it right.

Created attachment 63745 [details]
E2K_DEBUG=4 log file

Here is the log file that you requested.  For security purposes, I have masked the servername with <hostname> and the username with <username>

Something I just noticed is that I enter the username with the form <domain>\<username> but when reviewing the logs all I see is /exchange/<username>.  I don't see the domain name anywhere mentioned in the log, maybe that is the problem?

Thanks,
Carlos 

(In reply to comment #13)
> Created an attachment (id=63745) [edit]
> E2K_DEBUG=4 log file
> 
> Here is the log file that you requested.  For security purposes, I have masked
> the servername with <hostname> and the username with <username>
> 

Carlos,
/exchange/<username> is the path and it is correct.

Looks like the debug log file is not complete,
From whatever is there, for your credentials, server is sending
a "401 Unauthorized" response.
See http://support.microsoft.com/?kbid=902160.

Once again confirming, accessing the account using the same
URL, username and password works in OWA ?

Carlos, Jamie, any news on this? Can you please answer Sushma's question? Thanks in advance.

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!