Connect with Us
Blog: Do More With Search

How to Disable Phonetic Search in SharePoint 2010 People Search

Written by Sanjaya Paudel on . Posted in Beyond the Command Line, How-to Guides, SharePoint 2010

SharePoint 2010 People SearchPhonetic name matching and nickname matching is a new feature addition to SharePoint 2010 People Search. As per TechNet, users can search for a person in the organization by name without knowing the exact spelling of the name. For example, the search query “John Steal” could yield “John Steele” in the search results; results for the search query “Jeff” include names that contain “Geoff.” In addition, nickname matching makes it possible for a search query for “Bill” to yield results that include “William.”

It works as advertised, but seriously messes up results ranking. For example, if you search for Anjaya: people with names like Sanjaya, Ranjana and all other variations show up on the first page of results while the persons with name Anjaya are buried in 2nd, 3rd, or 4th pages of results.

FAST Search for SharePoint Error: Unable to resolve Contentdistributor

Written by John Ross on . Posted in Beyond the Command Line, FAST Search, Guest Industry Experts

I’ve been working on a custom search project recently and ran into an issue that had me scratching my head.  My FAST Content SSA wasn’t able to crawl successfully crawl content.  When I kicked off a full crawl it wouldn’t fail, but it would continue to run until I manually stopped it, never returning a single error, warning, or anything.  When I looked at the Event Viewer on the SharePoint Server I saw this:

Event-Driven Crawl Schedule

Written by Agnes Molnar on . Posted in Beyond the Command Line

Recently I’ve been working for a customer where I’ve found some interesting requirements: they had several content sources and wanted to crawl them one by one after each other. Scheduling the incrementals for fix time was not a good solution as their content incrementals were very hectic: incremental crawl for the same content source took 5 min at one time, then 1.5 hours next time. And of course, they didn’t want idle time.

But we cannot define these kind of rules from the UI, so the ultimate solution was PowerShell.

First, we need to be able to start the crawl. Let’s talk about Incremental Crawl only this time. Here is the PowerShell script for this: