Cannot Start 6 "Logos Bible software has stopped working"

Attempting to install Logos 6. Install works fine and indexing works fine. right after synchronization Crashes with message Logos bible software has stopped working. A Problem has caused the program to stop working correctly.... Close program. Did a complete uninstall, then reinstall of 5, five worked. updated to 6. got the error. complete uninstall, cleaned registry, restarted. Installed 6. Same error

6.0b SR-2, version 6.0.2.0075 x64 on Microsoft Windows NT 6.3.9600.0)

4375.Logos.log

Find more posts tagged with

Comments

Mark Smith

Max, is this the only current log in your Logos Log files folder? It does not show a crash.

Do you have an Error or Crash Log, etc? Zip all of them together and attach them to a follow-up post.

Wolfe Family

5074.LogosError.zip

Wolfe Family

https://community.logos.com/discussion/comment/695188#Comment_695188

Please help, I have to teach a Bible study at 6:00 am tomorrow!!!! [:)]

Mark Smith

https://community.logos.com/discussion/comment/695188#Comment_695188

Looks like an Index or Indexer problem. However you should have more files in that folder which could help. Please send them all along: Install, Indexer, crash, etc. - all of them from your latest install and attempt to run Logos.

Wolfe Family

https://community.logos.com/discussion/comment/695190#Comment_695190

6232.LogosError.zip

Sorry i didn't chose the other files because they were created days ago.

NB.Mick

https://community.logos.com/discussion/comment/695189#Comment_695189

The two errors from today are:

Program Version: 6.0b SR-2 (6.0.2.0075)
Time: 2015-02-08 15:00:20 -05:00 (2015-02-08T20:00:20Z)
Can't query HasExited for Indexer process.
System.ComponentModel.Win32Exception (0x80004005): Access is denied
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.get_HasExited()
at LDLS4.Indexer.IndexerProcess.HasIndexerExited()

Program Version: 6.0b SR-2 (6.0.2.0075)
Time: 2015-02-08 15:00:20 -05:00 (2015-02-08T20:00:20Z)
Can't subscribe to Indexer process events.
System.ComponentModel.Win32Exception (0x80004005): Access is denied
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.OpenProcessHandle(Int32 access)
at System.Diagnostics.Process.set_EnableRaisingEvents(Boolean value)
at LDLS4.Indexer.IndexerProcess..ctor(User user, IDigitalLibraryServices services, IEnumerable`1 initialCommands, Boolean bStartIfNotRunning)

Unfortunately I haven't seen such errors before - maybe it refers to a firewall blocking access, but it might as well be a permissions issue on your machine - you might want to check for those things. Sorry that I can't be of more help, maybe others can make something out of this.

Mark Smith

https://community.logos.com/discussion/comment/695192#Comment_695192

My best guess is that you have a corrupted Index and need to rebuild your Library Index. To force Logos to do this since you can't get into the program, you will need to delete the index you already have.

Navigate to \Users\(User Name)\AppData\Local\Logos4\Data\(Random string)\LibraryIndex and delete the contents of that folder. Then attempt to restart Logos 6. If Logos works at this point it you will see the preparing your library notification for some time.

Wolfe Family

https://community.logos.com/discussion/comment/695193#Comment_695193

No firewalls on, windows or otherwise. No other security software. Installed both as an administrator, and regularly. Running as administrator doesnt help either. Are there any folder permissions I should look at?

Wolfe Family

https://community.logos.com/discussion/comment/695199#Comment_695199

Thanks guys, God Bless you. REverting back to 5 for tonight and then going at it another time.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/695188#Comment_695188

The typical cause of this error is running the Indexer as an administrator and running the application normally. For security reasons, Windows will block the application from communicating with the Indexer in this scenario.

We strongly recommend running both programs as a regular user. You can force the indexer to shut down and restart with normal permissions by rebooting the computer.

Wolfe Family

https://community.logos.com/discussion/comment/695247#Comment_695247

I ended up reverting back to 5 last night, so I could finish my lesson. I'm going to try to update the software tonight and create a fresh set of logs. I'm going to try and let the software do the update rather than running the installer package.

Rev. Joe Roof

My LOGOS 6 is doing the same thing. After two phone calls, I was told it was being sent to the developers for their input. I have been unable to use LOGOS since Thursday last week and it is a killer when you have become dependent on this program for preparing Bible studies. Still have not heard anything from the developers.

Graham Criddle

https://community.logos.com/discussion/comment/695714#Comment_695714

Hi Joe

Sorry to hear you are having problems

For us to help here, please start a new thread providing as many details as possible and upload logs after a failed startup attempt

Graham

Bob Bacle

https://community.logos.com/discussion/comment/695717#Comment_695717

I started having the same problem today (July 18, 2016) with Logos 6.

I had this problem before and finally someone at Logos pointed me a .NET Framework file that I needed to install to make it work.
I tried that file today and did a repair, but still having the same problem -
"Logos Bible Software Has Stopped Working."

This is very disconcerting that a program of this caliber would experience these kinds of problems constantly.

JT (alabama24)

https://community.logos.com/discussion/comment/833150#Comment_833150

I started having the same problem today (July 18, 2016) with Logos 6.

I had this problem before and finally someone at Logos pointed me a .NET Framework file that I needed to install to make it work.
I tried that file today and did a repair, but still having the same problem -
"Logos Bible Software Has Stopped Working."

This is very disconcerting that a program of this caliber would experience these kinds of problems constantly.

Please see your other thread.