UNBELIEVABLE! The Bible Search Doesn't Work After the Update!

I know you are upset, but you haven't really explained the problem. Can you try again? Please explain the issue clearly, and provide specific examples. Screen shots are good, please use .jpg or .png

https://community.logos.com/discussion/comment/528927#Comment_528927

The problem is that SEARCH does not work. How much clearer do I have to be? No matter what I search for - and no matter HOW I search for it, there are NO results - NULL SET. You better believe I am upset.

https://community.logos.com/discussion/comment/528928#Comment_528928

I have deleted all custom search ranges.

I have rebuilt the Index. Short of uninstalling Logos COMPLETELY and going through the whole install process again, I have done everything in my power to restore the capability.

Lee

https://community.logos.com/discussion/comment/528928#Comment_528928

Hello I checked your the bible search also, I am on windows though. I also used the ESV in the search but I had no problems doing search.

I could not read the word you are searching for on the screenshot.

I also have 5.1b updated.

I am sorry for the problem you are having and that I could not help more.

https://community.logos.com/discussion/comment/528928#Comment_528928

The problem is that SEARCH does not work. How much clearer do I have to be? No matter what I search for - and no matter HOW I search for it, there are NO results - NULL SET.

We are not sitting down beside you. We have no idea what you are seeing and doing unless you explain it clearly. For example, if you were to search using "match all word forms," you would get a different set of results. From your logs, I see that you have "match all word forms" off, and "match case" turned on.

This is a FRESH install of Logos 5 on my Macbook.

Has it had time to fully index? Search results won't work properly until it finishes indexing.

You better believe I am upset.

If you want volunteers like myself to help, please STOP YELLING AT US. [;)]

If the issue wasn't an indexing one, I would give Logos a call.

Ray from Faithlife

https://community.logos.com/discussion/comment/528928#Comment_528928

The problem is that SEARCH does not work. How much clearer do I have to be? No matter what I search for - and no matter HOW I search for it, there are NO results - NULL SET. You better believe I am upset.

Hi Erik, I'm sorry you're having trouble. As Alabama said, most of the forum users here are volunteers. They don't work at Logos like I do. They're just friendly, helpful people who give of their time to help others get the most out of their Bible study.

I've forwarded this thread to our Customer Service team, and someone will reach out to help you troubleshoot very soon.

https://community.logos.com/discussion/comment/528945#Comment_528945

The install was done last week, and the indexing was completed then. You will note from my statement that this particular instance of the search issue did not manifest until it was updated to 5.1b this morning. I did state my problem clearly - SEARCH doesn't work. None of the search functions worked after the upgrade. How much more concise should I be? Translation = the upgrade corrupted my indices, again.

I have used Logos since version 1, and I have put up with the train wreck that has been versions 4 & 5 all along the way. I have been patching, working around, reindexes, manually deleting libraries and doing everything else the Logos people (not the volunteers) have told me to do. I used to be charitable. Now I am getting frustrated with them dropping unfinished products to the consumers.

I am very tired of waiting for Logos to release fixes to their fixes. Rather than dabbling in everything else they can think of, maybe they should make sure their core products works consistently. Unfortunately, I cannot afford to spend thousands to get the comparable resources in Accordance or I would have jumped ship long ago.

https://community.logos.com/discussion/comment/528942#Comment_528942

Lee, I was doing a search for the word Aaron; but I tried several different, common words in all kinds of different searches. I got nothing.

It would not be so annoying if this wasn't the third time it has happened on a upgrade. The last time it happened, it was because they had not taken custom search ranges created on mobile apps into consideration and it broke the whole search system - on a Friday, so all of us who needed Logos to prepare messages for Sunday were left hanging until the fix to the fix the following Monday.

This is a constant issue with Logos 5 on Mac. I have been dealing with issues since they dropped the Alpha of Logos 4 Mac on us back in 2009. One would hope the upgrade process would be right by now.

RyanB

https://community.logos.com/discussion/comment/528945#Comment_528945

It has nothing to do with Erik's problem, but I just wanted to make sure that the volunteers such as Alabama24, and the countless others on these forums, know that I truly, truly appreciate them. In my opinion you are invaluable and irreplaceable. What great service you provide, in your own spare time, to share your knowledge and understanding of the tech world so that pastors, missionaries, bible study leaders, Sunday school teachers, and countless others can serve the Kingdom better.

I just wanted to say Thank you and tell you that you are appreciated.

https://community.logos.com/discussion/comment/529012#Comment_529012

I resolved the problem by - once again - manually deleting the indices from the hidden Library folder and then having Logos reindex.

Of course, that also meant I got to spend the whole day trying to work without the single most important tool on my computer. But hey, we've all got four hours to wait for the index to rebuild before you can do searches in our libraries, right?

