Logos 4 Crashes on Startup
Here we go again. Logos4 has been working beautifully up until this morning. As a matter of fact, it was working last night when I left the office and now, this morning it crashes. This just started to be honest, it is getting a little annoying. I use this program alot and to not have it available when I need it - very inconsistently, it is frustrating - especially after spending so much $ on it and it doesn't function.
Here are ALL the logs in the log file that were posted during the most recent crash a few minutes ago:
Comments
-
The problem is caused by one of the resources open in your most recent layout (but I'm not exactly sure why, yet).
You can work around it by holding down CTRL as you launch Logos 4. When the Sign In dialog appears, check the "Use blank layout" checkbox, then click Sign In.
Logos 4 will open to a blank screen; you will then have to reopen the panels you were using one-by-one. (Loading the last layout will most likely crash the app.)
0 -
Rev. Mark C Spellman said:
Here we go again.
Sorry this is happening again, Mark. This does appear to be a different issue.
Does Logos crash on open, or when you try to do a search, when you click on a link, or when you open a certain resource?
What the logs show for the cause is consistent: "The string 'bible+bhs.26.14.0' has an invalid numeric verse."
Determining how Logos is getting the string is key to figuring out it's cause and solution.
What it looks like (to me at least - not an expert on reading these logs) is that this is happening on open, as Logos is loading a previous layout. If that's the case, the solution is simply to boot to a blank layout (hold down CLTR as Logos is booting up - ask Logos to load to blank layout). Given the error in your log, this should work. Then you would need to rebuild your layout -- you could try reloading it, but that would likely cause the same crash.
Every once in a while, for some folks more than others it seems, the layout database in Logos gets a bit of bad data. In another thread Bradley suggested the problem lies with SQLite, which should be stable, but has shown issues with other Logos databases as well.
EDIT: I see Bradley posted while I was composing. At least we agree about the fix.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I'll give these solutions a try. I was using Logos4 successfully yesterday, all day, and when I came into the office this a.m. and tried to pick up where I had left off last night (I didn't close anything last night, but left everything open), it stopped working. When I tried to reopen it, I get the error message box saying Logos4 had quit working and windows was trying to find a solution.
I've disable 'webroot' and tried to start up that way too, but nothing.
I'll try the 'ctrl' solution and see what happens.
Thanks for your help!
Mark
0 -
OK - just tried the startup using 'ctrl' with blank layout, but as soon as I type in a bible reference to search or read, the program crashes again - won't start. [:(]
0 -
Rev. Mark C Spellman said:
OK - just tried the startup using 'ctrl' with blank layout, but as soon as I type in a bible reference to search or read, the program crashes again - won't start.
In that case, it's possible your Bible index is corrupt.
Try this: open to a blank layout as before, but don't open anything. Instead type rebuild Bible index in the command box and let it finish.
After you're sure that Logos is finished rebuilding the Bible index, try to do what made it crash before. If it crashes again, please post all your logs (as before), so we can look under the hood.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Ok - got that going. Once indexing is complete, will post again the results.
Thanks Richard!
0 -
Indexing complete. Crashes continue same as before.
0 -
Rev. Mark C Spellman said:
Indexing complete. Crashes continue same as before.
Okay, attempt to fix #3.
This still looks like it's happening when loading a workspace, though I can't be sure. And the error is exactly the same as before.
The next likely culprit is a bad resource. This would be your BHS (Hebrew Bible). The simplest way to fix that issue would be to hide the resource (from the Settings menu), restart Logos, and then unhide it. This will first remove it from your directory and then download the file again.
To keep Logos from crashing on startup, load to a blank layout as before and only do this task, before shutting down, restarting and letting Logos download the resource. Let it finish downloading and indexing before trying anything (just to be safe), and then try what you did before.
If this doesn't work, Bradley will be your best bet in getting this fixed.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
The program is having trouble with BibleDataTypes, specifically with the Bible+BHS datatype. I don't there is anything we know how to do to fix that. Rich's suggestion may work but I won't be surprised if it doesn't. Worth a try. If it doesn't work, and Bradley doesn't look in, give Logos a call. They are still open (until 5 PM Pacific.)
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Now it will open, but if I try to go to a bible passage and type it into the box on the home page "go to topic or passage" it crashes again. Can't get anywhere! The logs below are the ONLY logs that were updated with the most recent crash.
0 -
How do I get in touch with Bradley?
0 -
Bradley - tried this and everything else in this thread and still not working. Any suggestions? I've called Logos support, but couldn't get through after waiting 30 minutes decided to try this forum again.
0 -
I have a theory that this might be caused by bad data synced up from your mobile device (based on the fact that you've posted in the iPad forum). Try opening the ESV on your iPhone and change to a different verse, then do the same for the BHS (which may be the affected resource).
Wait a few minutes for it to upload your "last read" position, then restart Logos 4, using CTRL to open to a blank layout again. Click the sync arrows to force a sync, then try reopening your Bible.
0 -
Actually, I think it's caused by a Favorite (which may have been added on the iPhone? If so, please let us know).
Try deleting the "BHS" Ezek 14 Favorite on your iPhone (and waiting for it to sync).
0 -
Don't have an Iphone, but do have an Ipad2.
0 -
I give up! I deleted the program from my computer and am now reinstalling. Will take a while, so will see you guys tomorrow morning. Let's see if all this can replicate itself with a new build. Thanks for your help!
Mark
0 -
The corrupt data will be re-downloaded from the sync server and will crash your program as soon as you launch it tomorrow.
To fix it, open to a blank layout, then open the Favorites panel and delete the BHS Ezek 14 favorite.
0 -
Rev. Mark C Spellman said:
Don't have an Iphone, but do have an Ipad2.
When I said "iPhone", I meant any Apple (iOS) mobile device. Did you try deleting the favorite from your iPad2?
0 -
yes removed all bookmarks and my installation on my home computer seems to be working now will try the office tomorrow when i get there in the morningm also wondering if the conflict might be another resource i had recently started using a greek interlinear and had that marked as a favorite none of this was a problem until i added that greek resource the bhs was working fine
0 -
Rev. Mark C Spellman said:
yes removed all bookmarks and my installation on my home computer seems to be working now will try the office tomorrow when i get there in the morningm also wondering if the conflict might be another resource i had recently started using a greek interlinear and had that marked as a favorite none of this was a problem until i added that greek resource the bhs was working fine
The problem appeared to be related to a bookmark (I said "favorite" but might have misdiagnosed the issue since I was rushing to try to post something before I left work; I apologise for any inaccuracies) in Ezekiel 14, so I don't think it was caused by bookmarking a Greek Interlinear.
If you've deleted the bookmarks at home, they should be deleted on the office computer once you start Logos 4, which should fix the crash.
I apologise for the inconvenience of having Logos 4 not working for the day; we'll be investigating how it's possible to create a bookmark that crashes Logos 4 and will fix the underlying bug and crash.
0 -
OK - I removed the favorites on the IOS device. Reinstalled and resynced the desktop program and it appears that everything is working now. Thanks for all your help with this Bradly and Richard. Sorry it took up so much time.
Hopefully the 'fav' problem will get resolved. Would be interesting to see if I could replicate it, but maybe at a time when I'm not under a crunch!
Thanks again,
Mark
0 -
I too have had Logos4 crash on startup. It was working just fine. I have software that backs up my computer every night. For reasons that shouldn't have anything to do with Logos, I decided to reinstate Friday night's backup. It replaces everything on the hard drive so that I'm supposed to have everything exactly as it was at the time of the backup. Since I use Logos every day it was working fine Friday.After the restore, everything was working fine until I started Logos. It won't get past the splash screen.
Is there a way to reinstall Logos4 without having to download all my resources again? That could take days.
Have a great day,
jmac0 -
Jim said:
Is there a way to reinstall Logos4 without having to download all my resources again? That could take days.
Look here: http://wiki.logos.com/Quick_Installation_onto_multiple_computers
Method 2 or 3 is probably what you will want to do.
BTW, your error logs don't tell us much. If you want to diagnose the issue you'll need to enable diagnostic logging.
Enable logging by carefully following all the instructions in the link below:
http://wiki.logos.com/Diagnostic_LoggingThen run Logos and see if you can repeat the issue that caused the crash. Make sure to post all the log and txt files here for review. Here are the Wiki instructions for how to upload logs.
http://wiki.logos.com/Uploading_LogsHelp links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Jim said:
I too have had Logos4 crash on startup.
The crash is caused by a recent Windows update for Windows XP. This Microsoft article gives the solution: http://support.microsoft.com/kb/2262911
0 -
I tried method 2 and Logos crashed right after the sign-in. This is puzzling since it was working fine Friday.
BTW the first time I ran the installer, it simply said Logos4 was up to date and quit. I deleted the Logos4 executable and it still said it was up to date! So I deleted everything and ran the installer.
Have a great day,
jmac0 -
Bradley Grainger said:
The crash is caused by a recent Windows update for Windows XP. This Microsoft article gives the solution: http://support.microsoft.com/kb/2262911
I don't have the updates this web page refers to. It's possible I caught this some time ago and fixed it.
Have a great day,
jmac0 -
Jim said:
I don't have the updates this web page refers to. It's possible I caught this some time ago and fixed it.
Did you attempt the fix, though? Because the error does not occur in Logos code and I can't find anything other than what Bradley found.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Did you attempt the fix, though?
I applied the fix, rebooted and Logos4 still crashes. It seems to get further though. The crash was during the sign-in. I'm totally puzzled because in the past any time I've restored my system using my backup software to a previous backup, everything worked fine.
Have a great day,
jmac0 -
Jim said:
I applied the fix, rebooted and Logos4 still crashes. It seems to get further though.
Is it the same crash?
Dave
===Windows 11 & Android 13
0 -
I fixed my system. Never did figure out what made Logos crash.
I ended up restoring my entire computer to older and older backups (I have daily backups) until I found one where Logos would not crash and worked from there. The biggest hassle is getting email files reasonable up to date. Thanks everyone for trying to help. I wish I could have figured out what was causing Logos to crash, it would have saved several days worth of work, but I'm back and running ok again.
Have a great day,
jmac0
