indexing failure

Page 1 of 1 (6 items)
This post has 5 Replies | 1 Follower

Posts 37
Dan | Forum Activity | Posted: Mon, Dec 27 2010 9:33 AM

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

 

Any advice? 

 

Thanks!

Posts 5573
Forum MVP
Rich DeRuiter | Forum Activity | Replied: Mon, Dec 27 2010 9:56 AM

Dan:
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)

Posts 37
Dan | Forum Activity | Replied: Tue, Jan 11 2011 7:00 PM

Thanks Richard, 

Here is my log file and index crash file:

 7853.Logos4IndexerCrash.zip

Any thoughts are really appreciated

Dan

Posts 5573
Forum MVP
Rich DeRuiter | Forum Activity | Replied: Tue, Jan 11 2011 10:45 PM

Dan:

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)

Posts 25602
Forum MVP
Dave Hooton | Forum Activity | Replied: Tue, Jan 11 2011 11:27 PM

Dan:

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.
    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.

Dave
===

Windows 10 & Android 8

Posts 3
Steven Allain | Forum Activity | Replied: Wed, Jan 12 2011 4:25 AM

Thanks thats fix worked for me also

Page 1 of 1 (6 items) | RSS