z-push 2.3.3 (ZCP 7.2.3) / Problem with z-pushh and moving outlook folders

[zarafatk]

Well... it's my third full resync after seeing inconsistencies (initially with single items in my Inbox only). But I haven't seen this specific effect so far again. But before this happend I increased memory and # of cores (now 2) as I have seen this effect when I moved several mails very fast after the other. Perhaps both issues are related.

Let's see, when the issue with the folders occurs again.

[fbartels]

Sorry, I should have written "did you create a new profile after upgrade?".

[zarafatk]

yes, I did - I just checked it as I give my profiles indicative names. And the current profile name is specific to 2.3

[zarafatk]

OK. I checked several folders. They worked (move without isses). But than I found a folder which fails all the time. I did a copy before with webapp. Than I moved it. I moved with outlook but not in the

I have the DEBUG data. What I don't understand is, that I don't find a "moved" message!!! (which I normally find with other folders I moved).

I have done a new clean resync before...

I have got the whole xml file (I removed all data before and after that move-event).

When I move other folders afterwards - they work without issue. I guess it has something to do with the folders or its content...? (wrong characters in one of emails or so?)

[fbartels]

Can you upload the wbxml and sent the link to it? We would need the whole file to reach a conclusion here

[zarafatk]

Have you seen anything helpful in this file? The problem still occurs - even with the latest z-push.
Thanks
zarafatk

[Sebastian]

Hi,

I am not aware that I saw this log.

I've just merged a bunch of tickets into the pre-final repository, one that could be related to your issue:
Did you create the folder in Outlook? Do you see that folder in Webapp?

Could you retest with the latest version from the pre-final repository (currently at version 2.3.6beta0+42) making sure to use folders that are known in Outlook and WebApp for your test?
Ideally, resync the Outlook profile before testing (after update).

Cheers,
Sebastian