Upgraded to 2.3.1, but all clients still using old ids

Clarify issues about the installation

Upgraded to 2.3.1, but all clients still using old ids

Postby maxxer » Wed Oct 05, 2016 9:33 am

Hi.
I upgraded from 2.2.x to 2.3.1 (with zimbra backend), after upgrade I ran the fixstates command and apaprently all went on normally.

Now I started upgrading clients, for androids by issuing resync and for outlook by deleting account and data... But even after all the commands the lastsync is always reporting clients NOT using short ids.

The only errors I found in z-push-error.log are:
Code: Select all
05/10/2016 10:28:53 [ 2623] [ERROR] [info] Zimbra->SoapRequest(): SOAP FAULT: Error Code Returned [mail.NO_SUCH_WAITSET]
05/10/2016 10:28:53 [ 2623] [ERROR] [info] Zimbra->SoapRequest(): SOAP FAULT: Error Code Returned [mail.NO_SUCH_WAITSET]


Apache's error log doesn't show any issue.

What can I check to see what's going wrong?
thanks
maxxer
 
Posts: 27
Joined: Sun May 16, 2010 6:14 pm

Re: Upgraded to 2.3.1, but all clients still using old ids

Postby liverpoolfcfan » Mon Oct 10, 2016 10:56 pm

I replied on the other (zarafa) forum. This one is not used any more.
liverpoolfcfan
 
Posts: 395
Joined: Mon Feb 22, 2010 2:47 pm


Return to Installation

Who is online

Users browsing this forum: No registered users and 1 guest

cron