Logos Crashes without opening

First, welcome to the forums! Sorry you are having troubles. [:S]

Vladimir Lugo said:

Please help!!

You have a corrupted database file, but I am not 100% sure which one. (I am only half techie, so please forgive me). Here is the error message: "Unhandled exception: System.Data.SQLite.SQLiteException (0x80004005): database disk image is malformed".

I will give you two suggestions. The first is no big deal, the second would be more troublesome. With Logos closed, try deleting the first .db file and restarting Logos. If that doesn't work, you can wait for more informed advice, or take a gamble. The second .db file will cause a FULL reindexing of your library. 

1. C:\Users\vladimir\AppData\Local\Logos4\Data\e1lsuzhe.k0o\Errors\Application\ErrorReportManager.db 

2. C:\Users\vladimir\AppData\Local\Logos4\Data\e1lsuzhe.k0o\PersonalBookIndex\LibraryIndex.db

Vladimir Lugo said:

I have attempted several things, like installing the latest version, uninstalling and reinstalling, opening it as an administrator, opening it with CTRL and choosing a blank template, but the results are always the same, it crashes when Preparing the library, step 2 of 3.

The best suggestion is ALWAYS to seek help before doing anything drastic. Reinstalling the software engine rarely fixes anything. In this case, you have a corrupted .db file. Reinstalling doesn't do anything, because the .db files stay in place unless you delete them! Plus, why delete all those files and redownload them when a simpler fix is available?

My advice would be to try .db #1. If that doesn't work, wait a few hours to see if a techie comes along to confirm my suspicion about #2. 

Vladimir Lugo said:

I even deleted all the files under the three Error directories that ended in .db, without success.

You shouldn't do that. Wait for someone to give you directions. You could cause more troubles for yourself if you don't. 

Vladimir Lugo said:

I then tried #2, also without success.

Did it perform a complete reindexing?

One last simple thing I should have suggested before: Have you tried opening to a blank layout? On windows, I <think> you press and hold the control key immediately after trying to open the application.