none
A failure was reported when trying to invoke a service application: EndpointFailure RRS feed

  • Question

  • I am noticing below error in the ULS logs:

    A failure was reported when trying to invoke a service application: EndpointFailure Process Name: w3wp Process ID: 1892 AppDomain Name: /LM/W3SVC/1303577831/ROOT-1-132179341008735794 AppDomain ID: 2 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:98e8a5829dcd48588a9075804a126cd3#authority=urn:uuid:0f4c2ac5b826414c9d0f1d13a1d4d759&authority=https://abc.com:32844/Topology/topology.svc Active Endpoints: 2 Failed Endpoints:2 Affected Endpoint: http://abc.com:32843/98e8a5829dcd48588a9075804a126cd3/SearchService.svc

    Not sure what is going on. I checked and all the application pools and IIS web sites are running. Only issue is that the application "98e8a5829dcd48588a9075804a126cd3" is listed under old IIS site which is stopped. I cannot start this web site because there is another IIS site running on the same port number 32843.

    Please see below. OLD SharePoint Web Services is a stopped IIS site as opposed SharePoint Web Services whose IIS site is started. How can I move the application "98e8a5829dcd48588a9075804a126cd3" from old sharepoint web services site to sharepoint web services site? Any pointers?

    Monday, November 11, 2019 9:44 PM

Answers

All replies

  • Hi, diffident, 

    As you mention, the Old SharePoint Web Service site is stopped. And the error message showing the affected endpoint is SearchService.svc. Do you currently have any issue concerning search service? If everything is working fine, and you have no plan to restart the old service site in the future, i will recommend you to ignore the error as it has no impact on your farm. 

    Best Regards

    Jerry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, November 12, 2019 8:12 AM
  • It is affecting timer jobs that query search service. How can I bypass this issue? As you can see the endpoint that I need is in the old site and I cannot start the old site because it is using the same port and new one. Is there a way I could move "98e8..." application from old to new site? I suspect it is all done internally by SharePoint?
    Tuesday, November 12, 2019 4:05 PM
  • Hi, diffident,

    Just like you say, all the configuration in IIS site shall be done by SharePoint internally. It is always not recommended to change it manually. As it seems the issue is on your search service application, i will recommend you to re-create the Search Service application.

    Best Regards

    Jerry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, November 14, 2019 8:59 AM
    • Marked as answer by diffident Friday, November 15, 2019 4:26 PM
    Friday, November 15, 2019 4:26 PM
  • Hi, diffident,

    Thanks for sharing your solution here! It will help other community members with similar issues. Here I will provide a brief summary of this post for your information.

    ====================================================================

    Issue Symptom:

    There are errors in ULS logs

    A failure was reported when trying to invoke a service application: EndpointFailure Process Name: w3wp Process ID: 1892 AppDomain Name: /LM/W3SVC/1303577831/ROOT-1-132179341008735794 AppDomain ID: 2 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:98e8a5829dcd48588a9075804a126cd3#authority=urn:uuid:0f4c2ac5b826414c9d0f1d13a1d4d759&authority=https://abc.com:32844/Topology/topology.svc Active Endpoints: 2 Failed Endpoints:2 Affected Endpoint: http://abc.com:32843/98e8a5829dcd48588a9075804a126cd3/SearchService.svc

    ====================================================================

    Possible Cause:
    The old search service application is no int the current running SharePoint Web services IIS site. 

    ====================================================================
    Solution:
    Add new application in the running Web Service IIS site

    Reference Links:
    https://gai3kannan.wordpress.com/2015/04/15/a-failure-was-reported-when-trying-to-invoke-a-service-application-endpointfailure-solution-step-by-step/

    Best Regards

    Jerry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Monday, November 25, 2019 8:57 AM