Things To Know When Configuring FAST Search

I’ve been doing a fair bit of FAST search configuration and re-configuration lately, and I just wanted to point out a few things that are good to know and understand.

Let’s start with some basics. If you use the following guide for configuring FAST (and I usually do), then you should be aware of:

  • You configure two service applications for FAST: FAST Content and FAST Query SSA. FAST Content is a FAST Search Connector. FAST Query SSA is FAST Search Query.
  • The FAST Content service application is where you configure your Content Sources and crawl MOST content. Please note that I say MOST and not ALL. Your user profiles or ‘People’ search, are crawled using the FAST Query SSA.

    Please reference this article for details: This is a key thing to understand, because until you initiate a crawl for the Local SharePoint sites Content Source in the FAST Query SSA, you won’t see any people results in the People scope.
  • If you’re trying to figure out HOW to crawl your user profiles, make sure that the following url is added to your FAST Query SSA – Local SharePoint sites Content Source: sps3://serverurl.

Some other things I’ve noticed:

And finally, if you come across this error:

The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component ’43fa5edd-3e14-4dba-b54c-7aad045dfdf7′ in search application ‘FASTContent’ is in a good state and try again.

Run the following command:

stsadm -o provisionservice -action start -servicename osearch14 -servicetype "Microsoft.Office.Server.Search.Administration.SearchService, Microsoft.Office.Server.Search, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c"

5 Responses to “Things To Know When Configuring FAST Search”

  1. Chris February 17, 2012 at 5:17 am #

    Thank you for posting this. I had the problem you stated above, and this stsadm command fixed it straight away. So far the only person who has provided a correct fix.
    Thanks again.

  2. shereen February 17, 2012 at 10:56 am #

    Glad it was useful to you Chris! It was a tricky one to resolve.

  3. Tom February 27, 2012 at 7:08 am #

    You have saved my life. your stsadm command has resolved my problem which took me a few hours scratching my hair… thanks heaps.

  4. shereen February 27, 2012 at 9:29 am #

    You’re welcome Tom! I struggled with it myself and knew it was worth a post.

  5. Sherif November 6, 2014 at 2:22 pm #

    Thanks a lot , the ContentDistributer issue happened with me , i tried many fixes , only solved by your fix ,
    Thanks a lot

Leave a Reply