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

    [Fixed] Error Could not resolve user.

    Kopano WebApp
    7
    14
    3330
    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.
    • Galen
      Galen @byteschubser last edited by

      @byteschubser

      Glad you found a workaround :)

      I’d like to find a fix for the problem in situ. Dumping and importing a large database would take too long as would reindexing :(

      Your workaround does make me think that the database or its schema is the problem.

      G

      umgfoin fbartels 2 Replies Last reply Reply Quote 0
      • umgfoin
        umgfoin @Galen last edited by

        Problem confirmed with:

        WebApp: 3.4.0.680-476.1
        Kopano Core: 8.4.0-644

        webapp debug.txt:

        [02-Jun-2017 17:58:42] ERROR - array (
          'msg' => 'Undefined offset: 806027522',
          'file' => '/usr/share/kopano-webapp/server/includes/core/class.operations.php:3418',
        )
        [02-Jun-2017 17:58:42]  - '
        @ class.operations.php:3418 - kopano_error_handler(...)
        @ class.operations.php:2810 - Operations->createRecipientList(...)
        @ class.operations.php:1873 - Operations->setRecipients(...)
        @ class.createmailitemmodule.php:211 - Operations->saveMessage(...)
        @ class.itemmodule.php:202 - CreateMailItemModule->save(...)
        @ class.jsonrequest.php:57 - ItemModule->execute()
        @ kopano.php:137 - JSONRequest->execute(...)
        

        core/class.operations.php:3418:

        $recipientItem["search_key"] = $user[0][PR_SEARCH_KEY];

        ++umgfoin

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

          @Galen said in Error Could not resolve user.:

          Your workaround does make me think that the database or its schema is the problem.

          I must say I doubt that, especially since he also installed on older Kopano version.

          I started collection similar reports in https://jira.kopano.io/browse/KC-709 and this suggests that 8.4.0~667 should actually be the newest unaffected version, but it still shows up as broken here.

          EDIT: core-8.4.0~644_137 actually seems to be the highest not affected version.

          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/

          Galen 1 Reply Last reply Reply Quote 0
          • umgfoin
            umgfoin last edited by

            Hello Felix,
            maybe this problem is related, too.
            Although (but I can’t state with certainity) my impression is, these adressbook-related issues do exist already for a longer time.

            ++umgfoin.

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

              @umgfoin hm… that should not really touch the same corners of the code. I will add it as a comment though and try to have someone from the webapp team take a look at it.

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

                @fbartels said in Error Could not resolve user.:

                @Galen said in Error Could not resolve user.:

                Your workaround does make me think that the database or its schema is the problem.

                I must say I doubt that, especially since he also installed on older Kopano version.

                Had i noticed that a different version was installed i wouldn’t have thought as i did. :face_palm_tone3:
                I had in my head that data out -> fresh install -> data in was pointing to the database.

                G

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

                  Hello

                  where can I get an older version?

                  umgfoin 1 Reply Last reply Reply Quote 0
                  • umgfoin
                    umgfoin @majoess last edited by

                    @majoess
                    You can’t - especially, if you won’t be more specific.

                    Community downloads are nightly builds.
                    Stable packages are available for Kopano-customers.

                    Alternatively you might checkout the stable branch from the git-repo and build a working installation on your specific platform.

                    ++umgfoin.

                    1 Reply Last reply Reply Quote 0
                    • JeskoMägle
                      JeskoMägle last edited by

                      Seems to be fixed in the latest version ( core-8.4.0~813_153.1 )

                      Thanks :)

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

                        I’ve just tested again with core-8.4.0~825_158.1 and webapp-3.4.0.704_489-Debian_8.0 and the error no longer appears.

                        G

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