No sync with EAS14 after upgrade to 1.8.11
Results 1 to 9 of 9

Thread: No sync with EAS14 after upgrade to 1.8.11

  1. #1
    Senior Member
    Join Date
    Oct 2013
    Posts
    70

    No sync with EAS14 after upgrade to 1.8.11

    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-Se...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-Se...AMSUNGGTI9195] 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.

  2. #2
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello stsimb,
    welcome to the forums!

    Unfortunately due to protocol limitations it's not possible to change the protocol version used by a device after the device itself registers to the server... I edited the changelog to make it more clear.

    Thank you for the heads-up,
    Cine
    the ZeXtras Team

  3. #3
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    Further to this, we have now set ZxMobile_EAS140 and ZxMobile_EAS141 to true in all our backends.
    But we want to disable this in the default COS, and only give this option to specific clients.
    Nevertheless, there is no such setting in the COS, and when we create a new account EAS beta is enabled by default.
    I manually edit the account, uncheck the EAS beta flag and save, but it just turns the checkbox back on.
    Is this a bug somewhere or am I missing something?

  4. #4
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello stsimb!

    The protocol version used for the synchronization is decided by each device according to a list of available protocols made available by the server.
    Setting the "ZxMobile_EAS140" and "ZxMobile_EAS141" properties to "true" will make those protocols available for all devices, while the "Use EAS14 beta" checkbox in a user's settings only provides an override of the server's configuration for that particular user. The behaviour of this checkbox is still provisional, and right now it only allows to override the server config by enabling additional protocols and not the other way around.

    The final behaviour will be decided upon the release of this feature as Stable, and the appropriate documentation will be published on the ZeXtras Wiki...

    Have a nice day,
    Cine
    the ZeXtras Team

  5. #5
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    Thanks for clarifying this behaviour.

    But I have now run setProperty ZxMobile_EAS141 false, and checked the Use EAS14 beta for some specific users, and I still get errors in log/sync.log (this is one of the users with Use EAS14 beta enabled in the checkbox)..

    2013-10-30 13:41:14,770 INFO [qtp563301789-82635:https://10.24.31.34:443/Microsoft-Se...hone&Cmd=Ping] [tid=82635;] sync - ZxMobile Handler: EAS Version '14.1' not available or disabled.
    Last edited by stsimb; 10-30-2013 at 12:29 PM.

  6. #6
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello stsimb!

    That's strange... Did you check the "Use EAS14 beta" checkbox after changing the "ZxMobile_EAS141" property?

    Also, do you have ZeXtras Backup running on your server? It would be useful to verify the changes in the account, so in case you do please run a SmartScan and let me know the output of the following command (run as the zimbra user)?
    Code:
    zxsuite backup getAccountInfo username@domain.com | grep -i eas14enabled

  7. #7
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    Here is the output..
    Code:
    [zimbra@zm-mbox-04 ~]$ zxsuite mobile setProperty ZxMobile_EAS141 false
    
    
    
                    Property ZxMobile_EAS141 set to false
    
    [zimbra@zm-mbox-04 ~]$ zxsuite mobile setProperty ZxMobile_EAS140 false
    
    
    
                    Property ZxMobile_EAS140 set to false
    
    
    [zimbra@zm-mbox-04 ~]$ zxsuite backup getAccountInfo dtsi | grep -i eas14enabled
                    eas14Enabled                                                true
    
    [zimbra@zm-mbox-04 ~]$ tail -f log/sync.log | grep dtsi
    2013-10-30 16:45:20,716 INFO  [qtp563301789-84066:https://10.24.31.34:443/Microsoft-Se...hone&Cmd=Ping] [tid=84066;] sync - ZxMobile Handler: EAS Version '14.1' not available or disabled.
    Last edited by d0s0n; 10-30-2013 at 03:22 PM. Reason: code tag

  8. #8
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello stsimb!

    The Dev Team found and fixed a bug causing this issue.
    You can download the new ZeXtras Suite 1.8.11 package (released as ZeXtras Suite 1.8.11 Hotfix1) from http://www.zextras.com/download/zext....11-HotFix.tgz

    Because of this issue, some mobile devices registered for the firts time on the affected ZeXtras Suite version might be using EAS2.5 instead of EAS14/EAS14.1, so please check your "Registered Devices" list. Should you find any device using EAS2.5 to synchronize an account supposed to be using EAS14, deleting and creating again the account on the mobile should solve the issue.

    Have a nice day,
    Cine
    the ZeXtras Team

  9. #9
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    I installed the HotFix version and I it looks like that the issue is now gone.
    I will continue to monitor logs for the next 24 hrs, but I feel lucky :-)
    Thanks for your quick reaction to fix this!

LinkBacks (?)

  1. 10-30-2013, 09:06 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •