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 Message after Login

    Kopano WebApp
    2
    10
    2270
    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.
    • Vogi
      Vogi last edited by Vogi

      Hello!

      I am using the latest Webapp versions taken from the repository and compiling it myself on a Gentoo system.
      Until now I never had bigger problems that weren’t fixed very soon.

      But for some weeks I have a annoying message coming up after every login:
      “Fehler - Konnte den Inhalt diesen Ordners nicht laden” which means “Error - Unable to load the folder content”
      After that everything works as always.

      I also see this errors in the log files:

      Aug  6 21:44:48 server01 php-mapi[31057]: MAPI error: not found (8004010f) (method: zif_mapi_msgstore_openentry, line: 1933)
      Aug  6 21:44:48 server01 php-mapi[31057]: MAPI error: call failed (80004005) (method: zif_mapi_setprops, line: 3377)
      Aug  6 21:52:15 server01 php-mapi[30914]: MAPI error: action not supported by server (80040102) (method: zif_mapi_msgstore_getreceivefolder, line: 2580)
      
      

      I haven’t found any similar problem so it might be some problem of my system.
      Any help would be appreciated

      Thank you
      Vogi

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

        Hi @Vogi ,

        are you only running the latest WebApp or also running the latest Core? php-mapi is part of Core, thats why I ask.

        Against which commit have you build you packages? Since you are already self compiling it would help in bisecting this if you’d be able to narrow down the window in which the supposed breaking change was introduced.

        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
        • Vogi
          Vogi last edited by

          Hello fbartels,

          I am not at home right now… but I rember that It was around the change to versioning 8.4.90.
          I had some problem with changes in the makefile (paralle make for python 2 /3) and went back some versions. And I had to upgrade gsoap to 2.8.49…

          At the same time I upgraded the Webapp…

          I was happy, that it worked again without any twaeks after some commits for the python build… but the error message didn’t disappear.

          I coudl try to revert to version that hadn’t a problem before…

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

            Ok… some update:

            Problem is independent from used Webapp version.

            I rolled back to to 8.3.3 - error message is gone.
            Instead of that the “calendar remember dialog” comes up again - this wasn’t working before
            In the log file I still see one error message whn logging in:

            Aug  8 20:32:35 server01 php-mapi[9124]: MAPI error: action not supported by server (80040102) (method: zif_mapi_msgstore_getreceivefolder, line: 2568)
            

            But this one doesn’t seem to brake anything.
            I will try to find the version which starts showing the error.

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

              Thanks. Looking forward to your findings.

              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
              • Vogi
                Vogi last edited by Vogi

                Hi again,

                I went through all commits and even double checked the following result:

                Up to commit “2460c47e2c5daf7d3bc5359b8afc8d8b5a907e46” I have no error on login.
                The reminders window occours as it should.
                Only this already mentioned log entry occours on log in via Webapp (looks for every user equal):

                Aug  9 19:30:05 server01 php-mapi[4881]: MAPI error: action not supported by server (80040102) (method: zif_mapi_msgstore_getreceivefolder, line: 2585)
                

                With commit “5131ba6cab786ba216022c238ae94aeb0c1c1927” the message "“Fehler - Konnte den Inhalt diesen Ordners nicht laden” shows up for every user shortly after login. The reminders windows doesn’t show up anymore.

                Then the log files shows two additional errors:

                Aug  9 20:03:06 server01 php-mapi[20731]: MAPI error: not found (8004010f) (method: zif_mapi_msgstore_openentry, line: 1938)
                Aug  9 20:03:06 server01 php-mapi[20731]: MAPI error: call failed (80004005) (method: zif_mapi_setprops, line: 3382)
                

                The commit includes some reverts and this comment: “server: disable reminders from shared stores”
                I don’t know if it is relevant, but my database is based on first zarafa 6.4 installation and got updated by the time.
                After switching from LDAP to ActiveDirectory (almost two years ago) I had to “rehook” the stores to the users, as they had new uids…

                Any idea how to fix my problem?
                As noone else has posted such an behaviour, I fear, that it might be a singular problem.

                Thank you
                Vogi

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

                  Hi @Vogi ,

                  thanks for your bisect. you have uncovered something quite interesting. I’ll have a developer look at this. Will keep you updated.

                  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
                  • fbartels
                    fbartels Kopano last edited by

                    Hi @Vogi ,

                    did you by any chance hook the store of this user to anther user in the past? The only way we could reproduce your effect is by hooking stores and this is why this slipped through. we have adjusted the change and will merge it as soon as its reviewed and tested.

                    if you already want to give it a spin you can find the change at https://stash.kopano.io/projects/KC/repos/kopanocore/commits/77513c5eb13209fd3935eca470e1ce068a3b3888

                    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
                    • Vogi
                      Vogi last edited by

                      Hi Felix,

                      with the latest commit the error message is gone - thanks for the fast fix!

                      You are right: As I wrote, I replaced our LDAP directory with ActiveSync. After that, all users had a different uid than before and Kopano created new empty stores - so I hooked the old ones back to the users.

                      Is there a way to completly migrate the old stores to the new users - or is it ok, the way I did it?

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

                        Hi @Vogi ,

                        oh indeed I overread that hooking part.

                        There is http://wiki.zarafa.com/index.php/Zarafa_DB_to_LDAP_user_plugin_conversion to totally switch your user data over to new unique ids, but since the rehooking was already a while back its probably not of much help anymore.

                        Generally speaking you should also be fine in continuing to work as you are doing 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
                        • First post
                          Last post