activesync z-push with outlook 2013 and KopanoOLExtension-2.0-294-64bit

This post is deleted!

Manfred

@psimpson do you have any idea?

psimpson

Very odd that there would be an exception in SendReceive.

It’d be worth trying to uninstall KOE (or disabling it in the plugindebugger in %PROGRAMFILES%\Kopano\Kopano OL Extension) and seeing if that fixes it.

However, given that the crash occurs in pstprx32.dll, which implements the .ost files, I’m inclined to think it’s some broken item. @Manfred Is it possible to somehow exclude any calendar items (and meeting requests, etc) from the sync? We’ve heard of crashes likes this before on those items.

@psimpson @Manfred

Without the koe plug-in it also crashes. Same as with the plug-in installed. So that makes No differense.

psimpson

@ckruijntjens Thanks. Then it would seem to be some weird item. That’s more @Manfred 's territory.

@Manfred

What is the best approuch to find and detect the bad item(s)?

I want to Thank you @Manfred and @psimpson for your help with this one!

Manfred

Hi ckruijntjens,

@ckruijntjens said in activesync z-push with outlook 2013 and KopanoOLExtension-2.0-294-64bit:

What is the best approuch to find and detect the bad item(s)?

Add the user with the issue to $specialLogUsers in Z-Push config and provide only that log (it will be something like username-deviceid.log. It should then be one of the items the server sends to Outlook. Unfortunately it’s not possible to disable calendar items or meeting requests to be synced. The only limitation you could do is to set the value of SYNC_MAX_ITEMS in Z-Push config to pretty low one, e.g. 10, so that less items are synced in a request and it’s easier to identify the broken one.

Manfred

This post is deleted!

Manfred

Hi ckruijntjens,

it’s only one item and also only a part of it, so it’s not possible to say if it’s the culprit, but its end date doesn’t look right: 19700101T000001Z. Could you upload the whole WBXML Log somewhere and send me the link?

Did Outlook crash again and this is the end of the log?

Manfred

This post is deleted!

Manfred

Hi ckruijntjens,

there are a couple of items which might cause Outlook to crash.

The most probably in my opinion is this one “FW: FW: FW: Chris Kruijntens / Klak, BNR, 9921836 — 268883 - 421463, Harteveld” as it doesn’t have a start time and its end date is 19700101T000001Z. It was created from a meeting request you received and that data was either missing there or wasn’t parsed properly. If it’s not an important item, you could try deleting it in webapp and syncing Outlook again. Or open it in webapp and set the correct start/end times.

The first for items in the log also have a rather strange POOMCAL:UID. It usually starts with 040000008200E… It shouldn’t be an issue but Outlook is quite picky about the data it receives, so if after solving the above issue it still doesn’t work, you could try removing (or moving to another calendar) those items.

Manfred

This post is deleted!

Manfred

Hi ckruijntjens,

that would be:
Vreten met mark
Gijs jarig
Afspraak Brechtje
riolering wordt onstopt

Manfred

@manfred

hi manfred,

all items deleted however this did not resolve the issue. now i removed all items that are not needed anymore and now it is working. not sure what item was causing the issue. But it was deffinitly an callendar item issue!

thanks for your help!

Manfred

Hi ckruijntjens,

good to hear that it works now. It might very well be that there were multiple broken items, but Outlook would just stop working on the first broken it encounters.

Manfred