KC: EntryID-corruption on server-restart with MAPI error 80040107 (MAPI_E_INVALID_ENTRYID) in new or modified mail-items
-
Good morning,
…and good news: @jengelh 's commit a3030e1dd8e will stop ongoing corruption, as reported above.++umgfoin.
-
Hallo @all
also does not work in version core-8.4.90.1063_0+138-Ubuntu_14.04-amd64 :(
I have moved new mail to deleted objects and back, reboot server, same issue.
How can I delete the annoying mails from the DB? -
@Sinux I just had success locally by repairing one item. It is possible but it is time consuming. How many elements do you think it is for you?
-
thanks @bosim it affects 14 mails so far but the error still exists…
plz, I would like to hear your solution anyway
thanks -
@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
-
-
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
-
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.
-
@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 -
Solution to the problem has been posted here
https://forum.kopano.io/topic/891/