Error: No Endpoint Listening! (but service running??)
Over the weekend, I deployed scheduled SharePoint Security and Windows updates to a medium-sized farm with multiple web applications. While verifying farm functionality, I encountered an error while opening documents through Office Web Apps.
Examining the logs revealed the below 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. ……………………
While this message seemed pretty clear, there was only one problem. The service was running.
Considering the service was running, and the error occurred after I updated the farm, I decided to run PSConfig again.
The process completed successfully and documents were rendering successfully in Office Web Apps. Everything looked good so it was time to watch the Eagles win the Super Bowl again.
The Error Returns
30 minutes later I start getting tickets about Office Web Apps. I try to reproduce them, but I can’t. Every document successfully opens in the browser. But then a document that initially opened in the browser, failed to do so a second time. Examining the error, I saw the same message from the weekend update. Following this, the document that successfully opened in the browser, then failed to open in the browser, successfully opened in the browser again.
Ok, since the error was intermittent, I assumed it was either a service or a memory issue. I checked and the service was still running. So I focused on server memory. I logged into the servers, and discovered memory utilization was at 75% on each WFE.
I increased the memory on the servers, and voilà! The errors stopped. The moral: always check memory utilization after installing updates!
Pesky errors got you flummoxed? Please feel free to reach out to us with any questions or concerns. We’d be happy to help you out.