system crash

Crashing eM Client
1

System.IO.IOException: database disk image is malformed —> System.Data.SQLite.SQLiteException: database disk image is malformed bij System.Data.SQLite.SQLiteBlob.Read(Byte[] buffer, Int32 count, Int32 offset) bij MailClient.Storage.Data.BlobStream.Read(Byte[] buffer, Int32 offset, Int32 count) — Einde van intern uitzonderingsstackpad — bij MailClient.Storage.Data.BlobStream.Read(Byte[] buffer, Int32 offset, Int32 count) bij MailClient.Streams.StreamHelper.CopyStream(Stream inputStream, Stream outputStream, Nullable`1 cancellationToken, ProgressReporter reporter) bij MailClient.Storage.Data.DatabaseCopyTool.CopyContents(Table table, Boolean sortDesc) bij MailClient.Storage.Data.DatabaseCopyTool.CopyTableData(Table table) bij MailClient.Storage.Data.DatabaseCopyTool.CopyInternal(String specificTable, Boolean copyIndexesViewsAndTriggers) bij DbRepair.CorruptionChecker.CheckCorruption(RepairOptions repairOptions, CancellationToken token) bij DbRepair.CheckingProcess.Check(CancellationToken token) Data: Table: LocalMailContents databaseFile: e6cedf99-f449-435b-9de7-6c1075345caa\f6ecec00-c85e-463e-be59-09f662c3e97c\mail_data.dat

2

Generally there is no way to fix a malformed database, so you will need to rename the C:\Users_userrname_\AppData\Roaming\eM Client directory and start again.

3

but how comes that there is a malformed database? I have a similar problem but I need my data back… how to restore manually? all data saved on hard drive only. I don’t trust other forms of storage (Imap, clouds and those “newer” techniques…)

My error message:

System.ApplicationException: database disk image is malformed
database disk image is malformed
Line: 15
DELETE FROM mail_data.LocalMailContents WHERE NOT EXISTS (SELECT id FROM mail_index.MailItems WHERE id=mail_data.LocalMailContents.id);
   bei MailClient.Storage.Data.DbRepository1.ImportFromResource(IDbConnection connection, Stream myStream, CancellationToken token)    bei MailClient.Storage.Data.DbRepository1.ImportFromManifestResource(String resourceName, CancellationToken token)
   bei MailClient.Storage.Data.DbRepository1.Repair(RepairMode mode, CancellationToken token) &nbsp;&nbsp; bei MailClient.Accounts.ItemRepositories.Repair(RepairMode mode, CancellationToken token) &nbsp;&nbsp; bei DbRepair.ConsistencyChecker.CheckConsistencyForAccount(String accountDirectory, RepairMode mode, CancellationToken token) &nbsp;&nbsp; bei DbRepair.ConsistencyChecker.\<\>c\_\_DisplayClass2\_0.<check>b__0(String p)<br alt="" name="" rel="" target="" title="" type="" value=""> bei DbRepair.PerAccountExecutor.Execute(String dataStoreLocation, Func2 action)
bei DbRepair.ConsistencyChecker.Check(RepairMode mode, CancellationToken token)
bei DbRepair.CheckingProcess.Check(CancellationToken token)
Data:
ResourceName: MailClient.Storage.Mail.Data.DbMailRepository.consistency.sql
DatastoreLocation: C:\Users\tw\AppData\Roaming\eM Client<br alt="" name="" rel="" target="" title="" type="" value="">

THX

4

You can try running the database repair tool manually, but I don’t think it will make any difference. You will find it at C:\Program Files (x86)\eM Client\DbRepair.exe

But there is not really any way to recover from that other than to restore from your last backup. If you are using POP3 then you absolutely need to make regular backups. At least with IMAP or Exchange all eM Client does is provide a cached copy of what is on the server, so if the database is corrupt you can always resync with the server. With POP3 the messages are generally deleted from the server so there is no second copy anywhere.