I was working along just fine, and closed Logos so the resource that wanted to load would load. When I restarted, it immediately crashed and now it won't start at all.
This isn't my 32-bit system, but rather is a 64-bit system.
And it's frustrating!
Here's what logs I can collect (hard to get logs when it won't start).
...and why do I ALWAYS get this screen when I upload logs?
Looks like a corrupt index. Delete C:\Users\borenjb\AppData\Local\Logos5\Data\eymcyonl.yow\LibraryIndex and restart Logos.
Did this. Tried to restart and it crashed again.
Re-deleted the file, then restarted the computer.
Indexer started on its own, and it says it is indexing, but won't give an indication of where in the process, and I don't want to try to open Logos until it is done.
After a little over 3 hours of indexing, it got to 98%, then seems to have frozen.
Is there some way to make it finish that last 2%?
This is really starting to get frustrating.
After about 3.5 hours, I got tired of it and killed the process.
Started the software. It actually came up this time, and this was my reward:
I have hundreds of free apps that run just fine, every time. Why won't this seven-thousand-dollar software package run?
Do you have an indexer log (it would have been helpful for the 98% session, but that would be overwritten by the current 1% session)?
I suppose not, then.
It is currently at about 21%, which is about four times faster than last time, but still on target to be another two hours.
Do you have a current indexer log in the Logos Log Files folder? Please upload if you do
No, Dave. There's nothing there but the crash.txt from earlier this afternoon. No indexer files.
OK, it's 10:53PM and the indexing that started today around 3PM is finally finished. The program opened normally. I haven't tried anything with it yet. I suppose I'll start another thread if it crashes again.
Where's that Advil?
It looks like the crash had something to do with connecting to an existing running Indexer. You could probably stop the crash (at the cost of restarting indexing) by killing the Indexer then launching Logos.
Is it possible that Logos or the Indexer was running elevated (as admin) but the other wasn't?
I don't see how, but then, I'm not a IT specialist. This was a personal computer for which I have sole account access and am set up as administrator.
I ran a few searches with it this morning and it didn't crash. Maybe it'll hold together this time.
I feel like the belly gunner on the Memphis Belle.
I suppose I'll start another thread if it crashes again.
Yes, but enable permanent logging so that detailed logs will be available.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
