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
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.
Try that. It still crashes.
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 ~ Does Logos 4 crash right after displaying the layout, as it does for Ka-Liong Lau?
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
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?
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.
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)
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.
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,
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.
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.
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.
I got it, thank you.
I have the file, thank you.
It's on the way. Let me know if you get it OK. I got it, thank you.
If there is any experimenting you, or development, wants me to do to, feel free to let me know.
The crash dump did contain information about the same crash you had reported earlier, but unfortunately not enough for me to see exactly why the problem is happening. I'd like you to try collecting a dump with a different tool (that's a little more complicated to use); the instructions are here: http://wiki.logos.com/Creating_a_Crash_Dump_with_ADPlus
The dump files that ADPlus creates are typically very large, so let us know if it ends up being too big to email.
Thanks,Bradley
The crash dump did contain information about the same crash you had reported earlier, but unfortunately not enough for me to see exactly why the problem is happening. I'd like you to try collecting a dump with a different tool (that's a little more complicated to use); the instructions are here: http://wiki.logos.com/Creating_a_Crash_Dump_with_ADPlus The dump files that ADPlus creates are typically very large, so let us know if it ends up being too big to email. Thanks,Bradley
I will get it out around 3:00 PM PDT
Logos 4.0d beta 1 crashes a lot for me as well. I attached the logs for a recent crash. I just opened the program and enlarged it to full screen, then it crashed. Sometimes it crashed when I just start the program.
4846.Logos Log Files4.zip
I moved a few books to the Prioritize list, then I shut Logos down. Now I cannot start it at all. As soon as it starts to draw the program screen, it crashes. I am stuck and cannot run the program.What can I do?
4834.Logos Log Files5.zip
You're getting the same error as others in this thread. It may be that the crash dump files provided to development team by the other users will give them all the information they need to troubleshoot the crash. However, if you want to create a crash dump from your system, you can 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.
7242.ADPlus_log_14ec_2010-05-27_16-22-53-203.log
Bradley,
Please check my log file generated from ADPlus after Logos4.0d Beta1 crashed. If you need the dump file, I can send it to you separately. It is quite large ~598M. Hope this help.
I put the log in the bug case. Thanks.
Hi Bradley,
I tried to collect the dump, but ran into two problems.
It looks like Microsoft has released a new version of the Debugging Tools for Windows since I wrote that wiki page (and made it harder to install). I'm sorry if you went to all the trouble of downloading the WDK, mounting/burning the ISO, etc.
I haven't ever used that specific version, so it may be causing the problem. Please uninstall it, and install the old version 6.11.1.404 from the version-specific link:
Previous Release version 6.11.1.404 - March 27, 2009Install 32-bit version 6.11.1.404 [16.9 MB]
Let me know if you still have problems with the older version of the Debugging Tools.
Hi Bradley, I tried to collect the dump, but ran into two problems. First was that there is no VBS script named "ADPlus.vbs", but there is one named "ADPlus_old.vbs" Second, if I rename ADPlus_old.vbs to ADPlus.vbs and run your command line, I am getting a requirement request form the debugger asking for an environment variable named "_NT_SYMBOL_PATH", that would point to a path with the proper symbols.
Hi Paul,
To run the new version ADPlus.exe under command prompt:
1. add the debugger installation directory PATH=%PATH%;C:\WinDDK\7600.16385.1\Debuggers.
2. go to the Logos4 directory (%LOCALAPPDATA%\Logos4\System\) and run the command "adplus.exe -crash -o c:\temp -NoDumpOnFirst -MiniOnSecond -pmn Logos4.exe"
%LOCALAPPDATA%\Logos4\System\
3. run Logos4.exe. This will create a sub-directory under c:\temp\20100527_######_Crash_Mode which contains log files and dump file.
It looks like Microsoft has released a new version of the Debugging Tools for Windows since I wrote that wiki page (and made it harder to install). I'm sorry if you went to all the trouble of downloading the WDK, mounting/burning the ISO, etc. I haven't ever used that specific version, so it may be causing the problem. Please uninstall it, and install the old version 6.11.1.404 from the version-specific link: Previous Release version 6.11.1.404 - March 27, 2009Install 32-bit version 6.11.1.404 [16.9 MB] Let me know if you still have problems with the older version of the Debugging Tools.
No problem, worked fine got the dump. It's too big to email though (131mb zipped). So if you want to email/call with a link to upload it to, or an invite for you take over my machine, an grab it, either would be fine.
Paul
Hi Paul, To run the new version ADPlus.exe under command prompt:...
To run the new version ADPlus.exe under command prompt:...
Thanks for the info, but I was able to get it with the older version. [:)]
Please use http://www.transferbigfiles.com/ to send it to my email (bgrainger at Logos).
If you have a fast upload speed, you can send it to my email (bgrainger at Logos) using http://www.transferbigfiles.com/. However, if it's not feasible to upload that file on your Internet connection, that's OK; Paul also has a crash dump and his may have enough information for us to figure out the problem.
Sent.
File name: Crash_Mode__Date_05-27-2010__Time_18-49-23PM.zip
If you have a fast upload speed, ...
I uploaded my crash dump in case you need it.
FULLDUMP_FirstChance_epr_Process_Shut_Down_Logos4.exe__14ec_2010-05-27_16-24-17-121_0528.dmp.zip
I have received both these files--thanks. I'll let you know what I find.
The problem is in code I added for 4.0d to try to solve a persistent bug we had with our SQLite databases in 4.0c and earlier. However, this change seems to have made things much worse. [:(]
I have an experimental patch I'd like you to try to see if it helps stop the crashing.
Please download and unzip the attached file to your %LOCALAPPDATA%\Logos4\System folder (overwriting the existing DLL file that's there), and let me know if this improves the stability of Logos 4. (If it does still crash, please upload the Logos4Crash.txt file so I can see if it's the same crash still, or a different one.)
worked for me [:)] thanks Bradley! ur the man!
The problem is in code I added for 4.0d to try to solve a persistent bug we had with our SQLite databases ...
After replacing the DLL, the problem is fixed. Thank you.
We will incorporate this fix into 4.0d Beta 2 (so the patch DLL will not be necessary once that ships).
Works like a charm.
Let's see what I can break now...[:)]
Thanks. This fixed a crash that happened every time I opened the Passage Guide.
