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?)
SharePoint Health Analyzer rules reference SharePoint 2013
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.
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 […]
If your Usage and Health Data Collection Proxy is in a stopped state here is a quick bit of PowerShell to to get it started: $sap = Get-SPServiceApplicationProxy | where-object […]
what you can do if your SharePoint is sometimes very slow. E.g.: on the first start of a Site Sometimes during the day a search query will take about a […]
Users and Permissions: People and Groups: _layouts/people.aspx Site Collection Admins: _layouts/mngsiteadmin.aspx Advanced Permissions: _layouts/user.aspx Master Pages: _Layouts/ChangeSiteMasterPage.aspx Look and Feel: Quick Launch settings page: /_layouts/quiklnch.aspx Title, Desc, and Icon: _layouts/prjsetng.aspx […]