EricHarlan

Lucky for me every so often when im dispatched on a reactive case I’m met by some other smart softies when I get on site. This time lucky for me it was Isaac Stith (@mrisaac). The problem was every 3-4 searches that were done in SharePoint would error out and give a coorilation ID.  Obviously not a good thing so bright idea was raised by my MCS colleague to make sure that all the servers being requested were in fact part of the search infrastructure. Turns out they were allocated in the config database as query servers but they did not have the search services enabled. They had been taken out to be used elsewhere.  So after running a few PowerShell commands to remove the servers from the search rotation the issue was resolved.  By the way, I owe Isaac Pho for a week for fixing this before I got there.

Here is the errors we were getting in the ULS (data has been scrubbed)

CRITICAL SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure Process Name: w3wp Process ID: 8932 AppDomain Name: -AppNameRemoved- AppDomain ID: -AppIDRemoved- Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:-ServiceRemoved-#authority=urn:uuid:-UIDREMOVED-&authority=https://SERVERNAME/Topology/topology.svc Active Endpoints: 6 Failed Endpoints:1 Affected Endpoint: http://SERVERNAME/-ServiceIDRemoved-/SearchService.svc -GuidRemoved-

Here’s the errors in the event logs

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          5/17/2012 1:44:10 PM
Event ID:      8313
Task Category: Topology
Level:         Error
Keywords:
User:          -UserRemoved-
Computer:      -ComputerRemoved-
Description:
SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
Process Name: w3wp
Process ID: 8932
AppDomain Name: -AppDomainRemoved-
AppDomain ID: -AppDomainIDRemoved-
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:-ServiceIdRemoved-#authority=urn:uuid:-URIRemoved-&authority=https://SERVERNAME/Topology/topology.svc
Active Endpoints: 6
Failed Endpoints:1
Affected Endpoint: http://SERVERNAME/-ServiceIdRemoved-/SearchService.svc

And the PowerShell commands we ran:

$qs = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -local

 

Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $qs

Tagged on:

Leave a Reply

Your email address will not be published.

No seriously, are you human? *