database controletool

System.ApplicationException: SQL logic error or missing database
table “LocalMailContents” already exists
Line: 227
CREATE TABLE mail_data.“LocalMailContents” (
“id” INTEGER NOT NULL CONSTRAINT fk_LocalMailContents_id REFERENCES “LocalMails”(“id”) ON DELETE CASCADE,
“partName” TEXT,
“contentType” TEXT,
“contentId” TEXT,
“contentDescription” TEXT,
“contentTransferEncoding” INTEGER,
“contentMD5” TEXT,
“contentDisposition” TEXT,
“contentLanguage” TEXT,
“contentLocation” TEXT,
“contentLength” INTEGER,
“synchronizationKey”,
“partHeader” BLOB,
“partBody” BLOB,
PRIMARY KEY(“id”, “partName”));
   bij MailClient.Storage.Data.DbRepository1.ImportFromResource(IDbConnection connection, Stream myStream, CancellationToken token)    bij MailClient.Storage.Data.DbRepository1.CheckSchema(String databaseName, String resourceName)
   bij MailClient.Storage.Data.DbRepository1..ctor(DataStore dataStore, String location, String indexTable, String[] readWriteDatabaseNames, String[] readOnlyDatabaseNames)    bij MailClient.Storage.Data.DbItemRepository1…ctor(DataStore dataStore, String dbLocation, String categoryNamesTable, String indexTable, String[] readWriteDatabaseNames, String[] readOnlyDatabaseNames)
   bij MailClient.Storage.Mail.Data.DbMailRepository…ctor(DataStore dataStore, String dbLocation)
   bij MailClient.Accounts.ItemRepositories.Open(DataStore dataStore, String accountPath, AccountType accountType)
   bij MailClient.Accounts.ItemRepositories…ctor(DataStore dataStore, String accountPath, AccountType accountType)
   bij DbRepair.ConsistencyChecker.CheckConsistencyForAccount(String accountDirectory, RepairMode mode, CancellationToken token)
   bij DbRepair.ConsistencyChecker.<>c__DisplayClass2_0.b__0(String p)
bij DbRepair.PerAccountExecutor.Execute(String dataStoreLocation, Func`2 action)
bij DbRepair.ConsistencyChecker.Check(RepairMode mode, CancellationToken token)
bij DbRepair.CheckingProcess.Check(CancellationToken token)
Data:
AccountType: Mail
DatabaseLocation: C:\Users\dirka\AppData\Roaming\eM Client\c460d606-aca9-4d9e-8a66-4425502c4faa

I think because this is pointing to synced data, you could remove the account from eM Client and then add it again. See if that makes any difference.