MAPI migration issues via kopano-backup -s command
Atomius last edited by Atomius
during running the kopano-backup command with -s Parameter on a existing Zarafa Installation I received the following errors frequently:
2017-03-02 10:26:03,230 - backup0 - ERROR - could not process change for entryidxd41\x90\xed\x04\x00\x00\x00'), SPropValue(0x30080040, 2016/05/17 08:41:55 GMT),x00\x00'), SPropValue(0x65E30102, '\x14\xeb*!\x8d\x9d>E\xc4\xadv%)v\x10\xd41\x883wM\xaa\xce\x00\x00\x00\x00'), SPropValue(0x67AA000B, False), SPropValue(0x0E070 2017-03-02 10:26:03,241 - backup0 - ERROR - Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 3956, in Impo item.store = Store(mapiobj=mapistore, server=self.server) File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 1457, in __in self._root = self.mapiobj.OpenEntry(None, None, 0) File "/usr/lib/python2.7/dist-packages/MAPICore.py", line 445, in OpenEntry def OpenEntry(self, *args): return _MAPICore.IMsgStore_OpenEntry(self, *args MAPIErrorNetworkError: MAPI error 80040115
Unfortunately I cannot find out which folders or mails are triggering those errors. It happens during the backup of a Mail folder with many mails. Please let me know if you also need additional logs from the source Zarafa installation. The source Zarafa Installation is running on a Synology Disk Station and is Version:
Product version: 7,1,2,39121
File version: 39121
If I try to restore the backups I got similar Errors during restoring the “Journal” unless this folder isn’t used ever.
Thanks a lot
I have a feeling that there is a bug in python-kopano, when used against “old” versions of ZCP, which we could probably solve by logging in remotely. would that perhaps be an option…?