Bug 6345 - (int-148594) First Synchronization between N900 and Exchange 2007 Server fails
(int-148594)
: First Synchronization between N900 and Exchange 2007 Server fails
Status: NEW
Product: Synchronization
Mail for Exchange
: 5.0/(1.2009.42-11)
: N900 Maemo
: Low major with 20 votes (vote)
: ---
Assigned To: unassigned
: activesync-bugs
:
:
:
:
  Show dependency tree
 
Reported: 2009-11-26 19:40 UTC by Andre Klapper
Modified: 2014-03-12 15:01 UTC (History)
11 users (show)

See Also:


Attachments
syslog (101.35 KB, text/plain)
2009-11-30 19:53 UTC, massimo.bilvi
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description Andre Klapper (reporter) maemo.org 2009-11-26 19:40:02 UTC
+++ This bug was initially created as a clone of Bug #5597  +++
Splitting reports about Exchange 2003 and supported Exchange 2007



SOFTWARE VERSION:
N900 see above
Exchange Server 2007

INFORMATION TO REPRODUCE THE PROBLEM:
I only selected E-Mail as sync source (but it happens also if I try to
synchronize calendar and contacts the same way).

During the first synchronisation the progress bar fills up to more or less 50%
but the it stops and an error message occours:
"Fehler bei der Kommunikation mit dem Exchange Server" (English it should be
something like "Error during the communication with the exchange server").

REPRODUCIBILITY:
always



ACTUAL OUTCOME:
"Error in communication with Exchange server." popup

--- Comment 23 ---
SCREENSHOT: https://bugs.maemo.org/attachment.cgi?id=1620&action=view

--- Comment 25 ---
I have the same problem with an exchange 2007 with the same error as comment
#23 from Sami Lavikko

--- Comment 31 ---
https://bugs.maemo.org/attachment.cgi?id=1633&action=view
Logfile from Active Sync to Exchange 2007
Server uses the protocol 12.0, not 12.1.
Comment 1 massimo.bilvi 2009-11-28 16:17:13 UTC
SOFTWARE VERSION:
N900 Version 1.2009.42-11
Exchange Server 2007

INFORMATION TO REPRODUCE THE PROBLEM:
I only selected E-Mail as sync source (but it happens also if I try to
synchronize calendar and contacts the same way).

During the first synchronisation the progress bar immediately stops and an
error message occours: "Exchange account disabled. Access refused."

REPRODUCIBILITY:
always

ACTUAL OUTCOME:
"Exchange account disabled. Access refused."

I work in a big corporation and even the cheapest Nokia E-Series works like a
charme.
Comment 2 Chris F 2009-11-30 11:08:54 UTC
Same problem as comment #1 on Exchange 2003.
Comment 3 massimo.bilvi 2009-11-30 19:53:40 UTC
Created an attachment (id=1646) [details]
syslog 

