When gathering files from a content source, the SharePoint 2013 Crawl Component can be very I/O intensive process – locally writing all of the files it gathers from content repositories to its to temporary file paths and having them read by the Content Processing Component during document parsing. This post can help you understand where the Crawl Components write temporary files, which can help in planning and performance troubleshooting (e.g. Why does disk performance of my C:\ drive get so bad – or worse, fill up – when I start a large crawl?)
When doing a search, using the farm account, you get search results, but when a “Normal” user does a search, they did not get any results.
Go through the article in detail for error and solution.
I came across a situation where user is trying to search documents selecting the option “search in same site” instead of “all sites” from search box and getting no result where as can find documents from other library with in same site.
Why such happens ?
The first point comes to mind for search error is content not crawled, indexing not done for this situation.
Yes , its true but we need to think why ?
During various search troubleshooting i came across the following crawling error in the Crawl log of a SharePoint 2013 environment. Processing this item failed because of an unknown error when […]
Error: SharePoint Crawl Log Error: The SharePoint item being crawled returned an error when attempting to download the item for example .aspx files Solution: 1.Open Regedit on your search server/s […]
Display templates for the Content Search Web Part You can use the following display templates to change the appearance of content that is shown in a Content Search Web Part. […]
We can access and analyze several query and crawl health reports, logs and usage reports from the Search service application in the SharePoint Central Administration to monitor the health of the search system.Go throught the post for indetail.