2605.Logos4.log
3554.Logos4Crash.txt
Hi,
After upgrading from 4.0c SR1 to 4.0d Beta 1, Logos starts to crash right after displaying the layout. The crash logs are attached. Please help.
Try http://wiki.logos.com/Logos_Not_Starting
Crash here too.
7711.Logos Log Files.zip
"As any translator will attest, a literal translation is no translation at all."
Paul Golder: Crash here too. 7711.Logos Log Files.zip
Yea, it seems to not want to open at all. Goes to "Logos indexer has stopped working" within a few seconds.
We'll take a look at your logs.
Mark Barnes: Try http://wiki.logos.com/Logos_Not_Starting
Try that. It still crashes.
Ka-LiongLau: Mark Barnes: Try http://wiki.logos.com/Logos_Not_Starting Try that. It still crashes.
Ditto
I also notice that if I keep on trying to start logos 4 after it crashed, it will eventually start successfully. So far I have two successful starts out of 10-20 crashes.
Paul Golder:Crash here too.
Paul ~ Does Logos 4 crash right after displaying the layout, as it does for Ka-Liong Lau?
Melissa Snyder: Paul Golder:Crash here too. Paul ~ Does Logos 4 crash right after displaying the layout, as it does for Ka-Liong Lau?
It did one time, but only when I had "open with blank layout" selected. After that is when it started crashing every time, regardless of layout choice.
It all seem to start after I rebuilt the index. ( I did interrupt the initial index with the "rebuild index" command and let it finish completely before starting L4 )
2783.Logos4IndexerCrash.txt
Hey... I also have had this same crashing problem. I start up Logos 4 and it does one of two errors: 1) opens the program (but not the layout) then crashes via a windows error stating it has stopped working. or 2) logos gives an error that the indexer has stopped working.
I tried uninstalling Logos 4 via windows uninstall in control panel and reinstalled it, still receive the same crashes above.
From my error log I have this:
Error ID: 6410Error detail: DatabaseVersionException: The database schema (16) is newer than the latest schema recognized by this code (15). The database cannot be opened.7658.Logos4Crash.txt
Thank You, hope this helps the fix
Chris~
Windows 7 (32 bit) AMD Quad-Core
Christopher S Macy:I tried uninstalling Logos 4 via windows uninstall in control panel and reinstalled it, still receive the same crashes above.
The reason you got the 2nd error (Error ID: 6410) was because you had installed 4.0d Beta 1, then reverted back to 4.0c SR-1, so the error is saying that the databases for 4.0d B1 are newer than the 4.0c software engine can support.
Are you able to update to 4.0d Beta 1 again?
no, the software continues to crash, I am unable to do anything from the command line textbox. hmmm, did I just make my problem worse then?
Christopher S Macy: no, the software continues to crash, I am unable to do anything from the command line textbox. hmmm, did I just make my problem worse then?
You may want to make sure all your user documents, etc. are synched to the server, then uninstall and reinstall the software (edit--4.0d B1). This would require deleting the Logos 4 folder after uninstall. You could backup the Logos 4 Resources folder to avoid having to download your books again, but I recommend allowing it to reindex; in other words, don't back up your index files.
Christopher S Macy: hmmm, did I just make my problem worse
Love your avatar ... I often refer to you (okay I have my Bill the Cat days - nothing personal)
Orthodox Bishop Hilarion Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."
I am not seeing this same crashing on any of my layouts. I thought originally because I was offnet, but no issue on-net either.
In Christ,
Ken
Dell Studio 1555; 15.6 True Life LCD; Intel Core 2 Duo T6600 2.20 GHz, 2M Cache, 800 MHz FSB ; 500GB 5400 HDD; 8GB RAM, Win 10, Chrome 70
http://wiki.logos.com/
Ka-LiongLau: I also notice that if I keep on trying to start logos 4 after it crashed, it will eventually start successfully. So far I have two successful starts out of 10-20 crashes.
Ka-Liong Lau,
Development is asking if you will collect a crash dump to help them troubleshoot this crash. Please follow the first set of instructions here: http://wiki.logos.com/Creating_a_Crash_Dump_with_ProcDump. The crash dump files can be very large, even when zipped. If the zipped file is not too large to email, you can email it to logos4feedback@logos.com. If it's too large to email, please let me know, and I will ask a support technician to contact you to do a file transfer.
Thank you.
Paul Golder:Yea, it seems to not want to open at all. Goes to "Logos indexer has stopped working" within a few seconds.
Paul,
Development is asking if you will collect a crash dump to help them troubleshoot this crash. Please follow the"Collecting Diagnostics for the Indexer" instructions here: http://wiki.logos.com/Creating_a_Crash_Dump_with_ProcDump. The crash dump files can be very large, even when zipped. If the zipped file is not too large to email, you can email it to logos4feedback@logos.com. If it's too large to email, please let me know, and I will ask a support technician to contact you to do a file transfer.
Melissa Snyder: Paul, Development is asking if you will collect a crash dump to help them troubleshoot this crash
Development is asking if you will collect a crash dump to help them troubleshoot this crash
It's on the way. Let me know if you get it OK.
Melissa Snyder: Ka-Liong Lau, Development is asking if you will collect a crash dump to help them troubleshoot this crash. Please follow the first set of instructions here: http://wiki.logos.com/Creating_a_Crash_Dump_with_ProcDump. The crash dump files can be very large, even when zipped. If the zipped file is not too large to email, you can email it to logos4feedback@logos.com. If it's too large to email, please let me know, and I will ask a support technician to contact you to do a file transfer. Thank you.
Hi Melissa,
The crash dump is sent.