A few users report that when they connect to pages containing Content Search web parts, the web part displays: Sorry, something went wrong. When the VIEW DETAILS link is clicked, these users sees this:
The communication object, System.ServiceModel.Configuration.ConfigurationChannelFactory`1[Microsoft.Office.Server.Search.Administration.ISearchServiceApplication], cannot be used for communication because it is in the Faulted state.
Correlation ID: 00000000-0000-0000-0000-000000000000
Most other users report that when they navigate to such pages, the Content Search web part displays content as expected. Below is my investigative method to resolve this issue.
- A single user experiences the issue
- Farm employs Windows network load balanced: WFE1 + WFE2, where WFE1 has priority
- One Application server
- SharePoint 2013 farm is patched through July 2015
- All Windows Server 2012 are patched through July 2015
- Verified user experience: user was able to reproduce issue.
- Could not reproduce issue from administrator workstation.
- Ad hoc selection of other users could also not reproduce user issue.
- Windows Server Services: Search services running on both WFE1, WFE2
- SharePoint Services on Server: Search services running on both WFE1, WFE2
- SharePoint Search Administration: all search components up and running (green checks)
- IIS: all sites and application pools started on both WFE1 and WFE2
- Able to reproduce issue by logging into WFE2 and then connecting to the page.
- ULS Logs: instances of the error message (presented above) was found in the ULS logs for WFE2 only.
- Found a posting, Unable to search Document Library, suggesting search component service restart and IIS restart to resolve similar problem.
- Restart the Windows Server services SharePoint Search Host Controller and SharePoint Server Search 15: issue still presents on WFE2.
- Restart the SharePoint Server service Search Query and Site Settings Service on WFE2: connecting to page on WFE2 returns HTTP 500.
- Perform IISRESET on WFE2: connecting to page, while logged into WFE2, Content Search web part now displays content as expected.
- Identify that server hosting the problematic Search service
- In Central Administration > Services on Server, restart Search Query and Site Setting Service on the server.
- On that server, perform IISRESET.