We currently have a Search Application that was running normal until yesterday. I am not 100% sure when things went down but here is the scenario.
A new site collection was added to our server. During this time we stopped all currently running crawls. The site came up, we added some pages and such. We tested search and it worked.
This morning we restarted the crawls and search broke. The components and everything within Central Admin shows a green light, (All online, Nothing Recovering, etc). Crawls still process and complete normally.
When searching for an item such as "test" we receive a "Internal Server Error" with a Correlation ID, and time stamp. If we search for jibberish ("asde4cr") we receive the normal "No results found page").
Now if we do an "Index Reset" and DO NOT search the local SharePoint sites our search page populates normally.
What is causing items that are classifed as "Local" to cause the results page to crap out?
I have restarted IIS, checked permissions, changed permissions to see what happens, recreated the search, bounced the box and so on.
Here is the log blog I receive around the correlation ID
SearchBoxEx AfterDeserialize begin 742e3c50-063a-4d8b-ac96-51313ad9a961
SearchBoxEx AfterDeserialize end 742e3c50-063a-4d8b-ac96-51313ad9a961
FetchDataFromURL start at(outside if): 1 param: start 742e3c50-063a-4d8b-ac96-51313ad9a961
Filter category FASTMaxNumberOfFilters in the config is in wrong format.Input string was not in a correct format. 742e3c50-063a-4d8b-ac96-51313ad9a961
It looks like the error is related to
<Column Name="ContentClass"/>. If I:
- Modify the "Search Core Results" webpart on my results page
- Uncheck "Use Location Visualization"
- Apply, Save and Close
Where is the "Location XSL" that I am unchecking located at? I feel like I can change that to solve my problem?