To put it short, the file server's index would fail randomly.
The file server has Windows Search service enabled and indexed. There are many clients connected to this server, possibly up to 100. The client Windows (7/10) machines would fail to search the server. Green bar keeps going and going with no result shown.
On the server, it can be resolved by simply restarting the Windows Search (Wsearch) service. It would take a long time (like a minute) to stop/restart. When "stopped", it would throw out an error saying the service cannot be stopped. Below is the error thrown stopping the service from powershell.
Stop-Service : Service 'Windows Search (Wsearch)' cannot be stopped due to the following error: Cannot stop Wsearch service on computer '------'. At C:\Users\------\Documents\PSscript\Wsearch-stop.ps1:4 char:54 + Get-Service -Name $svc_name -ComputerName $pc_name | Stop-Service + ~~~~~~~~~~~~ + CategoryInfo : CloseError: (System.ServiceProcess.ServiceController:ServiceController) [Stop-Service], ServiceCommandException + FullyQualifiedErrorId : CouldNotStopService,Microsoft.PowerShell.Commands.StopServiceCommand
Sometimes it won't fail but it could also fail many times per day. We haven't been able to find out the culprit and have to restart it upon request. File operations are unhindered.
edit: I wonder if anyone had such problem. I found nothing on the net. My current solution is try to make a script to query the network index from a client computer and when found error, restart the service.