No sync with EAS14 ...
 
Notifications
Clear all

No sync with EAS14 after upgrade to 1.8.11

1 Posts
1 Users
0 Reactions
359 Views
(@stsimb)
Posts: 20
Topic starter
 

Our zimbra installation is as follows:
Zimbra 8.0.4 OSE, ZeXtras 1.8.11, CentOS 6 x86_64, 17 Zimbra servers of which 9 are mailbox servers.

We run ZeXtras 1.8.10 until yesterday, and we had ZxMobile EAS14 beta enabled for some specific users.
After the upgrade to 1.8.11 today, some people complained about ActiveSync not working of their devices.

sync.log showed the following:
2013-10-23 09:10:52,784 INFO [qtp1305251747-12668: https://10.24.31.31:443/Microsoft-Server-ActiveSync?User=gstag&DeviceId=ApplDLXFKTB0DFJ2&DeviceType=iPad&Cmd=Ping ] [tid=12668;] sync - ZxMobile Handler: EAS Version '14.1' not available or disabled.
2013-10-23 09:11:20,867 [qtp1305251747-12681: https://10.24.31.31:443/Microsoft-Server-ActiveSync?Cmd=Sync&User=ccha&DeviceId=SEC11ECDF0C05010&DeviceType=SAMSUNGGTI9195 ] info ZxMobile Handler: EAS Version '14.1' not available or disabled.

We did not have this behaviour with 1.8.10, and as it turned out, after upgrading to 1.8.11 only EAS25 was enabled.

[zimbra@zm-mbox-01 log]$ zxsuite mobile getProperty

ZxMobile_EAS25 true (true)
ZxMobile_EAS120 false (false)
ZxMobile_EAS121 false (false)
ZxMobile_EAS140 false (false)
ZxMobile_EAS141 false (false)

I turned them all to true and most of our problems went away.

Special case was one user (ccha) that had a SAMSUNG device.

Changelog for 1.8.11 states "Added a workaround for a client issue that could cause Samsung devices to duplicate all emails in EAS14 mode. All devices registering as "*SAMSUNG*" (e.g. using the stock Samsung client or a modified version of such) are now forced to use version 12.1 of the EAS protocol instead of version 14.1."

So user "ccha" with was using EAS 14.1 and a SAMSUNG device, thus he should be automatically downgraded to 12.1 after the upgrade, but this didn't happen.
I removed the beta flag from his account, but the admin page kept reporting 14.1 in EAS version for his Samsung device (his iPad dropped to EAS 2.5).
His sync did not work, until he actually deleted the account from his Samsung device and then added it again (uses EAS 12.1 now).

I suggest that during an upgrade you take care of devices that use a higher version and you force them to a lower version.

 
Posted : 10/23/2013 20:44