IOS Devices dont getting synced anymore since z-push/kopano Update

Manfred

Hi Stefan,

What were the 2 updates? Z-Push and Kopano? From which versions have you updated?

For the Z-Push update - how have you updated? Did you do anything with the state folder (deleting or moving it manually or manipulating something with z-push-admin)? Did you also update the firmware of the device? Have you created a new profile on the device?

Is the device really stuck synchronising or is it still synchronising? How many devices are affected?

Are there other devices than iphones connected? Do they have similar issues?

Manfred

vm_machina

Hi Manfred

i upgraded kopano and z-push via the Ubuntu 16.04 Repositorys.
The Problem starting with z-push Version 2.3.8. On Kopano Side i cannot remember the Version but it was working with Kopano 5.4.0

I tried different Things:
I upgraded without touching state Folder or anything else on z-push Side.
The Ios Devices are on 11.2.6.
For Troubleshoting i tried everything include wipeing the Device I also recreated couple of Times the Profils on the Phones without Success.
On z-push Side i tried :
z-push-admin -a remove -u usera
and
z-push-admin with clearloop and fixstates.

When i clear the Systemwideloop the folowing is shown inside the z-push error log:

21/03/2018 09:02:21 [21147] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:22 [22016] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:23 [22952] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:26 [22068] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:27 [22958] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:28 [22016] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:29 [22952] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:31 [22471] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:33 [21531] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:35 [22958] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:37 [22016] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:38 [22952] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:40 [22471] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:41 [21531] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:43 [22958] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:45 [20468] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:47 [20510] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:49 [21147] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:50 [22068] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:52 [22958] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:54 [20468] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:55 [20510] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:57 [21147] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:02:59 [22068] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:03:00 [22958] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:03:02 [20468] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:03:03 [20510] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:03:05 [21147] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:03:06 [22068] [WARN] [usera] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
21/03/2018 09:14:21 [23903] [FATAL] [usera] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
21/03/2018 09:14:21 [23892] [FATAL] [usera] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
21/03/2018 09:14:21 [22016] [FATAL] [usera] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
21/03/2018 09:14:22 [24030] [FATAL] [usera] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
21/03/2018 09:14:22 [24030] [WARN] [usera] The store is not available. It is not possible to remove search folder with pid 23903
21/03/2018 09:14:22 [22016] [FATAL] [usera] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command_(ProvisioningRequiredException) - Retry after sending a PROVISION command
21/03/2018 09:14:22 [22016] [WARN] [usera] The store is not available. It is not possible to remove search folder with pid 23892
21/03/2018 09:14:22 [24030] [FATAL] [usera] Excepti
21/03/2018 09:14:22 [24030] [WARN] [usera] The store is not available. It is not possible to remove search folder with pid 22016
21/03/2018 11:14:01 [22471] [WARN] [usera] StatusException: ExportChangesICS->InitializeExporter(): Error, mapi_exportchanges_config() failed: 0xFFFFFFFF80040116 - code: 12 - file: /usr/share/z-push/backend/kopano/exporter.php:230

Manfred

Hi Stefan,

are all the iOS devices affected by this? Are there other devices connected (Androids, Windows Phones, Outlook via ActiveSync)?

Have you restarted apache after Kopano update? Are you able to open the emails in the webapp for this user?

Manfred

vm_machina

Hi Manfred,

yes all ios devices. I cross checked with Microsoft Outlook via ActiveSync. Same Problem !
Via Kopano Webmail it is working great.
Yes i restarted all relevant Services and the Server self multiple Times.

BR Stefan

Manfred

Hi Stefan,

can you post the full WBXML log since the initial FolderSync for one of the devices?

Manfred

vm_machina

you can download the logfile here:
https://brockz.dyndns.tv/index.php/s/5LHTrrDlVibsoTG

Manfred

Hi Stefan,

Were you switching between sql states and file states?

The Kopano version in the z-push.log is different from what you posted here. Are you using KC nightly builds?
Are there any errors in server.log of kopano?

As first action I suggest to start with a clean Z-Push installation and configuration, remove all the states, execute clearloops with z-push-admin, remove profile from the device and create a profile again.

If the above doesn’t help, try downgrading KC to 8.5.5.0.

Manfred

vm_machina

Hello Manfred

for testing purpose i switched to sql states one time. Without Success. Problem still exists.
I reinstalled z-pusg acouple of Times new wihtout Success.
I try it again to reinstall it and coming back here with my findings.

Vogi

Hello!

I run into same problem after updating kopanocore to latest master from repository and z-push from 2.3.9 to 2.4.0.
I am running a gentoo server and I’m compiling from source.

First I tried downgrading z-push to 2.3.9 first but that didn’t help.
After switiching kopanocore from master to 8.6.x branch it was working again.
I switched to z-push 2.4.0 again afterwards - also without any issues.

I haven’t checked which commit caused that problem, because I hadn’t time anymore…

vm_machina

