Share via

SharePoint 2013: There was no endpoint listening at net.pipe...

  • Article

Problem

You click on a document in a document library in order to view it in Office Web Apps (OWA). Instead, the browser presents "Sorry, something went wrong" and the usual correlation ID. Testing further, you find that you cannot open any Microsoft Office document in OWA.

Troubleshooting

  1. Executed Get-OfficeWebAppsMachine on the farm's OWA server, and it returned Healthy.

  2. Checked OWA discovery, by connecting to http:/[OwaServername]/hosting/discovery, and found that it returns the appropriate XML file.

  3. On a SharePoint server, executed Get-SPWOPIBinding and this returned all bindings appropriately configured.

  4. On the primary WFE, checked ULS logs using the time and correlation ID seen earlier, and found the following entries:

    Trusted provider is missing. Provider: '00000003-0000-0ff1-ce00-000000000000' and WOPIFrame

    Unhandled exception: 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. See InnerException, if present, for more details. ---> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc' could not be found on your local machine....

    among 17 entries associated with this correlation ID.

  5. Checked server event logs on the APP and WFE servers, and found no System or Application events associated with this issue.

  6. Noting the SecurityTokenService item in this ULS entry, checked the SecurityTokenServiceApplicationPool on all WFE and APP servers and found that it was started.

  7. Opened browser, and then connected to:

    http://localhost:32843/SecurityTokenServiceApplication/appsts.svc

    This displayed a normal return:

  8. Restarted the SecurityTokenServiceApplicationPool, but found that this didn't resolve the problem.

  9. Performed search on ULS log entry terms, as noted in step 4 above. Found articles on Net.Pipe Listener Adapter.

  10. Checked the Net.Pipe Listener Adapter service on the WFEs and found that it was stopped on the primary WFE (there are two WFEs in Windows NLB configuration):

Solution

  1. Check the server's Net.Pipe Listener Adapter service on all SharePoint servers.
  2. If it's stopped, start it.

References

Notes

  • SharePoint Server 2013 Enterprise, two WFEs.
  • Problem occurred immediately after successful patching.
  • Thanks to Waqas Sarwar for presenting the original solution to this problem.