Monthly Archives: May 2014

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
%d bloggers like this: