Bible Search

Okay. I have obviously got some setting wrong somewhere.

In Bible search, the only results I get returned are in the NIV. No ESV. No NET. No other Bible version returns hits from a search query except the NIV. When I highlight a word in the ESV and do a Bible Word Study, down at the bottom it says there are 26 hits for "anxious" in the ESV. But when I click on it it returns "0" hits.

I have the ESV listed as my top priority resource followed by The Message, NET, HSCB and the LEB. I get "0" hits returned for all 5 Bibles. I don't even have the NIV anywhere in my prioritized list.

I keep everything up to date. I'm using L4.2 SR-2.

I'm just learning how to use Logos. I'm not really a L3 user at all. Seems to me something isn't right.

Andrew Smith

Find more posts tagged with

Comments

steve clark

Welcome to the Forum Andrew!

Something is definitely wrong. i noticed that in your 1st screenshot that anxious is highlighted for other words found (in your ESV). But the search shows nothing as you mention. The highlighting in the ESV indicates that Logos4 has found other occurrences of the word.

Is your Logos4 indexing?

If not did you see an error message the last time you Indexed?

Someone more knowledgeable than i will probably chime in here later.

EDIT: you may want to turn logging on (see this wiki Diagnostic Logging). And then run Logos4 and repeat your search. Then upload your log files (see this wiki page Uploading Logs). Some of the MVP's will ask you to do this, which helps them identify your problem.

Rosie Perera

https://community.logos.com/discussion/comment/223736#Comment_223736

Is your Logos4 indexing?

Yes, it sounds like a classic "Logos is still indexing" problem. Do you see a blue Logos icon in your icon notification area? Hover over it and it will tell you if Indexing is still going on and what percent complete it is. Search results will be unpredictable until Indexing is finished.

Andrew Smith

https://community.logos.com/discussion/comment/223738#Comment_223738

So I found the command to force a reindex, "rebuild index". I'm doing that now. Sorry for posting this. This morning I did finally find another post in the forum about this same problem but didn't last night when I was so frustrated.

Thanks for the suggestion. I'll repost with the results of the rebuilt index.

Andrew Smith

https://community.logos.com/discussion/comment/223864#Comment_223864

I'm sorry. I didn't answer Rosie's question. No, actually; it wasn't still indexing. That's the thing that had me really stumped. We'll see if the "re" index fixes my problem.

Thanks again for the replies.

Andrew Smith

https://community.logos.com/discussion/comment/223736#Comment_223736

I did the index rebuild. I'm having the same problem.

Attached is my log file.

03548.Logos4.log

Rich DeRuiter

https://community.logos.com/discussion/comment/224346#Comment_224346

I did the index rebuild. I'm having the same problem.

Attached is my log file.

03548.Logos4.log

Would you also upload the indexer log. This log is showing a lot of resources not showing up in the catalog. This could be the result of an incomplete indexing process (the indexer log will tell).

Did you ever uninstall and then reinstall Logos4? If so, what the Log shows could be remnants of an incomplete uninstallation. Not that I know for sure but lines like this one:

Warn LibraryCatalog No metadata found for resource '{06A55AD5-64B7-4969-B121-992499EB186A}'.

suggest a registry issue, which could be related to an incomplete uninstallation.

Mark Barnes

https://community.logos.com/discussion/comment/224355#Comment_224355

Warn LibraryCatalog No metadata found for resource '{06A55AD5-64B7-4969-B121-992499EB186A}'.

Actually, that's not related to the registry. Several Logos resources have strange IDs like this. Usually it's the timelines or LiteraryTyping resources.

Mark Barnes

I'm just learning how to use Logos. I'm not really a L3 user at all. Seems to me something isn't right.

You correct - something isn't right, and whatever it is isn't your fault. I'm struggling to work out the problem. It's likely to be (a) metadata updates not being applied properly; (b) indexing not being completed, or (c) both.

