I am not sure when this might have started, but it was brought to my
attention today that the Solutions search function is not working
properly. I've found several other threads that reference similar
problems but no solution has been posted other than upgrade (re: https://forums.manageengine.com/topic/problem-with-searching-in-solutions-database).
I upgrade weekly, currently on Build 9032.
What's odd is that the main search box yields questionable results, but the secondary column search fields work OK. For instance, we have 7 solutions with "Password" in the title. All 7 are approved. Five of them public, 2 are tehnician-only. Searching "password" in the "search all solutions" field (with "All Solutions" set) finds 2 of them, both public. This happens both as a technician and as a regular user. But searching "password" specifically by the title field finds all 7 as a technician, 5 as a user.
Also, there are other solutions contain the word "password" without it being in the title, and none of them come up under either kind of search.
One thing I've noticed, and I've not dug into this much yet, is that the 3 solutions missing from the user search all have images embedded in them. Maybe something throwing off indexing there?
What's odd is that the main search box yields questionable results, but the secondary column search fields work OK. For instance, we have 7 solutions with "Password" in the title. All 7 are approved. Five of them public, 2 are tehnician-only. Searching "password" in the "search all solutions" field (with "All Solutions" set) finds 2 of them, both public. This happens both as a technician and as a regular user. But searching "password" specifically by the title field finds all 7 as a technician, 5 as a user.
Also, there are other solutions contain the word "password" without it being in the title, and none of them come up under either kind of search.
One thing I've noticed, and I've not dug into this much yet, is that the 3 solutions missing from the user search all have images embedded in them. Maybe something throwing off indexing there?