Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

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

    Synchronising (mobile) devices via Z-Push
    3
    28
    3058
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Former User
      A Former User @Manfred last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • Manfred
        Manfred Kopano last edited by

        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

        A Former User 1 Reply Last reply Reply Quote 0
        • A Former User
          A Former User @Manfred last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • Manfred
            Manfred Kopano last edited by

            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

            A Former User 1 Reply Last reply Reply Quote 0
            • A Former User
              A Former User @Manfred last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • Manfred
                Manfred Kopano last edited by

                Hi ckruijntjens,

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

                Manfred

                A Former User 1 Reply Last reply Reply Quote 0
                • A Former User
                  A Former User @Manfred last edited by

                  @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!

                  1 Reply Last reply Reply Quote 0
                  • Manfred
                    Manfred Kopano last edited by

                    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

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post