One user with similar lines in his log found his problem went away after a while (http://community.logos.com/forums/p/9130/72492.aspx). Perhaps it might worth leaving the machine overnight, then restarting Logos in the morning. If that doesn't work (and I'm not holding my breath), could you post any indexing logs you might have?

Andrew Smith

https://community.logos.com/discussion/comment/224390#Comment_224390

So I just completed another index with the "rebuild index" logging. Attached is the log index file.

Thanks again.

8737.Logos4Indexer.log

Mark Smith

https://community.logos.com/discussion/comment/224496#Comment_224496

So I just completed another index with the "rebuild index" logging. Attached is the log index file.

It looks like a successful attempt. Try your search again.

Andrew Smith

https://community.logos.com/discussion/comment/224497#Comment_224497

Yeah. Now it returns "0" hits even faster.

No I am not still indexing. No I did not reinstall on this computer. Brand new laptop last month, fresh install.

I'm thinking a reinstall? And before that use a registry cleaner?

Mark Barnes

https://community.logos.com/discussion/comment/224510#Comment_224510

Before you try a complete reinstall, I'd just rebuild your library catalog. There's some suggestion it might be a problem with metadata rather than anything else, and rebuilding your library catalog will do that. If you delete the following files:

LibraryCatalog\catalog.db
Updates\Metadata.db

Both are in C:\Users\Andy\AppData\Local\Logos4\Data\imnr2cz3.tpm\

If that doesn't work a reinstall might be the only option, but make a back up of your resources first, to save re-downloading them all. I'd also install version 4.2a (which is just coming out of beta), rather than 4.2 (as you'll need to install 4.2a in a couple of weeks anyway). I can provide more information about any of this if you want it. Just ask.

Dave Hooton

https://community.logos.com/discussion/comment/224544#Comment_224544

Before you try a complete reinstall, I'd just rebuild your library catalog. There's some suggestion it might be a problem with metadata rather than anything else

Quite possibly. Only 3 bibles are recognised for the Bible Index (LLS:1.0.301, NIV2011, SBLGNT) which explains (?) why a Bible Search on ESV shows 0 results!

After rebuilding the catalog Andrew should use the command rebuild bible index if it doesn't start indexing automatically.

Note that other bibles are indexed for the Library Index but they are not recognised as such for the Bible Index.

EDIT: it would be interesting to see what type:bible returns in the Library Find box ie. greater than 3 bibles?

Andrew Smith

https://community.logos.com/discussion/comment/224874#Comment_224874

That might very well have worked. But today was the day I needed to get things right and so today, I reinstalled Logos from scratch. Yes, all 6.17 gigs. And guess what? It works as advertised. I'm glad to be through with that.

Thanks to all who contributed to this problem. I'm sure others will benefit from your thoughts and postings here. I really appreciate the support getting me through a frustrating time.

Andrew Smith

https://community.logos.com/discussion/comment/224878#Comment_224878

One more thought. I know this sounds kind of old school, but a "Troubleshooting Guide" might have been helpful from the get go. I didn't even know I could rebuild index. Rebuild Bible Index. Rebuilt Catalog. Those kinds of things would have been helpful. As slick as Logos4 is, and it truly is amazing, the lack of documentation / help files is in adequate. The forum is great, if one has the time to sort through and search. But syntax being what it is, few folks word the same problems the same way. My two cents.

Thanks again to all the great forum folks. You folks are really supportive.

Rosie Perera

https://community.logos.com/discussion/comment/224879#Comment_224879

I know this sounds kind of old school, but a "Troubleshooting Guide" might have been helpful from the get go.

While there isn't an official Troubleshooting Guide, and you're right that it's something there really ought to be, the next best thing is what we users have generated on the wiki, which is a work in progress and I see not very well organized yet for people to find what they're looking for on the Windows side:

http://wiki.logos.com/Mac_Troubleshooting

http://wiki.logos.com/FAQ

http://wiki.logos.com/Installation_and_Indexing_FAQ's

It makes me realize that we need a more complete and separate Windows Troubleshooting page on the wiki. Anyone? Anyone? Want to work on it together with me? I think it needs to be a collaborative effort. Most times that I've started a page on the wiki in the past I've gotten too busy with other things and have left it unfinished, so there are bunch of those false starts of mine all over the wiki. Steve Clark does a better job of following through and finishing what he starts.

Mark Barnes

https://community.logos.com/discussion/comment/224881#Comment_224881

I like the idea of a troubleshooting guide. It could save time. I wonder if perhaps steve clark and some of the MVPs might put their heads together on another thread?

Dave Hooton

https://community.logos.com/discussion/comment/224881#Comment_224881

It makes me realize that we need a more complete and separate Windows Troubleshooting page on the wiki. Anyone?

I think Logos should contribute significantly to this. They have discouraged deleting databases, manipulating data values etc - and generally designed L4 as a Black Box! Further, this issue with metadata (as it appears to be) should raise some Corrective Action with the Developers - it should not have arisen. And there are also other spurious values in the databases that give rise to metadata warnings for resources we do not own ( the notorious LLS:APFTHLKENG in my case)!

The bottom line for any Trouble Guide at the moment would have to be the old favourite - re-install the application. Without developer assistance this was almost inevitable in this case.

steve clark

https://community.logos.com/discussion/comment/224914#Comment_224914

I like the idea of a troubleshooting guide. It could save time. I wonder if perhaps steve clark and some of the MVPs might put their heads together on another thread?

Started a thread: http://community.logos.com/forums/p/30395/224967.aspx#224967

Dave, Mark, Rosie, please present your thoughts.

Rosie Perera

https://community.logos.com/discussion/comment/224916#Comment_224916

They have discouraged deleting databases

Not all of them discourage deleting databases. Melissa encourages it from time to time: http://community.logos.com/forums/p/29687/219789.aspx#219789, even though she recognizes that it's not ideal.