Logos 4b fails on startup "Could not load file or assembly 'System.Data.SQLite"

Ian Shepard
Ian Shepard Member Posts: 32 ✭✭
edited November 2024 in English Forum

I've tried just about everything I can think of to get this working.  Logos was working fine for me up until I updated it today.  Pertinent information:

What I did: 

  1. Launch Logos, allow auto-update
  2. Received "Logos Bible Software 4 has encountered a problem and needs to close" message from Windows.  Clicked [Don't Send]
  3. Tried it again, same problem
  4. Launched installer again (manually from temp files), chose [Repair] - launched again, same problem
  5. Hit the forums, deleted the keymanager.db and catalog.db - relaunched, same problem
  6. Renamed the ..\Data\<gibberish>.<more>\ and ..\Downloads\<gibberish>.<more>\ directories, launched again, same problem
  7. Forced Windows Update, updated .NET framework, reboot, launched again, same problem

As of right now, there's not a lot that I can think of and I can't see anything in the forums that relate directly to this issue.

The log says this and I'm positive that's the problem:

  • Error ID: 7948
    Error detail: FileLoadException: Could not load file or assembly 'System.Data.SQLite, Version=1.0.65.1010, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Thoughts?  7522.Logos4.log1261.Logos4Crash.txt

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 36,357

    This is rather complex but the crash appears to be connected to the statistics database:-

    C:\Documents and Settings\Owner\Local Settings\Application Data\Logos4\Data\h4wybzsg.tyx\Statistics\Statistics.db

    Rename this eg. to Statistics.old and restart L4.

    When you launch L4 do you have to sign-in?

     

    Dave
    ===

    Windows 11 & Android 13

  • Ian Shepard
    Ian Shepard Member Posts: 32 ✭✭

    It opens a new statistics.db and a lock file (literally "Statistics.lock") right next to it, then fails. 

    No, I don't have to sign in.  I've also tried the "Blank Profile" thing that didn't work either.

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 12,199

    The log says this and I'm positive that's the problem:

    • Error ID: 7948
      Error detail: FileLoadException: Could not load file or assembly 'System.Data.SQLite, Version=1.0.65.1010, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

    It looks like the update didn't replace all the files on your system (I'm not sure why). Try this:

    1. Delete the file C:\Documents and Settings\Owner\Local Settings\Application Data\Logos4\System\System.Data.SQLite.dll

    2. Right-click the file C:\Documents and Settings\Owner\Local Settings\Application Data\Logos4\Install\Installers\Logos4.msi, choose Repair.

  • Ian Shepard
    Ian Shepard Member Posts: 32 ✭✭

    Deleting the files went without issue.  The installer didn't want to repair.  I then updated my other Windows machine in the house (without issue) and copied its ..\Logos4\System directory (except the *.config files) to a thumbdrive and put them on this system. 

    Same problem.

    So I deleted the statistics.db file and tried again - same problem.

    2010-03-17 00:57:43.8585 1 Info LocalFileDatabase Found existing database at C:\Documents and Settings\Owner\Local Settings\Application Data\Logos4\Data\h4wybzsg.tyx\Statistics\Statistics.db
    2010-03-17 00:57:44.1085 1 Info LocalFileDatabase Creating new database at C:\Documents and Settings\Owner\Local Settings\Application Data\Logos4\Data\h4wybzsg.tyx\Statistics\Statistics.db
    2010-03-17 00:57:44.4522 1 Error OurApp Unhandled exception: System.IO.FileLoadException: Could not load file or assembly 'System.Data.SQLite, Version=1.0.65.1010, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
    File name: 'System.Data.SQLite, Version=1.0.65.1010, Culture=neutral, PublicKeyToken=db937bc2d44ff139' ---> System.IO.FileLoadException: Could not load file or assembly 'System.Data.SQLite, Version=1.0.62.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
    File name: 'System.Data.SQLite, Version=1.0.62.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139'

    And on that bombshell, goodnight.

    If anyone else has any ideas, I'll start on those after I get home from work tomorrow. 

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 12,199

    So I deleted the statistics.db file and tried again - same problem.

    It may actually be a problem with the Logos4.exe.config file--the program should be looking for v1.0.65.1011, not 1.0.65.1010 or 1.0.62.0. Try replacing that file with the copy from the other computer and see if that helps.

    My other thought is that perhaps some other program has installed v1.0.62.0 in the GAC (Global Assembly Cache) and that's interfering with Logos 4. Our program should be loading the DLL from its installation folder, so I'm not sure this is actually the problem. Do you have the same programs installed on both computers, or are they set up fairly differently?

  • Ian Shepard
    Ian Shepard Member Posts: 32 ✭✭

    That made a lot of sense.  I checked the file and, sure enough, it was looking for the 1.0.65.1010 file as the new file.  Put the new config files in place and all is well.  Thank you!  I really appreciate your help!

  • Jeffrey S Gordon
    Jeffrey S Gordon Member Posts: 54 ✭✭

    This was a very useful thread.  I just got the same crash problem, edited the aforementioned config file directly (changing 1010 to 1011) and it seems to be starting up.