Help needed: Errormessage immediately after starting eM Client

1

Hi everybody. I’m using eM Client since years on two computers at home and i’m very happy with it. Until now. Since some days appears an errormesage on my son’s computer immediatly after starting eM Client:

“C:\Windows\system32\napinsp.dll is not intended to run under Windows or contains an error. Reinstall the application or ask a system admin.”

After clicking on OK a second message appears:

“An error appeared and does not allow to continue. The application will be closed” Then I am asked to describe the error.
After clicking on Weiter (= Continue) some checks are performed:

Clicking on Details leads to:

Clicking on Zeige Fehler (=show error; at the 2. picture) I get a lot of text (57 pages in Word).
I substituted the napinsp.dll file - witout success.
I reinstalled eM Client - no succes.

Any idea what the origin of the error is and how to fix it?
I would appreciate any help very much.

Regrds,
Stephan

2

Hi Stephan,
I would really appreciate seeing the actual error details, first 20-30 rows should be enough.
I am afraid the issue will be with a corrupted database though, have you made any backups of your database before?

Regards,
Olivia

3

Hi Olivia,
no db backups, unfortunately. Which kind of data are stored at the database? What will be lost in case …?
And here the beginning of the error details:

eM Client (6.0.24144.0)

Windows: Microsoft Windows NT 6.1.7601 Service Pack 1, Framework: 4.0.30319.34209

The following error has occurred:

System.Data.SQLite.SQLiteException (0x80004005): unable to open database file

unable to open database file

   bei System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)

   bei System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)

   bei System.Data.SQLite.SQLiteDataReader.NextResult()

   bei System.Data.SQLite.SQLiteDataReader…ctor(SQLiteCommand cmd, CommandBehavior behave)

   bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)

   bei System.Data.SQLite.SQLiteCommand.ExecuteDbDataReader(CommandBehavior behavior)

   bei System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()

   bei MailClient.Storage.Data.SQLite.DbFolderRepository.Store(IFolder item)

   bei MailClient.Storage.Data.SQLite.DbRepository1.Add[ST](Object senderContext, IEnumerable1 items, Action`1 storeCallback)

   bei MailClient.Storage.Data.SQLite.DbRepository1.Add[ST](Object senderContext, IEnumerable1 items)

   bei MailClient.Storage.Application.Folder.CreateFolder(Folder folder)

   bei MailClient.Accounts.AccountManager…ctor()

   bei MailClient.Accounts.AccountManager.Initialize()

   bei MailClient.Program.Main(String[] args)

 

 

" rel=“nofollow”>http://emclient.com/ns/report">;

 

    eM Client

    6.0.24144.0

 

  false

 

    Microsoft Windows NT
6.1.7601 Service Pack 1

   4.0.30319.34209

 

 

   System.Data.SQLite.SQLiteException

    unable to open database file

unable to open database file

    System.Data.SQLite

   

     

       

         System.Data.SQLite.dll

         100663598

         System.Data.SQLite

          System.Data.SQLite.SQLite3

          Reset

         

           

             System.Data.SQLite

             System.Data.SQLite.SQLiteStatement

              stmt

           

         

       

Regards,
stephan

4

Huhu, anybody there?

5

Hi,
I’m very sorry for the late reply, unfortunately, your database seems corrupted.
You’ll need to delete the active database and either set up a new one or restore from an older backup.
Your database is located in C:\Users\your windows user account\AppData\Roaming\eM Clientif you haven’t changed the default location.

Regards,
Olivia

6

Hi Olivia

Thanks for your answer.
Meanwhile I deinstalled eMClient again, deleted all folders of eMClient (including the one you mentioned) and installed EMClient again. The result is that the error still occurs. I am nearly desperate.
Any idea what I could do to be able to use eMClient again?

7

Hi,
since you started over with a new database, can you copy the error detail here again, in case the reason for the crash changed?
I’ll forward it to our developers, but it would be best to have the most current data available.

Regards,
Olivia