In my few previous post, I described how search service application has been created and configured. But just creating a service application doesn’t solve our purpose. We must have some page or site where user can use this application to perform search. SharePoint has some built in site templates(Enterprise search) to use search application features. In this post I will explain how one can create search site by performing simple steps.
As per the project infrastructure, we can either create a separate web application for search but I will create search site collection under the same web application where default SharePoint site is configured.
Creating an “Enterprise search center” site:
Navigate to Central Administration > Application Management > Site Collections, then click on Create site collections.
Ensure you are creating the Site Collection below the relevant Web Application.
Enter your Title, Description etc and select the Enterprise Tab under Template selection. Select the Enterprise Search Center, specify your site collection administrators and click OK.
This will create a basic search site collection as shown below:
If you have already completed full crawl from the search service application, you can now perform searches just for testing purpose. Also you can perform the people search.
Issues 1: This item and all items under it will not be crawled because the owner has set the NoCrawl flag to prevent it from being searchable
In the site collection settings under the “Site Administration” setting, there’s an option called “Search and offline availability” which contains a switch that seems to be disabled by default for certain templates (eg for the “Blank” site template, “Search Centre” or “My Sites”). If you are getting messages in the Unified Logging Service on the SharePoint Servers that looks like “This item and all items under it will not be crawled because the owner has set the NoCrawl flag to prevent it from being searchable”, then go into Site Settings –> Site Administration –> “Availability of search and work offline” for the site in question and set the “Indexing Site Content” switch to “Yes”.
Easy to fix, hard to find – all of the other search controls for a site collection are located under the “Site Collection Administration” setting, but this one – and ONLY this one – is tucked away under “Site Administration”.
Issues 2: People search is not working.
Resolution: Make sure that your search crawler administrator account must have adequate permissions on User profile service to search for people.
Navigate to “Search service application” home page. Under system settings find the value of “Default content access account” which will be search crawl admin account.
Now navigate to the “User profile service application” under “Manage Service application” option. Simple click once on the application name so that its shown selected. Now Click on “Administrators” from the top ribbon.
In new dialog box, make sure search crawl administrator account has been added, if not simple add it and also make sure that it have rights to “Retrieve People Data for Search Crawlers”.
Configure search time-out settings
To configure search time-out settings
- Verify that the user account that is performing this procedure is an administrator for the search service application.
- In Central Administration, in the Quick Launch, click General Application Settings.
- On the General Application Settings page, in the Search section, click Farm Search Administration.
- On the Farm Search Administration page, in the Farm-Level Search Settings section, click the value of the Time-out (seconds) setting.
- In the Search Time-out Setting dialog box, in the Connection time (in seconds) box, type the number of seconds that you want the search system to wait when attempting to connect to a content repository.
- In the Request acknowledgement time (in seconds) box, type the number of seconds that you want the search system to wait for a content repository to respond to a connection attempt.
- Click OK.