Indexer stopped, and stops again if I command line start an index in L4

Brent Hoefling · February 2011

Dell Desktop PC

Vista Ultimate (32)

I regularly make purchases from pre-pubs, community pricing and even from the product list.

Indexing used to work, but for the last couple months or so, since about the end of last year, every time I get an update, and the index starts, it stops/crashes. L4 seems to be functional, but the index isn't complete. it begins and has about 16 hours, and then at some point the indexer stops (pop-up box below). Since I have been using my laptop most of the time, this wasn't' a problem, but recently my laptop has failed (need a new PS), and haven't gotten around to fixing it yet, so in the meantime wanted to use my desktop. but at this point, I have tried for three days to make the indexer start again, restarting my computer, relaunching L4 and command line starting the index - all to no avail, at this point I have at least discovered that it takes about 10 minutes for the indexer to stop once it starts, as I am watching it.

I want to be able to trust the system I am working on, but when I get the above error, it is hard to believe that it is searching and working correctly.

Kevin Becker · February 2011

Brent, typically an indexer crash can mean that you have some corrupted file that needs to be deleted and redownloaded. You need to enable diagnostic logging. Start Logos, enter the command Rebuild Index. When the indexer crashes find the Indexer log file and upload the logs to the forum. Then someone can review you log files and suggest a course of action.

Brent Hoefling · February 2011

https://community.logos.com/discussion/comment/220587#Comment_220587

8358.Logos4IndexerCrash.txt

3678.Logos4.log

Rich DeRuiter · February 2011

https://community.logos.com/discussion/comment/220658#Comment_220658

Brent Hoefling said:

8358.Logos4IndexerCrash.txt

3678.Logos4.log

This appears to be a known problem, the solution to which is as follows:

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.

To be sure, we'd need to see the indexer log as well (though that crash message looks like the same that the above solution addresses).

Kevin Becker · February 2011

https://community.logos.com/discussion/comment/220660#Comment_220660

Richard DeRuiter said:
To be sure, we'd need to see the indexer log as well (though that crash message looks like the same that the above solution addresses).

Brent, ignore this line. Richard copied this from another thread. You've already provided the logs [:)]

Rich DeRuiter · February 2011

https://community.logos.com/discussion/comment/220661#Comment_220661

Kevin Becker said:

Richard DeRuiter said:
To be sure, we'd need to see the indexer log as well (though that crash message looks like the same that the above solution addresses).

Brent, ignore this line. Richard copied this from another thread. You've already provided the logs

Actually, he did not provide the Logos4Indexer.log file, which would help us determine the error itself, and confirm that it was one of the above resources. The Logos4IndexerCrash.txt file only tells us the type of error (typical of the error with those reverse interlinears).

Kevin Becker · February 2011

https://community.logos.com/discussion/comment/220678#Comment_220678

Richard DeRuiter said:
Actually, he did not provide the Logos4Indexer.log file, which would help us determine the error itself, and confirm that it was one of the above resources. The Logos4IndexerCrash.txt file only tells us the type of error (typical of the error with those reverse interlinears).

Ah, I skimmed over the fact that it was a crash.txt