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

    KC: EntryID-corruption on server-restart with MAPI error 80040107 (MAPI_E_INVALID_ENTRYID) in new or modified mail-items

    Kopano Groupware Core
    6
    27
    4798
    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.
    • Sinux
      Sinux @bosim last edited by Sinux

      thanks @bosim it affects 14 mails so far but the error still exists…
      plz, I would like to hear your solution anyway
      thanks

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

        @sinux
        as JIRA ticket KC-909 status shows, all this is currently under review.

        … and I tend to believe, patience is good advice, here.

        Jan’s commit a3030e1dd8e hasn’t been pushed to the master-branch, yet - thus it hardly can be contained in any community-build, either.

        Concerning deletion of sgl. mailitems, the following approach should work:

        • take down kopano-server or atleast prevent multi-user access.
        • start a mysql-cmd-client mysql -hlocalhost -udb_user db_name
        • identify hierarchyids of (broken) items by a query in the properties-table: e.g.
          SELECT hierarchyid FROM properties WHERE val_string LIKE "Subject_of_broken_mail%" AND hierarchyid IN (SELECT id FROM hierarchy WHERE type=5);
        • delete related properties, tproperties and hierarchyentries:
          DELETE from hierarchy WHERE id=<result from above>;
          DELETE from tproperties WHERE hierarchyid=<result from above;>
          DELETE from indexedproperties WHERE hierarchyid=<result from above;>

        But:

        • reliably backup your db prior any modifications
        • Be careful with the first query - your search criteria need to be unambiguously
        • eventually use START TRANSACTION/ ROLLBACK/ COMMIT to recover from typos or mistakes

        ++umgfoin

        Sinux 1 Reply Last reply Reply Quote 1
        • Sinux
          Sinux @umgfoin last edited by Sinux

          @umgfoin thanks, I’ll try it
          update
          thanks it works but I would still like to try his suggestion @bosim

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

            Hi,

            with this version core-8.4.90.1064_0+139-Ubuntu_14.04-amd64 it seems to work again.
            Now I hope on bosim data recovery.

            thanks

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

              It appears that a MAPI_MESSAGE’s entryid is only ever referenced from another message’s 0x80FD, 0x80FE and 0x825D properties. As these seem to be some obscure properties, regenerating entryids of messages (not so with folders/stores) at will should generally work.

              jackson5 1 Reply Last reply Reply Quote 0
              • jackson5
                jackson5 @Guest last edited by

                @jengelh said in KC: EntryID-corruption on server-restart with MAPI error 80040107 (MAPI_E_INVALID_ENTRYID) in new or modified mail-items:

                It appears that a MAPI_MESSAGE’s entryid is only ever referenced from another message’s 0x80FD, 0x80FE and 0x825D properties. As these seem to be some obscure properties, regenerating entryids of messages (not so with folders/stores) at will should generally work.

                So how to trigger that?

                Thx,
                jacks

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

                  Solution to the problem has been posted here
                  https://forum.kopano.io/topic/891/

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