Query Server Not Responding or Query Component Not Responding in SharePoint Search

Query Server Not Responding or Query Component Not Responding in SharePoint Search

Background : SharePoint Search new data is not getting crawled and the full & Increment crawling is never-ending.
Exception : Search Administration page
Propagation Status : Query server not responding(Guid – query-1)
Search Application Topology : Query Component Not Responding
Crawl Log :The server is unavailable and could not be accessed. The server is probably disconnected from the network.

Root Cause : When the query component is not responding then the SharePoint Search will not crawl the new content from the sites and it will not search the data from the new content sources created. Hence, the crawling status will not change.
Workaround : Before the general workarounds you can try different methods.
if you are fine with Search downtime and Index Reset, Please proceed with Method 1

Method 1 : Restart the Search Server Service
Restart the Search Server Service , Execute the below command on effected query server
stsadm -o osearch -action stop
stsadm -o osearch -action start -role query
if problem persists check the permissions of Index Folder, Ensure WSS_ADMIN_WPG, IIS_WPG has permission on this folder
You can find the location of index folder in Search Application Topology,Query Component>> Edit properties

General Location of Index. : C:\Program Files\Microsoft Office Servers\14.0\Data\Office Server\Applications
If the WSS_ADMIN_WPG, IIS_WPG don’t have read & execute access in Applications folder,Please grant read and execute permissions and check whether the issue resolves. If till issues persists please try Method 2

Method 2 : Change Index file Location
STSADM.exe –o osearch –propagationlocation “C:\NewLocationPath”
if the issue didn’t solve after executing the above command, please try Method 3

Method 3: Add a new query component
On the SharePoint Central Administration Web site, click General Application Settings and in the Search section click Farm Search Administration.
In the Search Service Applications section, from the list select the search service application that generated the event, and then click Modify Topology.
On the Topology for Search Service Application page, click the failed query component in the topology list, and then select Add Mirror from the component’s drop-list.
In the Add mirror query component dialog box, select the query server and associated metadata database for the new query component, and then click OK.
Click Apply Topology Changes. The changes are processed for the search application and the index is copied from the failed query component to the new query component.
Click the failed query component and click Delete.
The topology removes the index from the failed query component and deletes the component.
You can able to fix this issue using any one of above methods