Here my /var/log/syslog. It seems that I receive an HTTP 403 error from the
Exchange Server.
Comment 4 Vitaly Repin 2009-11-30 20:56:13 UTC
Does your company allows "non-provisionable devices"?  Maemo Mfe is such a
device.
Comment 5 massimo.bilvi 2009-11-30 22:12:14 UTC
I need to ask to the server administrator. Anyway Nokia E-Series and IPhone
work flawlessly with MfE.
Comment 6 massimo.bilvi 2009-11-30 22:41:53 UTC
Android devices do not work with our Exchange Server.
Comment 7 Chris F 2009-11-30 23:15:21 UTC
(In reply to comment #6)
> Android devices do not work with our Exchange Server. 
> 
TouchDown from NitroDesk worked just fine with Exchange 2003 on my G1. They
appeared to have thought it through (you had to enter your device code) but
you;d expect that from a global giant like NitroDesk.
Comment 8 Vitaly Repin 2009-11-30 23:17:41 UTC
(In reply to comment #7)
> (In reply to comment #6)
> > Android devices do not work with our Exchange Server. 
> > 
> TouchDown from NitroDesk worked just fine with Exchange 2003 on my G1. They
> appeared to have thought it through (you had to enter your device code) but
> you;d expect that from a global giant like NitroDesk.


It is not about Exchange 2003 stuff.  Exchange 2003 is not supported currently.

But it looks like thisis about non-provisionable devices.
Comment 9 massimo.bilvi 2009-11-30 23:24:16 UTC
I think that Nokia must address this problem. It's impossible that a high-end
device like the N900 doesnt' support fully the MfE protocol. The client
installed with the E-Series works like a charm. Is it possible for Nokia to
release the source code of the Series 60 client to be merged in the Maemo mail
client?
Comment 10 Vitaly Repin 2009-11-30 23:36:27 UTC
(In reply to comment #9) Is it possible for Nokia to
> release the source code of the Series 60 client to be merged in the Maemo mail
> client?

your joke is good.  if it was not a joke, than let me remind you that linux and
symbian are different animals.  very different.  and we are talking about
provisioning than this is very platform-specific.
Comment 11 massimo.bilvi 2009-11-30 23:47:11 UTC
I know that linux and symbian are very different OS but I think that, a part of
some SO & hardware-specific code, porting the C++ code is not a so much
difficult task to accomplish. We are talking about the MfE protocol and not of
direct programming the PowerVR GPU... :D
Comment 12 Andre Klapper (reporter) maemo.org 2009-12-01 00:13:48 UTC
Can we please keep this on-topic? Remember that a bugtracker is not a forum.
Thanks everybody! :-)
Comment 13 Chris F 2009-12-01 00:47:42 UTC
> It is not about Exchange 2003 stuff.  Exchange 2003 is not supported currently.
I understand Exchange 2003 is not supported but my current problem appears
consistent with this Exchange 2007 problem.

> But it looks like thisis about non-provisionable devices.
> 
I assume (but cannot currently check) that my server does not allow
non-provisionable devices. I know that it does "Allow simple password" because
that's all I had on my HTC G1 and HTC TYTN II before that. I don't know whether
they were any more 'provisionable' than that.

(For anyone looking for background on this subject, I found this interesting:
http://www.thestandard.com/news/2009/09/24/how-avoid-smartphone-exchange-policy-lie?page=0%252C1)
Comment 14 olaf slazak l√łken 2009-12-07 12:53:15 UTC
did not work for me at first. Than i changed the location from Norway to
Finland.
And .. it works perfectly.. Strange :)
I have tried this 3 times just to be shure.
Comment 15 Sim 2010-02-17 06:02:02 UTC
(In reply to comment #1)

> During the first synchronisation the progress bar immediately stops and an
> error message occours: "Exchange account disabled. Access refused."

I unfortunately also have this problem.  In the log, it indicates a HTTP Error
403 is being thrown.

I do not know if our server requires provisional devices enabled or not, but it
is infeasible for our IT to change this (large organization).  Is there any way
to fake this setting client side?  ;)
Comment 16 Andre Klapper (reporter) maemo.org 2010-06-30 14:12:26 UTC
(In reply to comment #15)
> I unfortunately also have this problem.

Exchange 2007 server?
Comment 17 Kym 2010-07-12 13:15:17 UTC
PR 1.2 (10.2010.19-1) does not fix the Mfe 2003 issue.

443 -  error. either the exchange server requires a secure connection or
account is disabled

80 - can not connect to Exchange, check that account settings are correct.

Whats the deal with PR1.1 supporting mfe 2003 and then newer update NOT?!!
Comment 18 Andre Klapper (reporter) maemo.org 2010-07-12 13:49:44 UTC
(In reply to comment #17)
> PR 1.2 (10.2010.19-1) does not fix the Mfe 2003 issue.

Offtopic as this report is about 2007. Please don't post unrelated comments.
Comment 19 Raghav 2010-07-28 09:17:34 UTC
Same issue here. Any updates on fix?
Comment 20 Nell 2010-08-08 21:30:16 UTC
hi all... i am also having the same problems... i am trying to sync my work
email but getting exchange account disabled access refused... i tried a nokia
5800 and it works just fine... i got this phone for just a week and can't use
my n900 for work emails... i am getting frustrated... i am using pr 1.2
Comment 21 Andre Klapper (reporter) maemo.org 2010-08-09 11:32:44 UTC
(Please avoid "me too" comments as they create bugmail - click "Vote for this
bug" instead. Thanks!)
Comment 22 Shashi 2010-08-13 23:01:55 UTC
Please help and provide some resolution, if somebody has any.
Comment 23 azim 2014-03-12 15:01:58 UTC
Considering Maemo is obsolete as well as Ex2007, might as well kill this bug?
Glad to see the Maemo community come together to fix this one </sarcasm>