I’m working on a computer of a client of mine. The eM Client wouldn’t open since 3 days ago. It does not give any errors, nor does it open any windows except th DBRepair tool that’s found in the same installation folder. The repair checks the data files, but their aren’t any problems found.
I’ve tested a few things before asking for support here. First I backupped all of the data and I re-installed the program. (The most recent update was already installed by the way)
It’s still not working, however I went to the task manager to check if it was running, and it was indeed running the client. Yet the window isn’t showing up (even after waiting for a long time).
But here’s some other info, I found in total 3 installations of the EM client, one in the normal installation folders (C:\Program Files (x86)\eM Client), one in the Downloads (C:\Users\Username\Downloads) and one in the C drive (C:\eM client).
I deleted the other 2, and let the one in program files stay.
Here’s the computer system’s info:
Windows 8.1 Pro 64 bit
Intel Core i5-4460
8GB RAM
System language: Dutch
Model: MSI-7823
Intel HD Graphics 4600 Onboard
I’ve looked throughout the forums here and also Google AND Bing, but I can’t find anyone with the same problem. Please help us resolve this. Thank you.
eM Client (6.0.21040.0)
Windows: Microsoft Windows NT 6.2.9200.0, Framework: 4.0.30319.34014
The following error has occurred:
System.Data.SQLite.SQLiteException (0x80004005): database disk image is malformed
database disk image is malformed
bij System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
bij System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
bij System.Data.SQLite.SQLiteDataReader.NextResult()
bij System.Data.SQLite.SQLiteDataReader…ctor(SQLiteCommand cmd, CommandBehavior behave)
bij System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
bij System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
bij MailClient.Storage.Data.SQLite.DbRepository1..ctor(Compactor compactor, String indexTable, String[] readWriteDatabaseNames, String[] readOnlyDatabaseNames) bij MailClient.Storage.Data.DbCategoriesItemRepository1…ctor(Compactor compactor, String indexTable, String[] readWriteDatabaseNames, String[] readOnlyDatabaseNames)
bij MailClient.Storage.Data.SQLite.DbMailRepository…ctor(Compactor compactor)
bij MailClient.Storage.Data.RepositoryFactory.get_MailRepository()
bij MailClient.Storage.Application.Folder.CreateMailItemsCollection()
bij MailClient.Storage.Application.Folder.get_MailItems()
bij MailClient.UI.Controls.controlMailFolders.AttachUnreadCallbacks()
bij MailClient.UI.Controls.controlMailFolders.AttachCallbacks()
bij MailClient.UI.Controls.controlFolders.LoadNodes()
bij MailClient.UI.Controls.controlFolders.OnLoad(EventArgs e)
bij MailClient.UI.Controls.controlMailFolders.OnLoad(EventArgs e)
bij System.Windows.Forms.UserControl.OnCreateControl()
bij System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bij System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bij System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bij System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bij System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bij System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bij System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bij System.Windows.Forms.Control.CreateControl()
bij System.Windows.Forms.Control.WmShowWindow(Message& m)
bij System.Windows.Forms.Control.WndProc(Message& m)
bij System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bij System.Windows.Forms.ContainerControl.WndProc(Message& m)
bij System.Windows.Forms.Form.WmShowWindow(Message& m)
bij System.Windows.Forms.Form.WndProc(Message& m)
bij MailClient.UI.Forms.BaseForm.WndProc(Message& m)
bij MailClient.UI.Forms.BorderlessForm.WndProc(Message& m)
bij MailClient.UI.Forms.formMain.WndProc(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bij System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Hi, unfortunately this seems to be a database issue, I’m afraid some of the database files may have got corrupted while force quitting the application, you can try to download this database repair tool http://www.emclient.com/tools/dbrepairrebuildall.exe and check if the tool is able to restore your database files.
However I’m afraid that if the database repair tool fails to restore the database, it is not possible to restore the original data and a new database has to be created.
To setup a new database please navigate to your local folder > App Data > Roaming and rename or remove the current eM client database folder, next time you reopen the application eM Client should automatically create a new database.
Thank you for answering so quickly, I did every step you told me to do. I ran the repair and it was indeed restoring the database files. Yet the client itself still does not open. It only opens the DbRepair.exe program and that one closes automatically after 3 seconds. And the client’s process is running.
What do I do now? I’ll try running that repair tool again, and see if that might solve it. I’ll also try another clean install.
Though I might wonder if it could be a virus? I scanned the system once but I didn’t find any. Since it’s an email program is it vulnerable?
One last question, is it possible to convert the eM client’s data so that other email clients can recognize it? I backupped all the data, and if it’s possible we have at least that. But we’ll still try to fix the start up problem.
Hi again Jento, id the dbrepair tool finishes without showing any errors, you should be able to open the application, if not, can you try to create a new database folder and setup your accounts from scratch, to setup a new database, please navigate to Your local folder > App Data > Roaming, and rename or remove the eM Client database folder.
Reopen the application and new database should be automatically setup.
If it were that simple, we would’ve fixed the problem yesterday. I’ve done these steps 3 times and still, it won’t open. Something isn’t right, we’ve tried every step possible. Other steps like running as an admin, changing permissions so that the system may access it, restarting, updating, repair using the installer, scanning for virusses, or even deleting ALL traces of the program and installing again won’t fix it. Maybe it’s the PC itself causing the problem? Maybe because of the OS?
Also, I’ve found a folder named “inbox.imm” where .eml files are located in, where does this folder originally come from?
Thank you for you time Paul, I really appreciate it.
Hi again, if the process is running in the task manager, please try to run this utility http://www.emclient.com/tools/emstackdump.exe and run the utility when the application is not running but still is displayed in the task manager as a running process.
However the error states your database is not accessible by the application, so removing the current database folder as I suggested should resolve the issue. Are you sure you’ve removed the database from the right directory?
I found that post is related to a problem I also have…
I installed a fresh clean version of W8.1 a couple of weeks ago.
I installed emClient and reconfigured all my accounts.
Each time I’m closing the application, I can actually see it in the task manager go from ‘application’ to ‘process’. At this point it is not possible to reopen the app until I manually kill the emClient process.
So I tried to repair the db with the tool provided above: not helping.
So I renamed my old db directory to _OLD and restarted.
After few tries I was able to add the CalDAV account again (it requested a huge number of times the login/passd that I was carefully writing). It took few tries to have the certificate prompt displayed and accepted. Don’t know why.
After that I was able to close the app and reopen without any problem.
GOOD.
Then I started to add the email accounts and now I want to rip my hair of my head!!!
I can never add an account completely. I add all the information, and the emClient is SYSTEMATICALLY not remembering it and replace with default parameters that are not correct for me and it looks like in goes into a loop of retries until I kill it.
For the last couple of hours I cannot create any account. A nightmare.
I don’t even know where to force the parameters in config files.
My older AppData emClient dir is still working at the price of the ‘kill process’.
Please help as I’m close to give up … and I don’t want to …
Hello Nicolas, what version of eM Client are you currently using on your computer, can you please check the exact release of the application in Help > About or try to install the latest release using this installer, 6.0.22336.0 .
We’ve released a fix for the process not being terminated on application shutdown, however maybe you’re experiencing a different issue. If you’re being re-prompted for password with the password required box using your Gmail account, this release should also help you resolve the issue.
If you’re still experiencing issues, can you please make a screenshot of the issue and submit it to us here on the forum?
I was gonna write that the issue remained but byt the time I opened my web browser the process was gone!!!
After few tests, can say that it takes somewhere between 10s to 3min before the process ends on its own.
But it works.
I hope it won’t be an issue when Windows is closing.
Hello again Nicolas, glad it works, please make sure to let us know if you come across this or any other issue or questions about the application, we’ll be happy to help.
I’m afraid to say that the issue is back again.
It did work for a few days but then I realized that the program was not shutting down correctly upon a Windows Shutdown. I had the message back when I restarted.
Yesterday, the process did not even work after letting the night to the shutdown.
Hello Nicolas, what version of eM Client are you currently using on your computer, can you please check the exact release number in Help > About?
Make sure you’re using the latest release of eM Client, 6.0.22344.0 and if the issue persists, use the above submitted eM Client Stack Dump tool and create a stack dump once the issue occurs. So if the process is still active after you close the application, run the utility and submit the created stack dump file to my email [email protected] with a reference link to this forum topic.
and I don’t want to …