EEC: James will not prioritize

This one is new to me and I cannot seem to fix it. When I downloaded the resource, it indexed. I quickly scanned it and saw it mirrored the other EEC volumes I have so I prioritized it with Moo (PNTC) next. I put James 1:1 in the box and clicked Go. In the passage guide only Moo is my highest priority commentary on James that shows up. I clicked more and the EEC volume was no where to be found. So, I rebuilt the index. After many hours I did the same thing and still no EEC volume in the passage guide. So, I am stubborn and rebuilt the index again which took many more hours. Yep, no EEC volume in the passage guide again. Any idea why this may be happening?

Find more posts tagged with

Comments

Rich DeRuiter

This one is new to me and I cannot seem to fix it. When I downloaded the resource, it indexed. I quickly scanned it and saw it mirrored the other EEC volumes I have so I prioritized it with Moo (PNTC) next. I put James 1:1 in the box and clicked Go. In the passage guide only Moo is my highest priority commentary on James that shows up. I clicked more and the EEC volume was no where to be found. So, I rebuilt the index. After many hours I did the same thing and still no EEC volume in the passage guide. So, I am stubborn and rebuilt the index again which took many more hours. Yep, no EEC volume in the passage guide again. Any idea why this may be happening?

Is this a passage guide you made (My Passage Guide)? And if so, do you have this section open to a collection? If so is EEC James in that collection?

Matt Hamrick

https://community.logos.com/discussion/comment/394247#Comment_394247

Is this a passage guide you made (My Passage Guide)? And if so, do you have this section open to a collection? If so is EEC James in that collection?

No, it is the standard passage guide that comes with Logos Bible Software.

Louis St. Hilaire

https://community.logos.com/discussion/comment/394249#Comment_394249

Matthew,

Try restarting Logos and refreshing your guide. We found and corrected an error in the metadata that was likely causing this problem. (Note: there could be a bit of a lag while the application updates its data from our servers.)

Matt Hamrick

https://community.logos.com/discussion/comment/394270#Comment_394270

Matthew,

Try restarting Logos and refreshing your guide. We found and corrected an error in the metadata that was likely causing this problem. (Note: there could be a bit of a lag while the application updates its data from our servers.)

Thank you Louis, but no luck. I have rebooted Logos 4 a couple times since yesterday and even shut it down last night while I slept for about 6 hours and started it back up this morning and it has been on for about 5 hours now. The passage guide will not display the EEC: James Volume. I have removed and changed resources to see if that matters and still nothing for the EEC: James volume in the passage guide.I can only load it by clicking on the resource or I can search the resource. I do not understand why it will not prioritize.

Louis St. Hilaire

https://community.logos.com/discussion/comment/394398#Comment_394398

Does the resource show up when you click the Parallel Resource Sets button in another commentary on James? (I'm trying to ascertain if your system has downloaded the metadata update.)

Also, have you tried deleting rather than just refreshing the guide? Does it fail when you start a guide on a different section or verse in James?

Matt Hamrick

https://community.logos.com/discussion/comment/394488#Comment_394488

Hi Louis,

I just tried the parallel resources and the EEC volume does not show up.

I started a new guide on James 3:10 (just random) and still no EEC.

Matt Hamrick

https://community.logos.com/discussion/comment/394488#Comment_394488

Hi Louis,

First of all, thanks for putting tech support on the case. Second, I did figure it out though before they could contact me. I hid the resource, reloaded Logos and deleted it. Then I unhid the resource, reloaded Logos and reinstalled it. Now it prioritizes like it should. I do not know why I did not think of that before I started this thread. But it is fixed now. Thank you for your assistance.