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

    Error messages when creating calendar entries in Outlook 2016

    Z-Push when using Kopano
    5
    14
    4038
    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.
    • gladston3
      gladston3 last edited by gladston3

      Hi Sebastian,

      thanks alot for your investigations and your time you put into this.

      I did not do anything in the webapp though besides checking if the entry was successfully synced. I think the best way to get an idea of my error is to see it with your own eyes. So I made a short screen capture video. It’s just a little bit over 2 minutes long so it shouldn’t be too time consuming.

      The time between the creation of an element and the “drag changing” doesn’t seem to matter at all. Also outlook should be fully synced.
      The only thing which seems to always get rid of the error is the reopening and resaving of the element a second time.

      But I showed all that in the video:

      https://cloud.ristl.it/index.php/s/psUyuZS3sqOUjla

      If you need any more information or a second video (:wink:) just let me know. I am happy to provide any additional information.

      cheers
      -gladston3

      1 Reply Last reply Reply Quote 0
      • gladston3
        gladston3 last edited by gladston3

        Ok, I investigated this further myself and it seems to be a local outlook problem. I tried two other PCs real quick and there it worked. What I did not try is to install the Kopano OL plugin since those PCs were production ones.
        What is strange is that the same error occurs now with a native exchange connection too. And that was definately not happening before. So I will try to find out the cause and let you know if I can find something and if it is related to kopano or its outlook plugin.

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

          Hum, indeed what I see in your video is only partly explained by what I tested.
          The way via the webapp is just to confirm the theory, it’s not required.

          I also learned from the video that you don’t move the appointment to a new time/data, but just change the duration (which is a different test case).

          Your hint about KOE got me thinking. I could reproduce the issue by changing the duration and the error vanished after I disabled KOE. This might explain why this also happened with Exchange for you afterwards.

          I created a ticket for the KOE to investigate this: https://jira.kopano.io/browse/KOE-92

          Cheers,
          Sebastian

          1 Reply Last reply Reply Quote 0
          • gladston3
            gladston3 last edited by gladston3

            Hey @Sebastian ,

            I played around some more today. I completely removed the Kopano Outlook Plugin and now the " element cannot be changed because it was used/changed by another or opened in another window" error is gone.
            What stayed though, is the second “reminder” error. It still can be fixed with the reopening and resaving procedure.
            I already did a complete repair of my office suite but that did not bring any improvements. If I find some time I am going to set up a VM with Office and see if I can reproduce the error or if it’s just random local thing.
            I will keep you updated of course. If you have any hints or tips, just let me now (:

            cheers
            -gladston3

            fbartels 1 Reply Last reply Reply Quote 0
            • fbartels
              fbartels Kopano @gladston3 last edited by

              H @gladston3 ,

              we now have a build in QA that should fix this error. Do you want to give it a try as well?

              This change though comes with the risk of reintroducing crashes in low memory system (the pre 1.2.127 behaviour), therefore we decided to make it configurable for now.

              Regards Felix

              Resources:
              https://kopano.com/blog/how-to-get-kopano/
              https://documentation.kopano.io/
              https://kb.kopano.io/

              Support overview:
              https://kopano.com/support/

              1 Reply Last reply Reply Quote 0
              • gladston3
                gladston3 last edited by gladston3

                Hey @fbartels,

                I am for sure interested in trying this out. What do I have to do? Update KOE or Z-push or both to the latest version? And where do I find the configuration switch?

                Thanks in advance
                cheers
                -gladston3

                fbartels 1 Reply Last reply Reply Quote 0
                • fbartels
                  fbartels Kopano @gladston3 last edited by fbartels

                  @gladston3 I’ve just uploaded the new build to https://download.kopano.io/supported/olextension:/pre-final/

                  EDIT: there is a new option in the global section of the PluginDebugger.exe called “ReleaseItemEventWrappers”, that controls this behavior. It defaults to true, if it causes problems it could be switched to false to have the old behavior back.

                  Regards Felix

                  Resources:
                  https://kopano.com/blog/how-to-get-kopano/
                  https://documentation.kopano.io/
                  https://kb.kopano.io/

                  Support overview:
                  https://kopano.com/support/

                  1 Reply Last reply Reply Quote 0
                  • Gerald
                    Gerald last edited by

                    Funny. I have the exact same problem without ever using the KOE plugin, just pure Activesync on Outlook 2016! It drove me crazy - then when I investigated it I found that it only happens when the “Teamviewer Meeting Add-In” was enabled in Outlook 2016. This gets installed by Teamviewer automatically (even though I’ve never used the Teamviewer Meeting functionality).

                    Since I’ve disabled the Teamviewer Meeting Add-In this weird error message is gone!

                    externa1 1 Reply Last reply Reply Quote 0
                    • externa1
                      externa1 @Gerald last edited by

                      @Gerald

                      Interesting - I’ve also this messages and teamviewer installed too - so i deactivated teamviewer plugin as I never used it too
                      Will see if this is now gone - will give feedback here in the next days

                      rg

                      Christian

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

                        I had this issue also without the Teamviewer extension (just checked, it’s installed but deactivated).
                        Latest KOE 1.3 has fixes for this behaviour and the calendaring is working fine now.

                        There is still a similar issue that happens when flagging emails after moving them.
                        https://jira.kopano.io/browse/KOE-103
                        We haven’t found a solution for this yet.

                        Cheers,
                        Sebastian

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