How can i downgrade ?
Where can i find the 8.6.x Branch ?
I am on Kopano 8.6.80.3 an having the Problem

Manfred

Hi Stefan,

for the best practice for the downgrade you should ask Kopano Support. If you don’t have a Kopano subscription, try asking in the core subforum. There’s also a thread regarding Kopano rollback: https://forum.kopano.io/topic/327/kopano-core-rollback

Manfred

vm_machina

Cannot download kopano core-8.4.90 for ubuntu 16.04 x64 anymore. This was my last Working Version. :(

onex.de

It seems, I have the same problem on my Google Pixel 2 on latest Kopano for UCS (Univention)
WebApp: 3.4.9.1330+53.1
Kopano Core: 8.5.5
Z-Push: 2.4.0+0-0

I deleted the account on my mobil and deleted all related account data with z-push-admin, then I recreated the account on my mobile, it begun syncing and after several /usr/share/z-push/backend/kopano/mapiprovider.php:997 Undefined offset errors and some loop messages, z-push reportet the sync to be finished and my mobile still tries to sync all unsynced data without any new connection to the server.

Addendum: I did my fifth account recreation on my mobile and this time I didn’t activate downloading attachments via WLAN (wifi) and now it seemed to finally sync, but with a lot of the errors and warnings, mentioned above.

vm_machina

Hello

I Reinstalled z-Push 2.4 from The Repo (no tarball) fresh without success. Also the downgrade to kopano 8.5.5 didnt resvolve the issue.

Br Stefan

Manfred

Hi Stefan,

is it still the same problem that the sync won’t complete? Can you post z-push-admin output for that device and user?

Manfred

vm_machina

Hello Manfred

here we go:

Synchronized devices of user: usera
-----------------------------------------------------
DeviceId:               xxxx
Device type:            iPhone
UserAgent:              Apple-iPhone9C4/1504.100
Device Model:           iPhone9C4
Device friendly name:   iPhone 7 Plus
Device OS:              iOS 11.2.6 15D100
Device OS Language:     de-DE
ActiveSync version:     14.1
First sync:             2018-03-23 07:21
Last sync:              2018-03-23 15:38
Sync Period:            unlimited (0)
Total folders:          26
Short folder Ids:       Yes
Synchronized folders:   6 (2 in progress)
Synchronized data:      Emails(2) Contacts Calendars Notes Tasks
Synchronization progress:
        Folder: Inbox                Sync: Synchronizing Status:  1% (559/40955)
        Folder: Sent Items           Sync: Synchronizing Status:  3% (59/2068)
Additional Folders:     none
Status:                 OK
WipeRequest on:         not set
WipeRequest by:         not set
Wiped on:               not set
Policy name:            default
Attention needed:       No errors known

No Success. Stucks since Hours… (Status)

Manfred

Hi Stefan,

there are 40k emails in your inbox. Have you tried synchronising a shorter period of time? Are there any errors in z-push.log or server.log of kopano? Do you have another device to try to sync?

Manfred

ablanco

Hi!

I have the same problem with upgrade 8.6, I deleted all devices and sync again, the result:

z-push-error.log:

29/04/2018 12:12:02 [12054] [FATAL] [ablanco] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
29/04/2018 12:13:07 [21942] [FATAL] [ablanco] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command

z-push-admin:

Synchronized devices of user: USER
---------------------------------------------------
DeviceId:               XXXXX
Device type:            iPad
UserAgent:              Apple-iPad4C2/1505.302
Device Model:           iPad4C2
Device friendly name:   iPad Air
Device OS:              iOS 11.3.1 15E302
Device OS Language:     es
ActiveSync version:     14.1
First sync:             2018-04-29 12:12
Last sync:              2018-04-29 12:12
Sync Period:            unlimited (0)
Total folders:          0
Short folder Ids:       No
Synchronized folders:   0
Synchronized data:      None available
Additional Folders:     none
Status:                 OK
WipeRequest on:         not set
WipeRequest by:         not set
Wiped on:               not set
Policy name:            default
Attention needed:       No errors known
-----------------------------------------------------
DeviceId:               XXXXXX
Device type:            iPhone
UserAgent:              Apple-iPhone9C3/1505.302
Device Model:           iPhone9C3
Device friendly name:   Negro iPhone 7
Device OS:              iOS 11.3.1 15E302
Device OS Language:     es-ES
ActiveSync version:     14.1
First sync:             2018-04-29 12:13
Last sync:              2018-04-29 12:13
Sync Period:            unlimited (0)
Total folders:          0
Short folder Ids:       No
Synchronized folders:   0
Synchronized data:      None available
Additional Folders:     none
Status:                 OK
WipeRequest on:         not set
WipeRequest by:         not set
Wiped on:               not set
Policy name:            default
Attention needed:       No errors known

Thanks! :)

Manfred

Hi ablanco,

how do you deleted all devices? With z-push-admin?

Please also post z-push.log at least at DEBUG level.

Have you tried removing the account on the device and adding it again?

Manfred

ablanco

This post is deleted!