Troubleshooting: OWA Fails With 'There Was No Endpoint Listening at net.pipe' Error

Version Affected: All
 
 

Overview

After authenticating to Outlook Web App (OWA), the following error can occur:

System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/s4u/<GUID> that could accept the message. This is often caused by an incorrect address or SOAP action.

with an inner exception of:

System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/s4u/<GUID>' could not be found on your local machine.

Cause

The Claims to Windows Token Service (C2WTS) on the OWA server is not running.

Resolution:

Open the Services MMC on the OWA server, set Claims to Windows Token Service to Automatic, then start the service.


 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.