Pages

Monday, June 10, 2013

EventID 8313 A failure was reported when trying to invoke a service application: EndpointFailure

Symptom:
 This error (EventID 8313 appears over and over in the event logs.

A failure was reported when trying to invoke a service application: EndpointFailure
Process Name: OWSTIMER
Process ID: 12524
AppDomain Name: DefaultDomain
AppDomain ID: 1
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:1cdaa95887c54f3b94db90e82e1605ee#authority=urn:uuid:50d4e54d203e48dfbeffcbdbad44507c&authority=https://
servername:32844/Topology/topology.svc
Active Endpoints: 1
Failed Endpoints:1
Affected Endpoint: http://servername:32843/1cdaa95887c54f3b94db90e82e1605ee/SearchService.svc

Issue:
The Search Service Application was uninstalled and the error is the endpoint still trying to reach out to the site.
For service applications, SharePoint has a built-in load balancer that sends requests to all endpoints listed in the configuration database.  Basically, the endpoints are still listed in the configuration database as valid endpoints to send to, but they are not available, so there is an erorr.


Resolution:
I did an IISReset on all front ends after the Search Service was uninstalled and this error disappeared.

When I had this same error after installing and reinstalling the Profile Service, I couldn't get the error to go away.  So I uninstalled and reinstalled a third time.  Luckily, the Profile Service is not difficult to delete and recreate with a PowerShell script.  If I had user profiles and existing MySites (meaning that uninstalling was not an option), from what I have seen of this error, I could just ignore it.
Please comment if you have seen that is not the case. I'd love to be corrected.

No comments:

Post a Comment