Logos Indexer crashes Logos 5

I have just installed Logos 5, but I have had this same problem before my upgrade using Logos 4. As soon as I run Logos, I get a mesage which says "Logos Bible Software 5 Indexer has stopped working. The problem details are as follows:

---------------------------------------------------------------------------------------------

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: logosindexer.exe

Problem Signature 02: 5.0.1.278

Problem Signature 03: 50cf773e

Problem Signature 04: Libronix.SearchEngine

Problem Signature 05: 5.0.1.278

Problem Signature 06: 50cf76c4

Problem Signature 07: 7e

Problem Signature 08: 6c

Problem Signature 09: System.ArgumentOutOfRange

OS Version: 6.1.7601.2.1.0.256.4

Locale ID: 7177

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

8611.Logos Log Files.zip

---------------------------------------------------------------------------------------------

If I run Logos with the Control key pressed, and I open with a blank layout, I am able to access resources (I just tried the NRSV). However, as soon as I click on the Home button I get a Logos 5 has stopped working message.

I have also attached the log files.

Find more posts tagged with

Comments

Bradley Grainger (Logos)

It looks like some of your index files are inconsistent with each other (I'm not sure why), which is causing the crash.

You can avoid it by deleting this folder, then restarting Logos 5: C:\Users\pag\AppData\Local\Logos4\Data\gz323ntk.22l\LibraryIndex

This will cause Logos 5 to re-index all your books when you start it, which may take a few hours.

Paul Grobler

https://community.logos.com/discussion/comment/450196#Comment_450196

Tx! I managed to start Logos using a blank layout and issued a rebuild index command, which seems to have the same effect as what you suggested.

Appreciate the quick answer.

FDA

https://community.logos.com/discussion/comment/450196#Comment_450196

Hello. I think I have the same problem. Logos 5 indexer just stops working. (Problem description logs are below.)

I tried to look for the folder you suggested I delete, but I couldn't find it.

Is there any other way to rebuild the index? What command should I issue, and how do I issue it?

Thanks!

One problem description:

Description:

Exception in TryCreateCore

Problem signature:

Problem Event Name: APPCRASH

Application Name: LogosIndexer.exe

Application Version: 5.0.1.291

Application Timestamp: 50f5abab

Fault Module Name: ntdll.dll

Fault Module Version: 6.1.7601.17725

Fault Module Timestamp: 4ec49b8f

Exception Code: c0000005

Exception Offset: 00038DC9

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

Another problem description from another crash:

Problem signature:

Problem Event Name: APPCRASH

Application Name: LogosIndexer.exe

Application Version: 5.0.1.291

Application Timestamp: 50f5abab

Fault Module Name: ntdll.dll

Fault Module Version: 6.1.7601.17725

Fault Module Timestamp: 4ec49b8f

Exception Code: c0000005

Exception Offset: 00038dc9

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

Mike

https://community.logos.com/discussion/comment/459784#Comment_459784

Hello Francis,

I apologize for the trouble. In order to troubleshoot this issue correctly, it may be necessary to give us a call. The faulting module appears to be a Windows component, so it may be wise to run Windows Update before calling.