eM Client crashes after upgrading from v5 to v6

1

I’ll get the warning below after upgrading to eM Client v6. I’ve already followed this procedure:

https://discourse.emclient.com/emclient/to…

but that gives the sqlite3.dll is part of eM Client. Going back to v5 doesn’t work, the database has already been altered by eM Client v6 so the only option is to upgrade to the v6 version which doesn’t work :frowning:

I’m using a Win XP SP3 system. Any ideas how to solve this?

Kind regards,

Maarten

System.AccessViolationException: Poging tot het lezen of schrijven van beveiligd geheugen. Dit duidt er vaak op dat ander geheugen is beschadigd.
bij System.Data.SQLite.UnsafeNativeMethods.sqlite3_open_v2(Byte[] utf8Filename, IntPtr& db, SQLiteOpenFlagsEnum flags, IntPtr vfs)
bij System.Data.SQLite.SQLite3.Open(String strFilename, SQLiteConnectionFlags connectionFlags, SQLiteOpenFlagsEnum openFlags, Int32 maxPoolSize, Boolean usePool)
bij System.Data.SQLite.SQLiteConnection.Open()
bij DbRepair.DbTools.OpenConnection(String fileName)
bij DbRepair.Form1.CheckConsistency(Int32& affectedRows, DbException& consistencyError)
bij DbRepair.Form1.Check(Object state)

2

Hi, here is link to downgradable version http://www.emclient.com/dist/v5.0.196…

Anyway Google translator tells me this:

Attempted to read or write protected memory. This often indicates that another memory is corrupted.
(Poging tot het lezen of schrijven van beveiligd geheugen. Dit duidt er vaak op dat ander geheugen is beschadigd. )

Do you have any other software using eM Client’s database? After you will shut down eM Client look into task manager for mailclient.exe if it is still there.

Jan

3

Hi,

You saved my day, that version works!!

There is no other software using the eM Client ́s database and mailclient.exe is not running after shutdown.

Btw, I ́m not the only one with this problem:

https://discourse.emclient.com/emclient/to…

Cheers,

Maarten

4

I am happy that I could help you, I will report this issue to devs so I will not need to provider older version again.

Jan

5

So I have newest information, this is being resolved. Fix should be known soon.

Jan