indexing failure

Dan
Dan Member Posts: 37 ✭✭
edited November 2024 in English Forum

For about 2 weeks L4 indexing popped up a window saying that it has failed to run. 

 

Any advice? 

 

Thanks!

Comments

  • Rich DeRuiter
    Rich DeRuiter MVP Posts: 6,729

    Dan said:

    For about 2 weeks L4 indexing popped up a window saying that it has failed to run. 

    This has been an issue for many people. It usually is a problem with one of the reverse interlinears (KJV1900, NASB95, and one time the NLT), in other cases folks have needed to rebuild their Bible index. If you follow the instructions here for enabling diagnostic logging, and post all your logs here, someone might be able to determine the cause and suggest a solution.

     Help links: WIKI;  Logos 6 FAQ. (Phil. 2:14, NIV)

  • Dan
    Dan Member Posts: 37 ✭✭
    https://community.logos.com/discussion/comment/206165#Comment_206165

    Thanks Richard, 

    Here is my log file and index crash file:

     7853.Logos4IndexerCrash.zip

    Any thoughts are really appreciated

    Dan

  • Rich DeRuiter
    Rich DeRuiter MVP Posts: 6,729
    https://community.logos.com/discussion/comment/211214#Comment_211214

    Dan said:

    Thanks Richard, 

    Here is my log file and index crash file:

     7853.Logos4IndexerCrash.zip

    Any thoughts are really appreciated

    Dan

    The crash log shows that you probably have a corrupt reverse interlinear, but it doesn't say which one. Please post your indexer.log too.

     Help links: WIKI;  Logos 6 FAQ. (Phil. 2:14, NIV)

  • Dave Hooton
    Dave Hooton MVP Posts: 36,339
    https://community.logos.com/discussion/comment/211214#Comment_211214

    Dan said:

    Thanks Richard, 

    Here is my log file and index crash file:

     7853.Logos4IndexerCrash.zip

    Any thoughts are really appreciated

    Dan

    This indicates a common error of late. The solution is:-

    1. Delete the NASB95.logos4,
      NASBOT.lbsrvi, NASBNT.lbsrvi, KJV1900.logos4, KJV1900NT.lbsrvi, and
      KJV1900OT.lbsrvi files.

      They are in
      C:\Users\userfolder\AppData\Local\Logos4\Data\uniquefolder\ResourceManager\Resources.
    Once the files are
    deleted, restart Logos 4 and enter the command Update
    Resources    .

    Allow the program
    to download the updates and restart Logos 4 again.

    After Logos 4 loads
    check your library to make sure the Bibles have completely
    re-downloaded:

    Open the King James
    Version (1900) and make sure the Interlinear Data is available in the Old and
    New Testaments.

    Repeat with the New
    American Standard Bible (1995).


    If the books do not
    show up they may be still in the Downloaded folder.

    Close Logos
    4 and
    go to the following location
    C:\Users\userfolder\AppData\Local\Logos4\Data\ uniquefolder
    \ResourceManager\

    Delete the
    ResourceManager.db file and restart Logos 4 to force
    discovery.

    After Logos 4
    reopens repeat step 4, if the Bibles appear to confirm the interlinear
    information is there as well.

    Dave
    ===

    Windows 11 & Android 13

  • Steven Allain
    Steven Allain Member Posts: 5 ✭✭
    https://community.logos.com/discussion/comment/211255#Comment_211255

    Thanks thats fix worked for me also

Categories