Todd Phillips

https://community.logos.com/discussion/comment/529023#Comment_529023

I resolved the problem by - once again - manually deleting the indices from the hidden Library folder and then having Logos reindex.

Of course, that also meant I got to spend the whole day trying to work without the single most important tool on my computer. But hey, we've all got four hours to wait for the index to rebuild before you can do searches in our libraries, right?

There is a "disk I/O error" in your log files. I would check to make sure your hard disk isn't failing. Can you run some kind of low level check on it and check for bad sectors? (I'm not a Mac user, so I can't suggest one). If the HD was the culprit, it would also show up repeatedly and after a fresh install.

https://community.logos.com/discussion/comment/529029#Comment_529029

It is a brand new SSD hard drive. I ran an error check just to be sure. There's no problems with the drive, which means that if there is an error - it is Logos' code base.

https://community.logos.com/discussion/comment/529033#Comment_529033

It is a brand new hard drive. I ran an error check just to be sure. There's no problems with the drive, which means that if there is an error - it is Logos' code base.

It doesn't mean that at all. It could be a problem with the "code base," but if it were "only the code base", you would expect that every user would be having the same exact problem. I haven't ever had this problem... which is why Logos and other forum members need info to help you diagnose the problem.

When someone is reading in the forums that "searches don't work," we have no idea how to assess that claim. I come across regularly forum users who are complaining about searches "not working" to find out (to name a few):

They are doing a "bible" search instead of "basic"
They don't actually own any/many resources
They haven't allowed Logos to index properly
They have selected "match all word forms"

I am unsure why you are having this issue, but it isn't common for a simple update to wipe out the index. My curiosity is peaked about your new drive... did you have a hardware failure before? What brand of drive do you have? What test did you run to check the drive? [I'm thinking about swapping out an HDD for SSD. Did you do that? If so, how has it gone?]

Beloved Amodeo

https://community.logos.com/discussion/comment/529033#Comment_529033

It is a brand new hard drive. I ran an error check just to be sure. There's no problems with the drive, which means that if there is an error - it is Logos' code base.

Hi Erik,

So sorry you having trouble with functionality. Have you heard from technical support yet? If not my best advice for you is to take initiative to personally contact them now. Call 1-800-875-6467 ask for technical support, you will probably first speak with customer support, be patient and log you problem with them.

Once you have completed this process they will put you in queue with technical support. Have your computer up and running. I do hope your problem is resolved today, however, sometimes complex problems can take longer to solve. Make sure to get your case number if your problem is not resolved today as this will save time when next you call.

Hang on in there; you will get through this. See this as an opportunity to learn something, this will take the sting out of this whole affair.

Peace

https://community.logos.com/discussion/comment/529037#Comment_529037

I fixed the problem by manually deleting the index and rebuilding it. My guess is that something glitched on the upgrade this time. I discussed the problem with some non-Logos software guys and they reviewed things for me.

The previous issues I had were quite different from this one (http://community.logos.com/forums/t/72280.aspx). That issue popped up on all my systems. (At the time, I did not have Logos on this computer because my wife was using it.) If this one comes up on my other Mac, then clearly the issue is not a glitch in the download.

I upgraded to SSD because I couldn't beat the price. I got a 256GB Samsung 840 SSD for $150 on Tigerdirect.com. My Macbook Pro is a 2009 Intel Core 2 Duo (8GB RAM) running Mountain Lion, and the original 160GB 5400RPM HDD was just not enough anymore.

The drive was running fine, and I still have it in my box of computer parts. It will probably go into my 2006 White Macbook to replace the 60GB in there.

Boot time went from 2 minutes to 23 seconds. Response time is absolutely amazing. I despise indexing on Logos (I have a lot of resource), but on the SSD, it cut the usual time from about 14 hours to 3.5. I have a third part TRIM Enabler. It's not required, strictly speaking, but it keeps the drive healthy longer.

https://community.logos.com/discussion/comment/529039#Comment_529039

I upgraded to SSD because I couldn't beat the price. I got a 256GB Samsung 840 SSD for $150 on Tigerdirect.com. My Macbook Pro is a 2009 Intel Core 2 Duo (8GB RAM) running Mountain Lion, and the original 160GB 5400RPM HDD was just not enough anymore.

The drive was running fine, and I still have it in my box of computer parts. It will probably go into my 2006 White Macbook to replace the 60GB in there.

Boot time went from 2 minutes to 23 seconds. Response time is absolutely amazing. I despise indexing on Logos (I have a lot of resource), but on the SSD, it cut the usual time from about 14 hours to 3.5. I have a third part TRIM Enabler. It's not required, strictly speaking, but it keeps the drive healthy longer.

Thanks for that. [:)] I am hoping to upgrade my 3 year old MacBook Pro drive for my birthday in a couple of weeks.

