Kerio Connect can consume a significant amount of RAM, eventually filling up the entire RAM and not leaving enough memory for other processes. This issue may be caused by a corrupted .journal.db file.
You can confirm this root cause by searching for the following (or similar) line in the Error log:
[Timestamp] SQLiteDbWriteCache.h: [Mail Path]/[Domain]/[Username]/.journal.db: runVacuum - SQLite error: code 11, error SQLITE_CORRUPT: database disk image is malformed
If you found the error mentioned above, please follow the steps below to resolve it.
- Stop Kerio Connect.
- Navigate to your Kerio Store folder; default paths are listed below:
- Navigate to the user folder found in the Error log (e.g.,
- Delete the .journal.db file that is reported in the error log.
- Start Kerio Connect.
Kerio Connect should now perform with normal RAM utilization.