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

SP2013 Crawling *Explained: Enumeration/Discovery (Part 3b)

With VerboseEx logging enabled, the crawl of a single item (or interchangeably, a “document”) can generate more than 6000 ULS events, at times making troubleshooting a particular document analogous to finding the needle in the haystack. In this series of posts, I first described the high level orchestration for crawling a document, deep dived on the…

3

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

SP2013: Using Get-SPIndexReports to Troubleshoot Failed Master Merge

Ever had an SP2013 Index Component report a yellow exclamation point () to indicate a “degraded index component” and then wondered what that really meant? From my experience, these almost always either tied to an underlying disk problem and/or some external software interfering with the component (most commonly, AntiVirus or file-level backup utilities). In this post, we’ll specifically look…

6

The Upcoming Cloud SSA and Next Generation Hybrid Search: Initial Thoughts

At the Microsoft Ignite Conference last week, we got our first look at the upcoming SharePoint Cloud Search Service Application (Cloud SSA), which enables on premise environments to push content to a Search Index running in SharePoint Online (SPO). And with it coming to SharePoint 2013 by the end of the year (and to SharePoint…

1

MS Ignite “Effective Search Deployment” Session References (BRK3176)

Thank you everyone that came by to talk about our favorite subject… Search. We are incredibly grateful for the number of folks that added us to their schedule, and we hope you came away learning something new. If your company or organization has a Premier Support contract and you need to engage us on anything…

1

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

Another Shameless Self-Promotion: Presenting at Microsoft Ignite 2015

Coming to Microsoft Ignite next week? Then I invite you to come see Kristopher Loranger and I present on Tuesday, May 5: Effective Search Deployment and Operations in SharePoint Server 2013       We’ll be covering some architecture best practices, detailed look at query flows and the indexer. Most of the focus will be OnPrem SP2013, but we expect…

0

SP2013 Search Index health reports for monitoring and troubleshooting

Update: The newest version of the Search Index Health Reports script can now be found with our Search Health Reports (SRx) Core diagnostic tools, which can be downloaded from the TechNet Gallery here. ———- Ever had an SP2013 Index Component report a yellow exclamation point () to indicate a “degraded index component” and then wondered what that…

1