Reprovision sharepoint search service

Reprovision sharepoint server search service when there is a situation where you find status of sharepoint server search service in stopping state. When there is an issue in search service application and its component due to which sharepoint search is not working. You need to restart service sharepoint server search. While restart, you find the sharepoint server search service stuck stopping state. In that case this post is helpful.

Advertisements

Restart sharepoint server search service

Run below script to restart or reprovision sharepoint server search service.

Add-PSSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue
$SearchServiceInstance = Get-SPEnterpriseSearchServiceInstance -Identity "WIN-Q2REPGHF9DU"
Start-SPEnterpriseSearchServiceInstance -identity $SearchServiceInstance # Wait for search service instance to come online
do {$online = Get-SPEnterpriseSearchServiceInstance -identity $SearchServiceInstance; Write-Host "Waiting for service: " $online.Status}
until ($online.Status -eq "Online")
Advertisements

Once script started running, you will find the details as seen in figure below.

sharepoint server search service status stopping
Advertisements

The service sharepoint server serach will be stopped first, then will chanage to state starating and finally will come to status as Started.

sharepoint server search service
Advertisements
Advertisements

full crawl takes too long to complete sharepoint search

I faced an issue with sharepoint search where full crawl takes too long to complete nearly 240 hours. Requirement was how to reduce the full crawl time.

  • Search service is working fine.
  • search components are online and heathy.
  • There is enough space in the server drive hosting search components.
  • Checked event log in the server hosting crawl component and found the below error
Event ID: 30
Description: The search service stopped the filter daemon because it was consuming too many resources. A new daemon will automatically be started, and no user action is required.
Advertisements

Also from crawl logs found most traces related to memory quota choking like as below

The filter process could not be initialized when trying to process this item. Verify that the file extension is a known type and the item is not corrupt.
Advertisements

Resolution

so as to resolve the issue, we need to made some changes in registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Global\Gathering Manager
Advertisements

Change the properties of below two items to 200 MB from the default value of 100 MB.

  • FilterProcessMemoryQuota
  • DedicatedFilterProcessMemoryQuota
Advertisements

follow the video below to get detail step by step information of the changes to do.

Advertisements

Get content source in sharepoint 2019 search service application using powershell

Get content source in sharepoint 2019 search service application using powershell. follow the code below to get the list with Name, Id, Type, CrawlState, CrawlCompleted date and time

$ssa=Get-SPEnterpriseSearchServiceApplication
Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $ssa
Advertisements
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-8844016778182294 (adsbygoogle = window.adsbygoogle || []).push({});
Get content source in sharepoint 2019 search service application using powershell
Advertisements

Get content source SharePoint Search Using Powershell | #SharePoint2019#SearchServiceApplication

Get content source SharePoint Search Using Powershell | #SharePoint2019#SearchServiceApplication
Advertisements
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-8844016778182294 (adsbygoogle = window.adsbygoogle || []).push({});