Logos Indexer Stopped Working (after upgrade to 5.2 RC 1)

I was running Logos and noticed the yellow alert icon. I clicked on it to download/install an upgrade. When Logos started back up again (presumably it was now running version 5.2 RC 1) it still had the yellow alert icon, this time telling me there were some resources to update, so I clicked to download those. I switched to some other app to keep busy while the download was happening. Next thing I knew there was an error message on my screen saying the Logos Indexer had stopped working.

Here are all the log files from today. LogosIndexerCrash.txt had not been updated recently, so I didn't include that one.

UPDATE: I saw that, though the Indexer had stopped working, Logos was still running after I closed that error box. I noticed that the alert icon was still there, so I tried to click again to download resources, and nothing happened. Here's a video of that interaction: http://www.screencast.com/t/hHdNkPTLjJj

Third issue: the icon for my Logos program in my taskbar area (Windows 7) turned into a generic icon:

LogosIndexerCrash 20131107.zip

Find more posts tagged with

Comments

Dave Hooton

There was no crash info and the Indexer's log indicated that it was cancelling indexing to download an update. What does Windows Event Viewer say about this?

Does restarting Logos resume the download?

Graham Criddle

Hi Rosie

Third issue: the icon for my Logos program in my taskbar area (Windows 7) turned into a generic icon:

This was an issue during beta testing and was fixed in beta 3.

However, as per the release notes for that beta:

Fixed issue with pinned taskbar icons being replaced with blank file icons upon updating – see Known Issues. (See this thread.)

Taskbar icons pinned before 5.2 Beta 1 may still be replaced with a blank icon. Repinning after Beta 1 should no longer be replaced.

I think if you refresh the icon manually this time it should be ok for subsequent updates.

Graham

Rosie Perera

https://community.logos.com/discussion/comment/541298#Comment_541298

There was no crash info and the Indexer's log indicated that it was cancelling indexing to download an update. What does Windows Event Viewer say about this?

Faulting application name: LogosIndexer.exe, version: 5.2.0.41, time stamp: 0x527aab0b
Faulting module name: Libronix.DigitalLibrary.Logos.dll, version: 5.2.0.41, time stamp: 0x527aaafc
Exception code: 0xc0000005
Fault offset: 0x00055cf8
Faulting process id: 0x3c1c
Faulting application start time: 0x01cedc1046d8c0db
Faulting application path: C:\Users\Rosie Perera\AppData\Local\Logos5\System\LogosIndexer.exe
Faulting module path: C:\Users\Rosie Perera\AppData\Local\Logos5\System\Libronix.DigitalLibrary.Logos.dll
Report Id: 9bc5b17c-4803-11e3-a900-20cf3055f406

Copy from the Details tab:

6378.LogosIndexerCrash (Event Viewer Details) 20131107.txt

Does restarting Logos resume the download?

Not automatically, but when I requested to start the download over again it began and continued without further problems. However it's disturbing that it should cause the Indexer to crash when cancelling the indexing to download an update. Should be able to just exit gracefully without scaring the user.

I think if you refresh the icon manually this time it should be ok for subsequent updates.

Thanks. I've noticed this problem in the past and have always refreshed the icon manually by unpinning/repinning. It's gotten to be annoying, and I'm glad they've finally found and fixed the problem.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/541464#Comment_541464

Faulting application name: LogosIndexer.exe

Deleted 4 Bible Resources, which were being indexed when crash happened:

LLS:ALXAFRCSPWARSCAELAT
LLS:APLGYSPCTCLSOCTVSLAT
LLS:CVLWARSCAELAT
LLS:GLLCWARCAELAT

Launching Logos 5.2 RC 1 causes file not found error for Indexer.

Keep Smiling [:)]

Dave Hooton

https://community.logos.com/discussion/comment/541558#Comment_541558

Launching Logos 5.2 RC 1 causes file not found error for Indexer.

Because of the deleted bibles? What steps did you take after this? Is the log available?

Was there a crash log for the original crash (it could be in the Error log if the crash log was overwritten)?

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/541584#Comment_541584

Was there a crash log for the original crash (it could be in the Error log if the crash log was overwritten)?

No crash information was written to LogosIndexer.log file:

4024.LogosIndexer.log

No error log was created.

Keep Smiling [:)]

Bradley Grainger (Logos)

If you're getting a repeatable crash in the indexer (that's being logged in Event Viewer), please use ProcDump to capture a crash dump of the program (make sure to use "LogosIndexer.exe" in the command when you run it, not "Logos.exe"): http://wiki.logos.com/ProcDump

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/541558#Comment_541558

LLS:ALXAFRCSPWARSCAELAT
LLS:APLGYSPCTCLSOCTVSLAT
LLS:CVLWARSCAELAT
LLS:GLLCWARCAELAT

Logos downloaded resources, then indexed OK so crash did not repeat.

Keep Smiling [:)]