Bug: Indexer – No translation word

There are many instances of the Indexer crashing with IndexingException: No translation word for specified document position, usually on a Reverse Interlinear

Software version: 4.2.
Reported by Dave Hooton.
Forum link: http://community.logos.com/forums/t/27367.aspx
http://community.logos.com/forums/t/27446.aspx
http://community.logos.com/forums/t/27503.aspx
http://community.logos.com/forums/t/27517.aspx
http://community.logos.com/forums/t/27646.aspx

Status: confirmed

Working Solution:

From Dave Hooton
This is the solution that Tech Support have found:-

  1. Delete the NASB95.logos4, NASBOT.lbsrvi, NASBNT.lbsrvi, KJV1900.logos4, KJV1900NT.lbsrvi, and KJV1900OT.lbsrvi files.
    1. They are in C:\Users\userfolder\AppData\Local\Logos4\Data\uniquefolder\ResourceManager\Resources.
  2. Once the files are deleted, restart Logos 4 and enter the command Update Resources.
  3. Allow the program to download the updates and restart Logos 4 again.
  4. After Logos 4 loads check your library to make sure the Bibles have completely re-downloaded:
    1. Open the King James Version (1900) and make sure the Interlinear Data is available in the Old and New Testaments.
    2. Repeat with the New American Standard Bible (1995).
  5. If the books do not show up they may be still in the Downloaded folder.
  6. Close Logos 4 and go to the following location C:\Users\userfolder\AppData\Local\Logos4\Data\ uniquefolder \ResourceManager\
  7. Delete the ResourceManager.db file and restart Logos 4 to force discovery.
  8. After Logos 4 reopens repeat step 4, if the Bibles appear to confirm the interlinear information is there as well.

Let indexing complete and go from Step 4 above.



Logos Bible Software Wiki

Welcome, Guest! (sign in)