Old appointments getting lost and not resyncing

bhuffman

All,

Is there any reason why old (less than a month) calendar entries would be disappearing and not resyncing? For example, I have an all-day event that was scheduled from June 19th, 2017 and goes until June 23rd, 2017 that shows up in my calendar in the webapp, but is not syncing to my phone. This was scheduled by another user than myself, but it still shows up on my webapp calendar.

I’ve tried clearing the cache on my phone, deleting and re-adding the exchange account (removing z-push state info in between) and no luck.

I’m running ZCP 7.2.4 and z-push 2.3.7

Please help.

Thanks!
Brian

Manfred

Hi Brian,

what is the calendar sync period on the mobile in the account’s settings? For some devices it’s 2 weeks per default, that would explain why it’s not on the phone.

Manfred

bhuffman

My device (Nexus 5x) doesn’t seem to have a specific “calendar sync period.” So, on the phone I set the “Sync emails from” to “all” and then set the SYNC_FILTERTIME_MAX to SYNC_FILTERTYPE_3MONTHS in the z-push.conf.

I still don’t see the calendar entry on my phone that I accepted in May for June 19th, 2017 - June 23rd, 2017.

How does z-push get those calendar entries? Does it require the initial invite email? I checked my “Deleted Items” and the invite seems to have been purged. I still have the “accept” email in my Sent Items.

Regards,
Brian

Manfred

Hi Brian,

that’s weird. The setting might be a bit hidden in the account’s settings. On my android device it’s under account’s settings, then more settings and then under Exchange ActiveSync settings.

Once the meeting is in the calendar, z-push will synchronise it if the item is in the sync window. The initial invite email is not required.

Manfred

Sebastian

Please also check with z-push-admin if this entry can perhaps not be synchronized.

bhuffman

@Manfred - I can not find this setting anywhere on my device. I believe that Google made their own exchange services when Android 6 was released. Perhaps there’s no option to change this setting in the new version?

@Sebastian - I checked z-admin and I don’t see any issues syncing these appointments. It’s more than one of them that have gone missing.

Manfred

Hi Brian,

@bhuffman said in Old appointments getting lost and not resyncing:

@Manfred - I can not find this setting anywhere on my device. I believe that Google made their own exchange services when Android 6 was released. Perhaps there’s no option to change this setting in the new version?

as every vendor has its own ActiveSync implementation, that might be very well possible.

Could you try to edit the appointment in webapp (e.g. add a category) and see if it appears on the mobile? It would be great if you’d set the loglevel to WBXML at least for your user while you test this.

Do those missing appointments have anything in common? E.g. all of them are meetings and the organiser is someone else.

Manfred

bhuffman

@Manfred - When I add a category and save from the web interface, I do not see any change on the device.

The z-push logs show:

26/07/2017 15:43:51 [12044] [DEBUG] [bhuffman] ASDevice->GetFolderIdForBackendId(): no valid condition found for determining folderid for backendid '8d8585bc97cd49aca0be8427c9871c3e1200000000000000'. Returning as is!
26/07/2017 15:43:51 [12044] [DEBUG] [bhuffman] DeviceManager->GetBackendIdForFolderId(): no backend-folderid available for '8d8585bc97cd49aca0be8427c9871c3e1200000000000000', returning as is.
26/07/2017 15:43:51 [12044] [DEBUG] [bhuffman] KopanoChangesWrapper::GetWrapper(): Found existing notification check exporter. Reinitializing.
26/07/2017 15:43:51 [ 1526] [DEBUG] [bhuffman] DeviceManager->GetBackendIdForFolderId(): folderid U57956 => 8d8585bc97cd49aca0be8427c9871c3e1200000000000000
26/07/2017 15:43:51 [ 1526] [DEBUG] [bhuffman] KopanoChangesWrapper::GetWrapper(): Found existing notification check exporter. Reinitializing.
26/07/2017 15:43:51 [12044] [DEBUG] [bhuffman] ASDevice->GetFolderIdForBackendId(): no valid condition found for determining folderid for backendid '8d8585bc97cd49aca0be8427c9871c3e1200000000000000'. Returning as is!
26/07/2017 15:43:51 [12044] [DEBUG] [bhuffman] SyncCollections->CheckForChanges(): Notification received on folder '8d8585bc97cd49aca0be8427c9871c3e1200000000000000', but it is not relevant
26/07/2017 15:43:52 [ 1526] [DEBUG] [bhuffman] SyncCollections->CheckForChanges(): Notification received on folder 'U57956', but it is not relevant

Thanks,
Brian

Manfred

Hi Bob,

could you post the output of

z-push-admin -a list -u bhuffman -d {deviceid}

It looks like the short folder ids and Kopano folder ids are mixed up.

Maybe you could also try to remove the account from the mobile, remove the device with z-push-admin (z-push-admin -a remove -u bhuffman -d {deviceid}), add account on the device again?

Manfred

bhuffman

@Manfred Here’s the output of the z-push-admin:
[root@mail1 bhuffman]# z-push-admin -a list -u bhuffman -d androidc1197698490

Synchronized by user: bhuffman

DeviceId: androidc1197698490
Device type: Android
UserAgent: Android-Mail/7.7.2.162644686.release
Device Model: Nexus 5X
Device friendly name: Nexus 5X
Device OS: Android 7.1.2
ActiveSync version: 14.0
First sync: 2017-07-07 16:41
Last sync: 2017-07-28 15:34
Total folders: 33
Short folder Ids: Yes
Synchronized folders: 8
Synchronized data: Emails(5) Contacts Calendars Tasks
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