Fix: There was no endpoint listening at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc that could accept the message

Recently, I faced an issue where I got error message below when trying to Publish SharePoint 2013 Workflow.

“Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : 10fb8c9c-74dd-e058-687d-57f284abd171. —> System.Net.WebException: The request was aborted: The request was canceled. —> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc that could accept the message. This is often caused by an incorrect address or SOAP action.”

SP2013WorkflowIssue

Initially, I try to spend time to troubleshoot the issue and ensure Workflow Manager installed and configured correctly by following this msdn article. Everything seems to be OK and the workflow can be save. Then I start googling and found the solution in msdn forum. Thanks Roy, you’ve made my Friday and save me a lot of time =) …

Solution
Start Windows Services -> Net.Pipe Listener Adapter service

I’m still not sure the reason why we need to start the service and it doesn’t even mentioned in Troubleshooting SharePoint 2013 Workflow article as well. Roy also mentioned that he just stumbled upon this service by associating the name “Net.Pipe” and the error message containing “There was no endpoint listening at net.pipe://…”

Reference
http://roykimsharepoint.wordpress.com/2013/05/31/sharepoint-designer-2013-publishing-2013-workflow-error/

Advertisements

Tagged: , , ,

4 thoughts on “Fix: There was no endpoint listening at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc that could accept the message

  1. Ravin Singh D 04/11/2015 at 9:43 AM Reply

    I have face below Error in office web apps.

    Unhandled exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc.

    After Start the service (Net.Pipe Listener Adapter) working fine. Thank you

  2. Pramod Bangalore Nagaraj 06/23/2016 at 3:39 AM Reply

    This saved me my evening. The word documents were not opening up and giving an “Something went wrong error” . The Net.Pipe Listener Adapter was running on the APPSERVER but was stopped on the WFE. Started it and wow…all documents are opening without a issue.

  3. Ole Bergtun 06/29/2016 at 5:16 AM Reply

    This also worked for me:) thx for the easy to find article.

  4. […] Source. […]

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: