Problem
You recently rebuilt your SharePoint 2013 farm's Managed Metadata service application, and it runs without issue. A day later, you check the SharePoint application server application event log, and see the following events:
Solution
Notes
You recently rebuilt your SharePoint 2013 farm's Managed Metadata service application, and it runs without issue. A day later, you check the SharePoint application server application event log, and see the following events:
Log Name: Application Source: Microsoft-SharePoint Products-SharePoint Foundation Date: [Date/Time] Event ID: 8313 Task Category: Topology Level: Error Keywords: User: [Farm Service Account] Computer: [Application Server] Description: A failure was reported when trying to invoke a service application: EndpointFailure Process Name: OWSTIMER Process ID: 1884 AppDomain Name: DefaultDomain AppDomain ID: 1 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service: 26fdc21debf74e8a8fbb25146d98c2c4#authority=urn: uuid:3e1fa89c3f23469f8e4947ba8a99c448&authority= [Application Server]/Topology/topology.svc Active Endpoints: 1 Failed Endpoints:1 Affected Endpoint: [Application Server]/26fdc21debf74e8a8fbb25146d98c2c4/ SearchService.svc Event Xml: ...and
Log Name: Application Source: Microsoft-SharePoint Products-SharePoint Foundation Date: [Date/Time] Event ID: 8313 Task Category: Topology Level: Error Keywords: User: [Farm Service Account] Computer: [Application Server] Description: A failure was reported when trying to invoke a service application: EndpointFailure Process Name: w3wp Process ID: 15280 AppDomain Name: /LM/W3SVC/522633276/ROOT-1-130460993295064685 AppDomain ID: 2 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service: 7c3ac0e364d64a9bad706582b3ae004d#authority= urn:uuid:3e1fa89c3f23469f8e4947ba8a99c448&authority= [Application Server]/Topology/topology.svc Active Endpoints: 1 Failed Endpoints:1 Affected Endpoint: [Application Server]/7c3ac0e364d64a9bad706582b3ae004d/ MetadataWebService.svc Event Xml:
Solution
- Rebuild the search service application.
Notes
- The reference cited above did not directly apply to our situation but pointed the way to the solution: namely, rebuilding the affected service.
No comments:
Post a Comment