[Solved]WARNING - Received a MAPI error or timeout, no backup, no search

Hi *!

I have a weird problem here with KC 8.6.4.0. I can’t successfully run kopano-search, and I can’t run kopano-backup. I assume there is an integrety problem with in my database.

First, attachments are stored in the DB. This, because I suspect my problems relate to the attachments.

When I run kopano-backup, after some time I get an error message

root@exchange64:/backup/dont_save# kopano-backup -u pbauer 
2018-08-24 17:12:45,068 - backup - WARNING - no data found for attachment of item with entryid 0000000070BE20DDCD354C668815C070B929434701000000050000007A581852F1C84402859A12B2D249D84C00000000
2018-08-24 17:15:43,673 - backup0 - WARNING - Received a MAPI error or timeout (error=0x80040115, retry=0/5)
2018-08-24 17:15:44,083 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=1/5)
2018-08-24 17:15:44,891 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=2/5)
2018-08-24 17:15:46,500 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=3/5)
2018-08-24 17:15:49,711 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=4/5)
2018-08-24 17:15:56,124 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=5/5)
2018-08-24 17:16:02,531 - backup0 - ERROR - Too many retries, skipping change
2018-08-24 17:16:02,539 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=0/5)
2018-08-24 17:16:08,954 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=1/5)
2018-08-24 17:16:15,369 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=2/5)
2018-08-24 17:16:21,785 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=3/5)

Please note two things

  • The error message regarding the attachment is far sooner than the error messages regarding MAPI errors
  • the first MAPI error has a different error code

At the same time, the server logs the following:

Fri Aug 24 17:12:44 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:12:44 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1353495
Fri Aug 24 17:15:43 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 555407
Fri Aug 24 17:15:44 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:15:44 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 555407
Fri Aug 24 17:15:44 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:15:44 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1353495
Fri Aug 24 17:15:44 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:15:44 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 555407
Fri Aug 24 17:15:46 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:15:46 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 555407
Fri Aug 24 17:15:49 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:15:49 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 555407
Fri Aug 24 17:15:51 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:15:51 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1353495
Fri Aug 24 17:15:56 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:15:56 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 555407
Fri Aug 24 17:15:57 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned

[...]

Again, notify the two different object numbers, 555407 and 1353495.

running kopano-fsck --all --autofix yes --autodel yes -u pbauer gives

Validating of folder "Kontakte" ended
Unknown class, skipping entry "Gesendete Objekte"
Unknown class, skipping entry "Gelöschte Objekte"
Unknown class, skipping entry "Postausgang"
Unknown class, skipping entry "Posteingang"
Unknown class, skipping entry "Shortcut"
Unknown class, skipping entry "FINDER_ROOT"
Unknown class, skipping entry "IPM_VIEWS"
Unknown class, skipping entry "IPM_COMMON_VIEWS"
Unknown class, skipping entry "IPM_SUBTREE"

Statistics:
IPF.Appointment
	Folders:	1
	Entries:	2470
	Problems:	2
	Fixed:		2
	Deleted:	9
IPF.Contact
	Folders:	1
	Entries:	504
	Problems:	0
	Fixed:		0
	Deleted:	5
IPF.Task
	Folders:	1
	Entries:	498
	Problems:	0
	Fixed:		0
	Deleted:	0

but does not fix the problem.

Can somebody please give me an advice what I could do more to identify which database entry/MAPI object is responsible for that issue?

Thank you all!

OK, Update: I have disabled kopano-search, set the log-level for kopano-server to 6 and restarted the server. Then, I tried to run a new backup.

The kopano-backup puts out

root@exchange64:/backup/dont_save# kopano-backup -u pbauer 
2018-08-24 17:44:56,519 - backup - WARNING - no data found for attachment of item with entryid 0000000070BE20DDCD354C668815C070B92943470100000005000000E230AD40B6F443C599BDAA10B23E53FA00000000
2018-08-24 17:47:24,261 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=0/5)
2018-08-24 17:47:24,666 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=1/5)
2018-08-24 17:47:25,471 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=2/5)
2018-08-24 17:47:27,077 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=3/5)
2018-08-24 17:47:30,286 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=4/5)
^C2018-08-24 17:47:36,693 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=5/5)

In the same time, the server log reads

