Reasons to do a full crawl (*and it’s not for schema changes)

To avoid burying the lede, I’ll start by “boldly” saying… *You don’t need to regularly schedule a full crawl for SharePoint Search I’ve been at this long enough to realize that someone likely has an exception to this – but I truly cannot think of a reason to schedule full crawls (especially for SharePoint content)….

3

Crawler Performance, Hosts, and Impact [Hit] Rules

As part of the crawl processing flow, the Crawl Component starts “robot” threads that orchestrate items from gathering to feeding and finally committing their final state (see this previous post on Crawl Orchestration for more details and an illustration of that flow). In this post, we focus more on the “robot” threads, Crawler impact rules,…

4

Search Health Reports (SRx) – Digging in further with PowerShell

After introducing the Search Health Reports (SRx) last year, we continued to extend the battery of PowerShell tests for analyzing and troubleshooting a SharePoint 2013 and SharePoint 2016 on-premises search farm. Because most of these efforts resulted in new or improved tests, we largely suggested and recommended the RunAllTests report and Indexer Disk report to leverage the SRx…

0

Announcing the Search Health Reports (SRx) for SharePoint Search Diagnostics

Brought to you by SearchEngineers@microsoft.com, the Search Health Reports (SRx) is a PowerShell-driven tool for surfacing complex diagnostics for SharePoint Search through new multifaceted reports. The SRx includes a battery of tests that leverage a customized SSA object extended with contextual data from many disparate sources. Our goal with this project is straightforward – empower…

14

SharePoint Search Topology Limits Clarified for the Crawl Component

As more environments begin scaling out to the documented limits for Search, a common question tends to get asked… “Does the Crawl Component count against the 64 component limit?” The short answer is… no, the Crawl Component does not count against the 64 component limit, and the documentation stating this has now been updated here…

0

PowerShell to Deploy an SSA Across Multiple Servers (v2.0)

A few years back, I published a PowerShell script to deploy a SharePoint Search Service Application across multiple servers, but it admittedly had a few quirks in regards to Index path location… until now. Below, I’ve attached the new/updated version 2.0 of the deploy script (and will also upload to the TechNet Scripts center soon) and have a…

7

From SPC14: “Troubleshoot Search” session (spc375)

Wow! I wanted to send a huge thank you to the >500 folks that attended our session today and for the very gracious feedback. Here is a link to our session on Channel9: How to manage and troubleshoot Search: A practical guide (SPC375)https://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC375   And as promised, here’s the PowerShell that I build for filtering the ULS by…

4

SP2010: Search Query Load Balancing *Explained (part 2)

In part 1, I described the load balancing that occurs among Query Components (e.g. SSA load balancing). In this post, I’m expanding the focus to the load balancing involved when there are multiple instances of the SQ&SS (e.g. Farm level load balancing) and from this, begin to explain why the “Internal Server Error Exception Occurred” failure is intentionally ambiguous. I’ll then wrap up this…

4

SP2010: Removing/Re-joining Server to a Farm Can Break Search

Removing or re-joining a SharePoint Server that hosts a Search component will typically break the Search Topology and lead to an inconsistency between the ServerID being referenced by the applicable Search component(s) and the SharePoint farm Configuration object for the applicable server.  Translation you ask? Each Search component object has a reference to the SharePoint on…

2

SP2010: Troubleshooting ServerID Mismatch (Deleting Components)

In a another post, I described a scenario where removing/re-joining a SharePoint Server that hosts a Search component will lead to an inconsistency in the ServerID being referenced by the applicable Search component(s) and the SharePoint farm Configuration object for the applicable server. If you identify a ServerID mismatch, the recommendation is to remove (or…

1