1. Sharepoint 2013 Search List

How to find and set the search index location in SharePoint 2013 Posted on August 28, 2015 by Admin With this post I’ll try to explain the complete step-by-step guide how to check and change Search Index Location in SharePoint 2013. The SharePoint product comprises many different components and can perform a wide variety of tasks. Use this list to get a quick handle on which part of SharePoint does what. SharePoint Foundation: SharePoint Foundation is a foundational program that enables communication, collaboration, and content management; it comes free with the Windows Server operating system.

Once upon a time, after a whole server farm reboot, one of my search component was broken. Content crawling was taking forever, and the ULS were not very explicit. In the central administration, I could see this :

My application server was unable to run the « Content Processing Component », even if I restart the whole search service (net stop / start OSearch15).
I noticed 2 things that drove me to the solution :
– First, a noderunner.exe process was missing. This confirmed the red cross in the central administration. There was 2 processes instead of 3 (the crawler doesn’t spawn a noderunner.exe process) :

– On the second hand, there was strictly no logs in the « 15.0DataOffice ServerApplicationsSearchNodesContentProcessingComponent » directory !
It was like the search topology was ignoring this component. So I decided to re-install the search topology, just by cloning it, and activating it :

$searchApp = Get-SPEnterpriseSearchServiceApplication
$initialTopology = Get-SPEnterpriseSearchTopology -SearchApplication $searchApp -Active
$cloneTopology = New-SPEnterpriseSearchTopology -SearchApplication $searchApp -Clone -SearchTopology $initialTopology
Set-SPEnterpriseSearchTopology -Identity $cloneTopology -SearchApplication $searchApp

And it works, without any service interruption !

The Search service application introduced in SharePoint 2013 is different than that of SharePoint 2010 in more ways than just one.
To start with, SharePoint 2013 uses the web-based interface to change the current status of the topology. It can only be done by using Windows PowerShell. SharePoint Server 2010 also included a web-based option for changing the topology.
The Search Query web service is deprecated in SharePoint 2013. Search in SharePoint 2013 supports FAST Query Language (FQL) syntax and Keyword Query Language (KQL) syntax for custom search solutions. You cannot use SQL syntax in custom search solutions - FullTextSQLQuery was used for this purpose in SharePoint 2010. In SharePoint 2013, this class has been deprecated. It doesn't even support backward compatibility.
Custom search solutions that use SQL syntax with the Query object model and the Query web service that were created in earlier versions of SharePoint Server do not work when you upgrade them to SharePoint 2013. If you submit queries by using these applications, you will receive an error.
There are a lot more features which have been deprecated in SP 2013, thorough details of which you can find here.
The information I am going to share with you will help you configure your search service application to get it up and running for your sites. We will start with changing the default search topology and then move on the Search Service application configuration which I would cover in a different post. Please note that creating a new search topology is not a mandate if the Search is configured properly on your server.
Creating a Search Topology / Changing the Default Search Topology
For demonstrative purposes and making things easy to understand, I'll consider a farm consisting of only server. For multi-server approach, you may refer this link.
- Ensure that no crawls have been started and that the search index is empty on the server that hosts Central Administration.
- Verify that the user account that is performing this procedure is an administrator for the Search service application.
- In Central Administration, in the Application Management section, click Manage Service Applications.
- On the Manage Service Applications page, in the list of service applications, click the Search service application.
- Verify that the search index is empty. On the Search Administration page, under System Status, verify that Searchable items displays '0'. Here, if the Searchable items are not zero, discontinue this process and make sure you click on 'Reset Search Index'. Only then move on with the next steps.
- Verify that no crawls have been started. On the Search Administration page, under Crawling, click Content Sources. On the Manage Content Sources page, verify that the Status column for any existing content source displays Idle.
- Start a SharePoint 2013 Management Shell on one of the servers in the farm.
- Specify the new servers you want to add search components to, start a search service instance (ssi) on these servers and create references to the search service instances. In this procedure we have used the example host name 'server_name' for the server. At the Windows PowerShell command prompt, type the following command(s):
$host = Get-SPEnterpriseSearchServiceInstance -Identity 'server_name'
Start-SPEnterpriseSearchServiceInstance -Identity $host
- Wait until all the search service instances are running. At the Windows PowerShell command prompt, type the following commands until the commands return the state 'Online' for the search service instance:

Sharepoint 2013 Search List