I’ve been using eM Client for years and it has been perfect with no issues
However about 1-2 months ago the program usually can’t start due to a corrupt database but it could repair itself after trying to start it a few times to which it would work again
A few weeks of this and now the program can no longer start or repair itself at all so I’ve reinstalled it multiple times and used a backup just to have it work for the day then to have the same problem the next day or it only works for a few hours before crashing and being corrupt
I’ve gone back to version 9 and used an even older backup (as the newer backup was for 10) and its been working perfectly fine
A week later and now having the exact same problem again where its corrupt and it just can’t fix itself or it fixes itself then instantly crashes after launching
Is there anything I can try that Isn’t reinstalling to try and stop this from happening
If it is a database issue, reinstalling won’t fix it as the application and the database are separate. And if the error is in the database that was previously backed up, and you restore that, you will probably get the error again.
It comes down to the error reported when trying to repair it. If you send that to us (instructions are given when you get the error) we can tell you more about the cause and how to recover from it if possible.
I do have the same problem, EMclient never showed up and keeps trying in “repair database” and exit with error :
“Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 11: ‘vtable constructor failed: MailNotesIndex’.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteCommand.PrepareAndEnumerateStatements(Stopwatch timer)+MoveNext()
at Microsoft.Data.Sqlite.SqliteCommand.Prepare()
at MailClient.Storage.Mail.Data.DbMailRepository…ctor(DataStore dataStore, IMailClassifier classifier, String dbLocation, SingleFileDatabaseContext singleFileDatabaseContext)
at MailClient.Accounts.ItemRepositories.Open(DataStore dataStore, IMailClassifier mailClassifier, String accountPath, AccountType accountType, String singleFileDatabaseName)
at MailClient.Accounts.ItemRepositories…ctor(DataStore dataStore, IMailClassifier mailClassifier, IAccount account, String accountPath, AccountType accountType, String accountName, String protocolName)
at MailClient.DbRepair.ConsistencyChecker.CheckConsistencyForAccount(String accountDirectory, RepairMode mode, CancellationToken token)
at MailClient.DbRepair.ConsistencyChecker.<>c__DisplayClass3_0.b__0(String p)
at MailClient.DbRepair.PerAccountExecutor.Execute(String dataStoreLocation, Func`2 action)
at MailClient.DbRepair.ConsistencyChecker.Check(RepairMode mode, CancellationToken token)
at MailClient.DbRepair.CheckingProcess.Check(CancellationToken token)”
Even after a few tries…
Do you know how to repair the database with an outside tool ?
Regards
Finally found the problem and it doesn’t seem to be an eM client problem
My 14900KS is failing and that for some reason causes eM client to crash and corrupt itself every single time
I switched back to my old 14700K and its working perfectly fine now
My 14900KS is failing and that for some reason causes eM client to crash and corrupt itself every single time
Yes there was many programs crashing with the i9 CPU & alot of Motherboards particularly in the Gaming side of things. This was mainly a problem with overclocking.
There is new firmware & updates from Intel and the Motherboard manufactures to fix those i9 crashing issues, that were all completed by the end of October.
So you need to contact your Motherboard manufacturer as to what updates you need. They will then advise (after updating), what Motherboard bios settings you need to change to fix that.
No. There is a well-known issues and defect with Intel 13 and 14 gen CPUs.
Severe enough that it causes internal damage to the cpus, no matter what bios settings.
Consumer and enterprise.
Just Googling this issue will give you the long story. Has nothing to due with user overclocking.
Anyone with a failing Intel 13th or 14th gen cpu, needs to get it replaced, AND update their mother board bios to the newest version, as Intel claims such update will prevent any further damage to a cpu. The BIOS update will not fix any already damaged cpu.
Yes i know about the 13th and 14th gen CPU’s as had heaps of friends i had to update their CPU’s and Motherboard settings recently to fix crashing late this year with i7 CPU’s.
But this did also affected alot of i9 CPUs “and certain Motherboards” from many sites i read and they also had to get new firmware / bios updates. So if @Thenijiway is getting crashing with his i9 CPU, then he needs to contact his Motherboard Manufacturer to get that sorted out.