Milford Charles Murray

https://community.logos.com/discussion/comment/529012#Comment_529012

It has nothing to do with Erik's problem, but I just wanted to make sure that the volunteers such as Alabama24, and the countless others on these forums, know that I truly, truly appreciate them. In my opinion you are invaluable and irreplaceable. What great service you provide, in your own spare time, to share your knowledge and understanding of the tech world so that pastors, missionaries, bible study leaders, Sunday school teachers, and countless others can serve the Kingdom better.

I just wanted to say Thank you and tell you that you are appreciated.

Peace, Ryan! I sit here in my study in Eastern Canada, hoping to hear my wife call me soon to her home-made chili supper with just the right amount of cumin in it! And! I'm pleased to notice your post! And Bless You for it!

Alabama has over 13,000 posts trying to give people help and a boost! He's been an MVP a lot longer and stronger than I; and I -- for one -- truly appreciate him ............ so ..........!! Here's a pat on the back to you for giving the volunteers a pat on the back! *smile*

Now, be very careful, Ryan! *smile* You're liable to make yourself a candidate for future MVP status yourself, eh???

OR! Maybe Logos will pursue "Beloved" one of these years ???? *smile*

Psalm 29:11

Dan Francis

https://community.logos.com/discussion/comment/529039#Comment_529039

It might not be a bad idea to run disk utility. Bad permissions or a flaw in the volume bitmap system could cause issues.

-Dan

https://community.logos.com/discussion/comment/529047#Comment_529047

I worked at Apple Support for years, please do verify the disk in disk utility and run a repair. Third Party drives often give problems.

https://community.logos.com/discussion/comment/529272#Comment_529272

I ran disk utility when I encountered the problem. The disk checks out fine.

https://community.logos.com/discussion/comment/529322#Comment_529322

I ran disk utility when I encountered the problem. The disk checks out fine.

Also run a repair permissions. Permissions often get out of whack and need to be realigned to keep everything working properly.

https://community.logos.com/discussion/comment/529426#Comment_529426

I did run a permissions repair through Disk Utility. The only permission that were unaligned were in iTunes.

Like I said. This is a brand new SSD, properly installed in my MacBook Pro.

https://community.logos.com/discussion/comment/529640#Comment_529640

I did run a permissions repair through Disk Utility. The only permission that were unaligned were in iTunes.

Like I said. This is a brand new SSD, properly installed in my MacBook Pro.

Hmm, not sure what to tell you there without seeing the machine. Doesn't seem to be Logos though as it seems to be an isolated instance of the issue.

Lee

https://community.logos.com/discussion/comment/529640#Comment_529640

@Erik:

An experience I had three months ago.

Brand new SSD. Installed OS and everything, then strange glitches occurred. I almost returned the SSD!

Then I checked the support webpage. Lo and behold, a firmware update, barely two weeks old, that assured stability.

You can guess the rest. Updated firmware (which flushed out all the data) and reinstalled. It was smooth after that.

That may not be the situation in your case, but it remains a possibility.

https://community.logos.com/discussion/comment/529649#Comment_529649

Thanks for the info Lee! [:)]

What brand of drive was it? Are you happy with it?

https://community.logos.com/discussion/comment/529649#Comment_529649

@Erik:

An experience I had three months ago.

Brand new SSD. Installed OS and everything, then strange glitches occurred. I almost returned the SSD!

Then I checked the support webpage. Lo and behold, a firmware update, barely two weeks old, that assured stability.

You can guess the rest. Updated firmware (which flushed out all the data) and reinstalled. It was smooth after that.

That may not be the situation in your case, but it remains a possibility.

Agree. That is what I was saying earlier, when I was a tech with Apple, I cringed whenever I saw a 3rd party drive, or third party anything for that matter. I don't have anything against 3rd party stuff, but the creators at Apple seem to.

Lee

https://community.logos.com/discussion/comment/529654#Comment_529654

Thanks for the info Lee!

What brand of drive was it? Are you happy with it?

[:#] [:#] [:#]

https://community.logos.com/discussion/comment/529656#Comment_529656

I appreciate everyone's input, but as I stated above, the problem with this particular iteration seems to have been a glitch in the download process. Logos is running fine since I deleted and updated the indices. I am going to chalk this up to something in the download - it doesn't take much.

My SSD is running just fine. Apple uses Toshiba SSD's mostly, but the Samsung 830 and 840 series are both designed for use with Macs and do not have the issues other off-brand and lesser known SSD's have on Apples.