SharePoint 2010 Foundation site collection not assigned to an indexer

I have recently being configuring a basic SharePoint 2010 Foundation setup for a client and noticed that I was unable to perform searches. When I attempted to I received the error “Your search cannot be completed because this site is not assigned to an indexer. Contact your administrator for more information.”

Apparently something didn’t happen during the configuration steps for the Web Application/Site Collection. After having a look around I found the following worked to rectify the problem:

  • Go to SharePoint Central Administration > Application Management > Manage Content Databases (Underneath Databases).
  • Select the correct SharePoint web application associated Content database  – this will open the  “Manage Content Database Settings” page. 
  • Make sure that the Search Server is set on the “Manage Content Database Settings” page.
  • You might also like to check the Timer Jobs server details as well. Mine wasn’t set either.
Advertisements

7 Comments

Filed under General SharePoint Development, SharePoint 2010

7 responses to “SharePoint 2010 Foundation site collection not assigned to an indexer

  1. J

    This tells me where to correct the issue. Thanks for that; however, the area is grey’d out and not configurable. Any ideas how to make this an editable field?

    • Hi J.
      the behaviour you refer to makes sense if you are in fact using either of the SharePoint 2010 Server editions instead of the Foundation edition. Within the Server editions search is handled differently i.e. it is supported as a managed Service Application that can index many content sources rather than as a simple service running on a restrictive content DB basis as it is under the Foundation version. In the server editions you will need to configure the Search service application and will not run the SharePoint Foundation Search service at all i.e. if you have a look at the services running under Services on Server you will see the following…

      Search Service configuration

  2. Brian

    I too had a drop-down menu I could not edit, but that’s because there’s more things on SharePoint Foundation 2010 that need to be SETUP: SharePoint Central Administration > under System Settings > Manage services on server > SharePoint Foundation Search > Service Account: SharePoint account > Content Access Account: SharePoint account > Database Server: Usually same as main SharePoint database server > Database Name: SharePoint_Search_SERVER## > Indexing Schedule: Daily 12AM-6AM > OK > Start (the service must start or you can’t select the “search server” later) > Application Management > under Web Applications > Manage web applications > highlight the web application you want search to index > in the ribbon click User Policy > Add Users > Zones: (All zones) > Choose Users: enter the name of the Content Access Account (i.e. SharePoint account) > Choose Permissions: Full Read > Finish > OK > Application Management > under Databases > Manage content databases > click the appropriate SharePoint web application associated content database that contains the site(s)/site collection(s) you want to index > Search Server: select your SharePoint Server > OK.

    You can force a CONTENT CRAWL: Start a crawl: ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm -o spsearch -action fullcrawlstart’.

    Just in case you delete a SharePoint search index database (DELETE): You can delete the search index database file from the database server and then stop the “SharePoint Foundation Search” service, but to recreate the search index database you will need to create a “different” database name and in SharePoint Central Administration > under Application Management > Manage content databases > click the appropriate SharePoint web application associated content database that contains the site(s)/site collection(s) you want to index > Search Server: select your SharePoint Server > OK, and then you can do the same again to go back to the original database name if you like. Run C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm -o spsearch -action fullcrawlstop’, then start a content crawl again. See also database references in SharePoint 2010 Management Shell: Run ‘get-spdatabase’.

  3. Mike

    Very Helpful and Brian’s comments got us going in the correct direction for foundation.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s