So while my eM client doesn’t crash so often (once a month?) it does take 2 hours to do the corrupted database check.
How do I speed that process up? Is there a way of reducing the size of my database while keeping the information elsewhere?
thanks!
2 Likes
If you are getting a 2hr database check then sounds like your mail database has got a big error
in it somewhere, and you should really be looking at deleting your mail database and starting again.
If you have an eg: IMAP type account i would personally uninstall the program and delete the database on uninstall and then download the same or later version from the eM Client ver history page and reinstall & setup as new again.
https://www.emclient.com/release-history?
You can check what current version you have via “Menu / Help / About”.
If you then keep on getting checking for errors on startup, make sure you are exiting the program and waiting aprox 5secs before shutting down your computer so the database closes correctly.
Sometimes database checking errors on startup can also be caused by “other background programs” interfering with eM Client closing correctly so you think it’s closed ok, but it’s infact still open in the background when you shutdown.
You can dblcheck it’s really closing after you have exited in the task manager for Windows and Mac.
Thank you for this.
Currently I have version 8.2.1473 - eM Client does not crash often at all, but yes when it does there is a two hour wait while it does a database check.
Deleting my email mail database is not an option as I have to dig through old emails quite frequently. I also have 14k contacts. If I could dump the old emails in a different searchable archive that might be an option…?
Thank you very much for your quick response in any case!
And now a similar message:
[IMAP]NO sockio_write_msg_timed() failed, rc=18446744073709551615.
What were you doing in eM Client when you got that error ?
Sending an email, which sent successfully. But gave me the error anyway.
Did the sent email have a large file attachment with it ? and if it did how long did it take to send.
No, they didn’t have attachments.
Ok as you are getting sockio_write_msg_timed() failed even “when sending text emails” without attachments (even though it sends ok), sounds like you may have some sort of either optional program scanning / delaying your outgoing mail like an eg: Antivirus scanning program causing the msg_timed() failed error, or your smtp connection is very slow and just takes forever.
Do you have any optional Antivirus scanning programs running, or optional Internet Security programs, or VPN’s etc ? If you do, try disabling those to test to see if any of those are the cause of the msg_timed() failed error. You shouldn’t normally be getting message timeout errors.
Hmm, there might be an antivirus or anti spam program? I’ll take a look. No VPNs though. Thank you again for the suggestions.
Mine was checking for four hours and counting, so I eventually “cancelled” the database check. That has been “cancelling” for half an hour now. It’s ridiculous, I can scan and back up my whole PC in an hour.
Yes. This is still a problem. It takes too long. I always just cancel and let eM Client load and it seems to work fine. Just like everyone else, I don’t have time to wait.
Suggestion to the eM Client developers: Assuming that the process cannot be any faster, allow eM Client to check the database in the background while it is running.
1 Like
Cancelling the database check is extremely dangerous. If the data is not checked, and you cancel it and open the database, it can result in irreversible loss of data.
Better is to shut down eM Client correctly so that it doesn’t have to repair the database on start. Or, if it is crashing, open a support ticket so the cause can be determined.
100%. The database check takes more than 90 minutes, i can’t just stop work. So I cancel the check every time (maybe once a week?). I wish there was a better way, but sometimes eM just locks up or shuts down. If the database ever does get corrupted, I hope the backup structure works.
The time it takes mostly depends on where the database is stored. If it is on a mechanical disk, read/write operations are 100s of time slower than SSDs, so it will take some time.
While we never recommend you have the database on external storage, like a USB disk or network share etc. because that will cause errors, that could be even slower.
So better to discover why it is crashing, and fix that, than take the chance of irreversibly losing your data by cancelling the necessary repair.
Clearly its time to upgrade my computer. Well, when it crashes it sends a log and I get to say I was “checking emails” at the time. I assume if it is something obvious they’d do a fix…?
If you can contact me directly on [email protected] and give me the email address you entered in the crash report, I can have a look and see what caused the crash.
This is a bit ridiculous. So the solutions are 1) Delete email and reinstall 2) Properly exit client prior to shutting or whatever?
Like seriously?
Outlook doesn’t require us to do all this work around for a database cleanup, which is a tool problem and should be handled by tool without the consumer having to bear the pain of it. The question is, why does it get corrupted so easily? So damn fragile.
I have an i7 processor fast enough with an SSD drive, yet its annoying every morning I have to load the damn client, get coffee, then come back. I shouldn’t have to shut down all my application manually before I shut the computer down for the night. If I trigger windows shutdown, you app should see that event and start shutting itself down before it releases that service.
Figure it out guys. Hint hint, what does Outlook do? I’ve never had a corrupted database error in the life of that client.
I shouldn’t have to shut down all my application manually before I shut the computer down for the night. If I trigger windows shutdown, you app should see that event and start shutting itself down before it releases that service.
When you shutdown, Windows just forces programs to close, but “does not automatically wait for them to close”. The open program / process just gets killed, so eM Client will then have to do an automatic repair on the OS restart due to the SQL mail database “was still open in memory” at the time, which then if that is happening alot can cause permanent corruption in your mail database leading to sometimes having to delete it and start again brand new. Some different type of programs might survive forced shutdown, but not eM Client.
So you have 2 options. Either “shutdown eM Client before you shutdown Windows”, or “shutdown in sleep mode”. Either way works for for me on Windows 10 & 11 and Mac OS Sonoma & Sequoia.
Also if you have a Windows laptop and normally slam / close the lid if your not using it for along time, “configure the OS to sleep rather than shutdown on lid closure” to avoid repairing as @skybat advised in his post in another thread.
2 Likes