Email 4.0.1 "Waiting for sync" on corporate Exchange/Activesync

[david-simons]

Update June 5th 2012: I ended up using Enhanced Email (http://enhancedemail.net/viewforum.php?f=34), which actually is much nicer than the stock email client, and works like a charm with my Exchange and IMAP servers, and nicely integrates into the Android Calendar and Contacts. For $9.99, in Google or Amazon store, I recommend this as a satisfactory solution!

Update June 1st 2012: This issue is NOT resolved. Upgrading to 4.0.4 did not solve this issue (for me).

Update May 5th 2012: This issue is NOT resolved, and still bugging multiple clients. A "Repair phone" (ie. reinstall ICS via Sony PC Companion) action did NOT resolve this issue!

Happily upgraded my Sony-Ericsson Arc S to Android 4.0.3 yesterday.

But:

When using the stock email/calendar/contacts client 4.0.1 to connect to my corporate Exchange account (Office 365), I get stuck after a succesful account set-up, during sychonization. Exchange Services is vesion 4.1.

The email client hangs on "Waiting for sync / Syncing" endlessly, despite all my attempts

Symptoms:

- Account set-up correctly, as the Exchange server reports a succesful phone connection, but no succesful sync completion

- Another account, with IMAP, works flawlessly

- Using RoadSync 3rd party client also works flawlessly

- Accepted security policy from Exchange server

- Enabled auto-synchronization for the Corporate account, for Calendar, Contacts, and Email. "Sync now" gives _no_ error.

Welcome any help! (just don't tell me to reset my phone)

David

Message was edited by: david-simons

[david-simons]

I think I've traced this down to an error in the ActiveSync Provisioning Protocol session, when the client (Android) is retrieving the server security Policy settings.

- The device information is communicated properly

- There is Partial success (at least the PIN was enabled) in applying the security policy

- But before the FolderHierachy can be started to sychronize email:

- The provisioning phase erroneously ends by the server saying "Status 5 - The client is acknowledging the wrong policy key"...

[Johan]

Thank you for great feedback and info, I'm investigating this and so our my developer colleagues. I hope that I can back to you soon with information on what is causing this problem.

[david-simons]

Appreciate this being picked up!

I think the current Exchange client does not implement all required Exchange security policies, and therefore is denied access to the email folders, contacts, and calendar data.

Certainly appreciated if this can be addressed, since I do not want to fall back to using 3rd party clients

Thank you!

For the technical team, here's the Exchange server log (anonymized):

-----------------
Log Entry: 0
-----------------

RequestTime :
04/26/2012 02:06:24

ServerName :
011-DB3MMR1-007

AssemblyVersion :
14.01.0355.003

Identifier :
77B444B5

RequestHeader :
POST /Microsoft-Server-ActiveSync/default.eas?Cmd=FolderSync&User=&DeviceId=&DeviceType=Android HTTP/1.1
Connection: Keep-Alive
Content-Length: 13
Content-Type: application/vnd.ms-sync.wbxml
Accept-Encoding: gzip
Authorization: ********
Host:
User-Agent: Android/4.0.3-EAS-1.3
MS-ASProtocolVersion: 14.1
X-MS-PolicyKey: 0

RequestBody :


0

AccessState :
Blocked

AccessStateReason :
Policy

ResponseHeader :
HTTP/1.1 200 OK
MS-Server-ActiveSync: 14.1

ResponseBody :


144

ResponseTime :
04/26/2012 02:06:24

-----------------
Log Entry: 1
-----------------

RequestTime :
04/26/2012 02:06:44

ServerName :
011-DB3MMR1-007

AssemblyVersion :
14.01.0355.003

Identifier :
341ACBDD

RequestHeader :
POST /Microsoft-Server-ActiveSync/default.eas?Cmd=Provision&User=&DeviceId=&DeviceType=Android HTTP/1.1
Connection: Keep-Alive
Content-Length: 100
Content-Type: application/vnd.ms-sync.wbxml
Accept-Encoding: gzip
Authorization: ********
Host:
User-Agent: Android/4.0.3-EAS-1.3
MS-ASProtocolVersion: 14.1
X-MS-PolicyKey: 0

RequestBody :



 
   LT18a
   Android 4.0.3
   Android/4.0.3-EAS-1.3
 


 
   MS-EAS-Provisioning-WBXML
 

AccessState :
Allowed

AccessStateReason :
Global

ResponseHeader :
HTTP/1.1 200 OK
MS-Server-ActiveSync: 14.1

ResponseBody :



  1

1

 
   MS-EAS-Provisioning-WBXML
   1
   2325609562
  
 

ResponseTime :
04/26/2012 02:06:44

-----------------
Log Entry: 2
-----------------

RequestTime :
04/26/2012 02:06:45

ServerName :
011-DB3MMR1-007

AssemblyVersion :
14.01.0355.003

Identifier :
102AA6C7

RequestHeader :
POST /Microsoft-Server-ActiveSync/default.eas?Cmd=Provision&User=&DeviceId=&DeviceType=Android HTTP/1.1
Connection: Keep-Alive
Content-Length: 60
Content-Type: application/vnd.ms-sync.wbxml
Accept-Encoding: gzip
Authorization: ********
Host:
User-Agent: Android/4.0.3-EAS-1.3
MS-ASProtocolVersion: 14.1
X-MS-PolicyKey: 0

RequestBody :



 
   MS-EAS-Provisioning-WBXML
   2325609562
   2
 

AccessState :
Allowed

AccessStateReason :
Global

ResponseHeader :
HTTP/1.1 200 OK
MS-Server-ActiveSync: 14.1

ResponseBody :


1

 
   MS-EAS-Provisioning-WBXML
   1
   123379956
 

ResponseTime :
04/26/2012 02:06:45

-----------------
Log Entry: 3
-----------------

RequestTime :
04/26/2012 02:06:45

ServerName :
011-DB3MMR1-007

AssemblyVersion :
14.01.0355.003

Identifier :
504828A4

RequestHeader :
POST /Microsoft-Server-ActiveSync/default.eas?Cmd=Provision&User=&DeviceId=&DeviceType=Android HTTP/1.1
Connection: Keep-Alive
Content-Length: 59
Content-Type: application/vnd.ms-sync.wbxml
Accept-Encoding: gzip
Authorization: ********
Host:
User-Agent: Android/4.0.3-EAS-1.3
MS-ASProtocolVersion: 14.1
X-MS-PolicyKey: 0

RequestBody :



 
   MS-EAS-Provisioning-WBXML
   123379956
   1
 

AccessState :
Allowed

AccessStateReason :
Global

ResponseHeader :
HTTP/1.1 200 OK
MS-Server-ActiveSync: 14.1

ResponseBody :


1

 
   MS-EAS-Provisioning-WBXML
   5
 

ResponseTime :
04/26/2012 02:06:45

[#5]

I seem to have the same problem. The strange thing is that it worked before the upgrade and after the upgrade to 4.0.3.But after a factory reset after the upgrade, it is not working any more.

[Anshu]

I seem to have the same problem. The strange thing is that it worked before and after the upgrade to 4.0.3.

But after a factory reset after the upgrade, it is not working any more and giving "waiting for sync".

Tried reset many times but didn't helped.

[Anshu]

I am also having the same problem. The strange thing is that it worked before and after the upgrade to 4.0.3.

But after a factory reset after the upgrade, it is not working any more and giving "waiting for sync".

Tried reset many times but didn't helped.

Details of the software are:-

Android Version:- 4.0.3

Kernel Version:- 2.6.32.9-perf

Build No.:- 4.1.A.0.562

[david-simons]

Update: turns out the Partial implementation of the Security Policy is NOT the issue, since I now do get access, but still cannot synchorize ("Waiting for synchronization"):

Device OS:	Android 4.0.3
Device language:	Not Available
User agent:	Android/4.0.3-EAS-1.3
Access state:	Access Granted
Access set by:	Global Permissions
Policy applied:	ActiveSync Policy - Partially applied
Policy updated:	28-Apr-12 07:58
ActiveSync version:	14.1

So, I think we're down to a flaw in the EAS (Exchange Active Sync) client on the Sony Arc S (Android 4.0.3) with Exchange 2010

[Rock33]

I'm having the exact same problem on my Xperia Ray.

- 4/30 AM:  Exchange Active Sync was working fine.

- 4/30 PM:  Upgraded to ICS - Exchange Active Sync no longer worked.  Kept getting security errors

- 5/1 AM:  Deleted Exchange account - reloaded the Exchange account.  Account verified on Exchange server - no emails or contacts showing on mobile device

I found this link on Office365.  Not sure if it is related or not.

http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-cl...

[david-simons]

Thanks for weighing in. However, I don't think the cross-site-redirection is the problem, and none of the suggested solutions in that thread solved the issue for me...