Windows 8 crash

Page 1 of 1 (15 items)
This post has 14 Replies | 2 Followers

Posts 9
James Bills | Forum Activity | Posted: Mon, Sep 9 2013 5:08 AM

When on the home page, I put a topic in the "enter passage or topic" search window, it crashes when I search a topic such as "Hope," Love," "truth," etc etc. 27704.Logos Log Files.zip

Posts 23209
Forum MVP
Graham Criddle | Forum Activity | Replied: Mon, Sep 9 2013 5:48 AM

Hi James - and welcome to the forums.

It looks as though this may be trying to open the "HarperCollins Bible Dictionary (Revised and Updated)" resource in responding to your topic request (or I could be totally misreading what the logs are saying!)

To verify this could you try searching for the topic "Lovesick" which isn't included in that resource and so it won't be included in the results?

Graham 

Posts 8688
LogosEmployee

This crash occurs when running the Sermon Starter Guide, but I'm not able to reproduce it. Can you give some more diagnostic information about your system? On the Help menu (far right), choose "About Logos Bible Software". In the pane on the left, scroll down to "Sermon Starter Guide". The top entry in that section should be:

DB:PREACHINGTHEMES
2013-05-06T19:37:58Z
PreachingThemes.lbsptd

If the date given for "DB:PREACHINGTHEMES" is older, then this crash is probably caused by an out-of-date resource. Please enter "update resources" into the Command Box at the top of the main window to force a check for updates.

Posts 9
James Bills | Forum Activity | Replied: Mon, Sep 9 2013 9:09 AM

Hi Graham, Thank you for the welcome

I did as you suggested and it worked. I was able to make a successful search and not crash.

Is there a solution?

James

Posts 9
James Bills | Forum Activity | Replied: Mon, Sep 9 2013 9:11 AM

Hi Bradley,

I looked as you suggested. I found it to be identical to the one you posted.

I have not done anything more since checking it.

Should I do what as you suggested anyway, (Update resources)?

James

Posts 9
James Bills | Forum Activity | Replied: Mon, Sep 9 2013 9:31 AM

Here is the latest. It works if I type in lovesick in the topic/passage search bar. If I put in "hope" "love" or anything else, it crashes.

here is the report1526.LogosCrash.txt

Posts 23209
Forum MVP
Graham Criddle | Forum Activity | Replied: Mon, Sep 9 2013 9:55 AM

James Bills:
Here is the latest. It works if I type in lovesick in the topic/passage search bar. If I put in "hope" "love" or anything else, it crashes.

So it looks as though my hunch might have something going for it!

Is the "HarperCollins Bible Dictionary (Revised and Updated)" resource one of your highest prioritised encyclopedia? Can you prioritise five dictionaries above it? Just trying to remove it from the equation.

For details of prioritising please see http://wiki.logos.com/Prioritizing

Posts 8688
LogosEmployee

What are your highest prioritised Bibles?

Posts 9
James Bills | Forum Activity | Replied: Mon, Sep 9 2013 10:26 AM

I realized as I was looking at my priority list looking for the Harper Collins Dictionary, that I had the SBLGNT Greek New Testament as my number one resource. I switched it back to the ESV and tested the topic/passage search and it worked. As I was studying the GNT I prioritized the SBLGNT and didn't realize that it would effect my search. Thank you gentlemen for your time and support. Now I can get back to writing my sermon for this week. May God bless you both.

James Bills

Posts 25861
Forum MVP
Dave Hooton | Forum Activity | Replied: Tue, Sep 10 2013 12:08 AM

Bradley, what is happening here? 

I prioritised SBLGNT above ESV as #1 Bible (and first in the list) and the Topic Search still worked with HarperCollins as my #1 encyclopedia, but I wouldn't expect a Bible datatype to affect a Headword datatype.

Dave
===

Windows 10 & Android 8

Posts 8688
LogosEmployee
Bradley Grainger (Faithlife) | Forum Activity | Replied: Tue, Sep 10 2013 12:17 AM

Dave Hooton:

Bradley, what is happening here? 

No idea, sorry; the provided steps aren't sufficient to repro on my system.

Posts 9
James Bills | Forum Activity | Replied: Tue, Sep 10 2013 4:27 AM

I tried to redup. the problem and I could not get the problem to occur again. Very strange. Once I placed the ESV at the top of my priority list, replacing the SBLGNT as #1 it worked. I switched them back to test the problem and it still works. I guess there was just a glitch. However, I did receive two updates between tries. I received one yesterday and one this morning when I logged onto my computer. The one I received yesterday, I received it after I prioritized my library. I tried to reduplicate the scenario this morning and could not. I guess it was a true glitch. But I am up and running and that is something to be thankful for. 

Blessings

James 

Posts 25861
Forum MVP
Dave Hooton | Forum Activity | Replied: Tue, Sep 10 2013 4:54 PM

James Bills:
I did receive two updates between tries

There was a similar case affecting Bible Facts where the first update failed and the second replaced the errant resource affecting the Tool!

Dave
===

Windows 10 & Android 8

Posts 13399
Mark Barnes | Forum Activity | Replied: Tue, Oct 15 2013 7:18 AM

Bradley Grainger (Logos):
No idea, sorry; the provided steps aren't sufficient to repro on my system.

Bradley: Another user has reported the same crash: http://community.logos.com/forums/t/76405.aspx 

<edit>On that thread, it appears to be confirmed that the crash occurs when verses from the Passages section of the SSG cannot be found in your most highly prioritised Bible (either because the verses don't exist, or because advanced prioritization prevents it).

To reproduce, you'll need to prioritise a Bible that doesn't cover the whole canon (or use advanced prioritisation to restrict it), and run an SSG for a topic that includes passages outside that Bible.</edit>

Posts 1471
Angela Murashov | Forum Activity | Replied: Tue, Oct 22 2013 3:05 PM

James Bills:
When on the home page, I put a topic in the "enter passage or topic" search window, it crashes when I search a topic such as "Hope," Love," "truth," etc etc.

This crash will be fixed in 5.2 Beta 2.

Page 1 of 1 (15 items) | RSS