Fri Aug 24 17:44:03 2018: [=======] Starting kopano-server version 8.6.4 (pid 9370)
Fri Aug 24 17:44:03 2018: [warning] Config warning: Option 'server_max_keep_alive_requests' is not used anymore.
Fri Aug 24 17:44:03 2018: [info   ] Using epoll events
Fri Aug 24 17:44:03 2018: [notice ] Listening for TCP connections on port 236
Fri Aug 24 17:44:03 2018: [notice ] Listening for SSL connections on port 237
Fri Aug 24 17:44:03 2018: [error  ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0. See kopano-coredump(5) for details.
Fri Aug 24 17:44:03 2018: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock
Fri Aug 24 17:44:03 2018: [notice ] Listening for pipe connections on /var/run/kopano/server.sock
Fri Aug 24 17:44:03 2018: [notice ] Connection to database 'zarafa' succeeded
Fri Aug 24 17:44:04 2018: [debug  ] PurgeCache took 0 ms
Fri Aug 24 17:44:04 2018: [notice ] Querying database for searchfolders. This may take a while.
Fri Aug 24 17:44:04 2018: [notice ] Loading search folders.
Fri Aug 24 17:44:04 2018: [notice ] Done loading search folders.
Fri Aug 24 17:44:04 2018: [notice ] Startup succeeded on pid 9370
Fri Aug 24 17:44:04 2018: [debug  ] Started priority thread 9378
Fri Aug 24 17:44:04 2018: [debug  ] Started thread 9379
Fri Aug 24 17:44:04 2018: [debug  ] Started thread 9380
Fri Aug 24 17:44:04 2018: [debug  ] Started thread 9382
Fri Aug 24 17:44:04 2018: [debug  ] Started thread 9381
Fri Aug 24 17:44:04 2018: [debug  ] Started thread 9383
Fri Aug 24 17:44:04 2018: [debug  ] Started thread 9384
Fri Aug 24 17:44:04 2018: [debug  ] Started thread 9385
Fri Aug 24 17:44:04 2018: [debug  ] Started thread 9386
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:04 2018: [debug  ] Previous message logged 10 times
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from 192.168.100.1
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:04 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:05 2018: [debug  ] Previous message logged 3 times
Fri Aug 24 17:44:05 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:44:05 2018: [debug  ] Accepted incoming connection from 192.168.100.1
Fri Aug 24 17:44:05 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:05 2018: [debug  ] Previous message logged 2 times
Fri Aug 24 17:44:05 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Fri Aug 24 17:44:05 2018: [error  ] Previous message logged 3 times
Fri Aug 24 17:44:05 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:05 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Fri Aug 24 17:44:05 2018: [error  ] Previous message logged 7 times
Fri Aug 24 17:44:05 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:05 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:06 2018: [debug  ] Previous message logged 3 times
Fri Aug 24 17:44:06 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:44:06 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Fri Aug 24 17:44:06 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:44:06 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Fri Aug 24 17:44:08 2018: [error  ] Previous message logged 3 times
Fri Aug 24 17:44:08 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:12 2018: [debug  ] Previous message logged 2 times
Fri Aug 24 17:44:12 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:44:12 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:21 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:44:35 2018: [debug  ] Previous message logged 2 times
Fri Aug 24 17:44:35 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:44:45 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:44:46 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:45:18 2018: [debug  ] Previous message logged 80 times
Fri Aug 24 17:45:18 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:45:21 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:45:24 2018: [debug  ] Previous message logged 5 times
Fri Aug 24 17:45:24 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:45:24 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 498466
Fri Aug 24 17:45:24 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:45:40 2018: [debug  ] Previous message logged 27 times
Fri Aug 24 17:45:40 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:45:40 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:45:45 2018: [debug  ] Previous message logged 16 times
Fri Aug 24 17:45:45 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:45:49 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:46:28 2018: [debug  ] Previous message logged 38 times
Fri Aug 24 17:46:28 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:46:28 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:46:45 2018: [debug  ] Previous message logged 51 times
Fri Aug 24 17:46:45 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:46:46 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:46:47 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:46:48 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:47:24 2018: [debug  ] Previous message logged 73 times
Fri Aug 24 17:47:24 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:47:24 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1114519
Fri Aug 24 17:47:24 2018: [debug  ] gSOAP error on processing request: SOAP_FATAL_ERROR
Fri Aug 24 17:47:24 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:47:24 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:47:24 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1114519
Fri Aug 24 17:47:24 2018: [debug  ] gSOAP error on processing request: SOAP_FATAL_ERROR
Fri Aug 24 17:47:24 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:47:25 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:47:25 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1114519
Fri Aug 24 17:47:25 2018: [debug  ] gSOAP error on processing request: SOAP_FATAL_ERROR
Fri Aug 24 17:47:25 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:47:27 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:47:27 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1114519
Fri Aug 24 17:47:27 2018: [debug  ] gSOAP error on processing request: SOAP_FATAL_ERROR
Fri Aug 24 17:47:27 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:47:30 2018: [debug  ] Previous message logged 2 times
Fri Aug 24 17:47:30 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:47:30 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1114519
Fri Aug 24 17:47:30 2018: [debug  ] gSOAP error on processing request: SOAP_FATAL_ERROR
Fri Aug 24 17:47:30 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:47:36 2018: [debug  ] Previous message logged 3 times
Fri Aug 24 17:47:36 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:47:36 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1114519
Fri Aug 24 17:47:36 2018: [debug  ] gSOAP error on processing request: SOAP_FATAL_ERROR
Fri Aug 24 17:47:36 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:47:45 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:47:52 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:47:58 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:48:05 2018: [debug  ] Previous message logged 5 times
Fri Aug 24 17:48:05 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Fri Aug 24 17:48:05 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:48:45 2018: [debug  ] Previous message logged 25 times
Fri Aug 24 17:48:45 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:48:47 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:48:58 2018: [debug  ] Previous message logged 8 times
Fri Aug 24 17:48:58 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:49:00 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:49:45 2018: [debug  ] Previous message logged 5 times
Fri Aug 24 17:49:45 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:50:02 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:50:08 2018: [debug  ] Previous message logged 2 times
Fri Aug 24 17:50:08 2018: [debug  ] Accepted incoming connection from 192.168.94.230
Fri Aug 24 17:50:09 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:50:19 2018: [debug  ] Previous message logged 5 times
Fri Aug 24 17:50:19 2018: [debug  ] Accepted incoming connection from 192.168.100.1
Fri Aug 24 17:50:22 2018: [debug  ] Previous message logged 6 times
Fri Aug 24 17:50:22 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock
Fri Aug 24 17:50:45 2018: [debug  ] Previous message logged 11 times
Fri Aug 24 17:50:45 2018: [debug  ] Accepted incoming connection from 192.168.94.24
Fri Aug 24 17:50:52 2018: [debug  ] Accepted incoming connection from file:///var/run/kopano/server.sock

There are a few lines like

Fri Aug 24 17:47:24 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:47:24 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1114519
Fri Aug 24 17:47:24 2018: [debug  ] gSOAP error on processing request: SOAP_FATAL_ERROR

Update to 8.6.7 did not change anything.

Hi, the name of your database zarafa indicates you have legacy bug carried over likely to be fixed with kopano-dbadm k-1216 seee knowledge base: https://kb.kopano.io/ & https://kb.kopano.io/display/WIKI/kopano-dbadm+k-1216+troubleshooting. I know this as common theeme migrating Zarafa to Kopano for k4s. Hope that helps.
-TosoBoso

Thanks for your advice - I will check later.

I’d like to document that by raising the loglevel of kopano-backup to 6, I was able to track down to a few folders which can’t be backed up. By removing the contents of each affected folder (and purging the softdelete cache), I have progress.

Currently, kopano-backup complains on a problem with my calendar … <facepalm>

I assume a deeper bug: to me it looks as the error recovery code might have a problem. When the code runs into a MAPI error on an object, it does five retries, but if all of them are unsuccessful, the code does not seem to give up and proceed with the next object, but stick on the one failing, repeating to fail …

2018-08-25 12:57:08,805 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=0/5)
2018-08-25 12:57:15,225 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=1/5)
2018-08-25 12:57:21,648 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=2/5)
2018-08-25 12:57:28,068 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=3/5)
2018-08-25 12:57:34,492 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=4/5)
2018-08-25 12:57:40,917 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=5/5)
[ and again, instead of commencing to the next object ...]
2018-08-25 12:57:47,339 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=0/5)
2018-08-25 12:57:53,761 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=1/5)
2018-08-25 12:58:00,183 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=2/5)
2018-08-25 12:58:06,605 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=3/5)
2018-08-25 12:58:13,035 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=4/5)
2018-08-25 12:58:19,456 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=5/5)
[ and again, instead of commencing to the next object ...]
2018-08-25 12:58:25,878 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=0/5)
2018-08-25 12:58:32,299 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=1/5)
2018-08-25 12:58:38,723 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=2/5)
2018-08-25 12:58:45,143 - backup0 - WARNING - Received a MAPI error or timeout (error=0x8004010f, retry=3/5)

Just a theory, to be proven …

I don’t think I run into the kopano-dbadm k-1216 problem.

First, my server log does not complain refering to this problem. And second: it does in the past (a few updates ago), and I was aware on that issue and ran the command. However, I will run it again and see what happens …

Looks like someone just deleted rows from the lob table, and now of course e-mail have a dangling reference to attachment(s).

I had stability problems in the past - the server crashed a few times. This might have led to deleted rows.

The question now is: how to do a consistency test on the DB? kopano-fsck seems not to be able to detect such anomalies, yet fix them.

Or: how to identify objects from error messages. When the log reads

Fri Aug 24 17:47:25 2018: [error  ] ECDatabaseAttachment::LoadAttachmentInstance(): no row returned
Fri Aug 24 17:47:25 2018: [error  ] SerializeObject failed with error code 0x80000007 for object 1114519
Fri Aug 24 17:47:25 2018: [debug  ] gSOAP error on processing request: SOAP_FATAL_ERROR

how can I find object 1114519? If I was able to identifiy the message, appointment, …, I could delete it without any problem.

Opened a support Ticket KS-41558

… and requested the supportes to close it unprocessed. I found out what’s wrong, and the solution is at https://forum.kopano.io/topic/1697/database-corruption