Run a full recover and look the resulting recover log.
Dont use the recovered file.
There are generally two reasons why Finds fail:
1) The index is damaged (a form of corruption)
2) Searching on unstored calculations that are not refreshing properly
What is the search that is showing incorrect results? What field types and storage?
and for 2) there have been cases in the past where results where different from a hosted solution than when test as a local copy.
Mike, there are at least two finds that search unstored calculations that are not working but only when the file is being hosted on FM15 server - when opened on a local machine the search works okay. - Is there a fix for that?
Yeah. Don’t search on unstored calculations.
I’m not 100% certain of the cause of this phenomenon, but I suspect it has something to do with data caching and refreshing. If you can, eliminate the unstored calculations and use scripting to populate the fields instead.
Other things to look at are server performance and (especially) network latency.
1 of 1 people found this helpful
Here's a previous thread that discusses the issue. Be sure you're up to date on all your patches, because the last comment in the thread says it's been fixed in 15.0.2.
Mike, thank you - I'll ask our IT department to update the server - and your first point is helpful as well, I'll look at those two reports and find a better way too get the results we need. Thanks again