Logos 4 "has stopped working" message

Logos 4 was working fine yesterday.

I noticed it was indexing this morning. When I tried to open it this evening, I got the "Logos 4 "has stopped working" message".

I tried the "open with CTRL pressed", but no success.

Any solutions please.

Am I the only one that feels L4 is very fragile?

Thanks, Mike

Find more posts tagged with

Comments

Kevin Becker

Did you tell Logos to launch with a blank layout?

Try again and submit crash logs and we'll see if we can help.

Directions:

http://wiki.logos.com/Diagnostic_Logging
http://wiki.logos.com/Uploading_Logs

Mike Pearson

https://community.logos.com/discussion/comment/94193#Comment_94193

Hi Kevin,

Thanks for the very quick response.

I'm using L4 in Windows 7. I have the L4 icon on the taskbar and double click it. It's worked well like this for the last month or so. But today as I mention I got the "stopped working message".

When holding down the CTRL key I get:

1. Sign in.

2. Library update, followed 5 seconds later with the "Stopped working message".

I've attached the logs. Does it make sense?

Thanks,

Mike

5873.Logos4.log

6763.Logos4Indexer.log 2161.logos4setup[1].log

Clinton Wood

https://community.logos.com/discussion/comment/94208#Comment_94208

Hi there,

I just received exactly the same error message as Kevin above. Logs are attached7002.Logos4.log

Help appreciated!!! Win 7, 64-bit. Error part was:

"Error OurApp Unhandled exception: System.InvalidOperationException: Error reading postings. Document id out of range."

Is this a case of re-indexing?

thanks so much

Clinton

Peter Venable

https://community.logos.com/discussion/comment/94241#Comment_94241

"Error OurApp Unhandled exception: System.InvalidOperationException: Error reading postings. Document id out of range."

Is this a case of re-indexing?

Yes, that's what happens when a merge corrupts an index. The cure is to invoke the "rebuild index" command.

Mike Pearson

https://community.logos.com/discussion/comment/94193#Comment_94193

Hi Kevin,

Were you able to make sense of the logs?

My L4 hasn't been working for 36 hours now.

Thanks,

Mike

Kevin Becker

https://community.logos.com/discussion/comment/94666#Comment_94666

Mike,

According to Peter above the particular error message is a corrupted index. To force an index without starting Logos delete the contents of this folder (Vista/Win7) C:\Users\<UserName>\AppData\Local\Logos4\Data\<Random>\LibraryIndex. The AppData folder is hidden so you will have to enable viewing of hidden files to find this folder. After the folder is deleted start Logos 4 and it should fire up the indexer.

Mike Pearson

https://community.logos.com/discussion/comment/94676#Comment_94676

Hi Kevin,

You're a genius! Yes, L4 works.

Your instructions were step-by-step clear.

Many thanks,

Mike

PS does this mean the indexer is going to start all over? Although I have an Intel Core 2 Duo processor T6600 (2.2 GHz) it took many hours on the first index!!

Andy

https://community.logos.com/discussion/comment/94676#Comment_94676

Thanks Kevin, I had the same problem today as Kevin and you fix worked fine

Kevin Becker

https://community.logos.com/discussion/comment/94687#Comment_94687

PS does this mean the indexer is going to start all over? Although I have an Intel Core 2 Duo processor T6600 (2.2 GHz) it took many hours on the first index!!

Unfortunately, yes.

Doug Ford

https://community.logos.com/discussion/comment/94676#Comment_94676

Aloha,

Thanks for this instruction. Everything was fine (other than Logos 4 being slow even after all the tweaks I could find) until trying to type a little into an existing note. This caused an immediate "Logos 4 has stopped working . . ." alert and program crashed. Restarted, and identical problem. Some corruption must have taken place. Will now let it reindex.

Doug

Kevin Becker

https://community.logos.com/discussion/comment/132950#Comment_132950

Doug,

Lots of things can cause crashes. Index corruption was a frequent problem in 4.0a but isn't very common any more. The index rebuild might fix your problem or it might not. If it doesn't, get logs (see the links in my post above) and start a new thread with a description of the crash, start the thread title with "CRASH:". It'll get more attention that way and if your problem is a new bug the details will get to the developers so they can start work on a fix.

~Kevin