Logos Bible Software 5 indexer stopped working

I just finished downloading books I bought and after that it started indexing. However, I did not give it time to finish. I just closed my laptop. When I opened it later to continue indexing it gave me this error message and wouldn't even open the program. The error reads, "Logos Bible software 5 indexer stopped working"

Find more posts tagged with

Comments

Lynden O. Williams

Have you restarted the computer and Logos? If that fails, then use control panel and try to repair it.

Getachew Yohannes

https://community.logos.com/discussion/comment/579646#Comment_579646

Have you restarted the computer and Logos? If that fails, then use control panel and try to repair it.

Yes I have tried everything I could but there is no any remedy. You said use the control panel to fix it. Can you say a little bit more on that? What should I do in the control panel?

Those of you who encountered similar problems, please help me. The error log I received was as follows:

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: logosindexer.exe

Problem Signature 02: 5.2.0.136

Problem Signature 03: 5304e12a

Problem Signature 04: System.Data.SQLite

Problem Signature 05: 1.0.86.24

Problem Signature 06: 51d33134

Problem Signature 07: b0

Problem Signature 08: 88

Problem Signature 09: System.Data.SQLite.SQLite

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Graham Criddle

https://community.logos.com/discussion/comment/579945#Comment_579945

If you haven't already done so please enable full diagnostic logging as per http://wiki.logos.com/Diagnostic_Logging and then post logs to this thread (using the paperclip icon) after a failed start attempt.

Getachew Yohannes

https://community.logos.com/discussion/comment/579956#Comment_579956

If you haven't already done so please enable full diagnostic logging as per http://wiki.logos.com/Diagnostic_Logging and then post logs to this thread (using the paperclip icon) after a failed start attempt.

7450.Logos.zip

I have attached the log file.

When I tried to open Logos it wouldn't allow me. It crashes immediately giving the message, "Logos 5 indexer has stopped working" it asks me to search for solution online and then closes the program.

Thanks

Graham Criddle

https://community.logos.com/discussion/comment/579962#Comment_579962

I have attached the log file.

Thank you

This states that one of the Logos databases has become corrupted.

But there isn't enough information for me to identify which one.

Some options:

wait to see if anyone else can glean some more information from the log file
contact Logos customer support and see if they can advise
upgrade to Logos 5.2a RC2 - available at http://community.logos.com/forums/t/82688.aspx. One of the features of this release is that it automatically detects and repairs database corruptions of this type. But please note that this is still technically a beta release and may introduce other problems.

Graham

TCBlack

https://community.logos.com/discussion/comment/579945#Comment_579945

Have you restarted the computer and Logos? If that fails, then use control panel and try to repair it.

Yes I have tried everything I could but there is no any remedy. You said use the control panel to fix it. Can you say a little bit more on that? What should I do in the control panel?

I believe Lynden is referencing the add/remove programs applet in the control panel, if you right click on Logos In that, you should should be able to choose a repair option.

I have looked at your logs and can't see much more than what Graham pointed out. The point of failure at line 230 follows the creation of several databases all related to the indexer. (190, 219-227) Line 231 references txt.monograph.bible right before the database disk image is malformed. It almost seems like it is only the bible index - but I'm no log reading professional.

Adding to the suggestions above by Graham, you might let the indexer crash, keep Logos open and issue one of these commands in the command bar:

Rebuild bible index

Rebuild Index

The second one will be comprehensive, and forcing a full rebuild might bypass the problem - or just re-encounter it. Either way, if you could pass on other logs as well such as the indexer log that would help more.

Getachew Yohannes

https://community.logos.com/discussion/comment/579967#Comment_579967

Thank you Graham. My problem is now solved after I installed the beta version (5.2a). I really appreciate your help.

Getachew Yohannes

https://community.logos.com/discussion/comment/579989#Comment_579989

Thank you all. I have installed 5.2a (the beta version) and it is now working. Thanks.

Getachew Yohannes

Graham Criddle

https://community.logos.com/discussion/comment/580029#Comment_580029

Thank you Graham. My problem is now solved after I installed the beta version (5.2a). I really appreciate your help.

Getachew Yohannes

That is great news. Thanks for posting back.

Dave Hooton

https://community.logos.com/discussion/comment/579989#Comment_579989

I have looked at your logs and can't see much more than what Graham pointed out.

FYI it was the Library Catalog.db (in the stack trace at line 238) which was discovered at line 68! However, 5.2a will quickly make us diagnosticians redundant!

TCBlack

https://community.logos.com/discussion/comment/580209#Comment_580209

Thanks Dave, your log reading skills were always far beyond me.