Error opening Office documents in SharePoint 2013 website

For one of my Premier customers, Office documents were giving an error while opening in SharePoint 2013 website through office web apps.

Here are details of the issue and it’s resolution:



In SharePoint 2013 website, You might receive this error while opening Office documents in browser via office web apps:

Sorry, something went wrong
An error has occurred on the server.
Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.


3rd party softwares can cause this issue.
In our case "Dell change auditor agent" was the causing the issue so we had to stop the service of the 3rd party software(Dell).


You might see these entries in ULS logs:
w3wp.exe (0x1CA0) 0x44B0 SharePoint Foundation Authentication Authorization aib35 Medium SPShareByLinkHandler.Initialize : Not a ShareByLink request - missing access token
w3wp.exe (0x1CA0) 0x44B0 SharePoint Foundation Application Authentication agmxo 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.

w3wp.exe (0x1CA0) 0x44B0 SharePoint Foundation WOPI ajc39 Unexpected 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. Server stack trace: at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract.Issue(RequestApplicationSecurityToken request) at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.<>c__DisplayClass2.<RequestSelfIssuedToken>b__0() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.RequestSelfIssuedToken(RequestApplicationSecurityToken rst) at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.RequestRawLoopbackToken(OAuth2EndpointIdentity endpointIdentity, JsonWebSecurityToken onBehalfOf, String applicationContext) at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPIdentityContext identityContext, String applicationContext, DateTime& validTo) at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPUser user, String applicationContext, DateTime& validTo) at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPWeb web, Guid uniqueId, String proofKeyId, SPUrlZone zone, SPBasePermissions perms, Boolean hasEditLicense, Int64& ttl) at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPFile file, String proofKeyId, SPUrlZone zone, Int64& ttl) at Microsoft.SharePoint.Utilities.SPWOPIHost.GetWOPITargetInternal(HttpContext httpContext, SPWeb web, Object& spPrimeObject, SPWOPIAction& requestedAction, SPRegionalSettings spSettings, String& wopiAppUrl, String& wopiFavIconUrl, String& wopiAccessToken, Int64& wopiAccessTokenTtl, String& errorMessageToDisplay, String& redirectUrl) at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoadHelper(WOPIFrame frame) at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoad(WOPIFrame frame)

w3wp.exe (0x1CA0) 0x44B0 SharePoint Foundation General aat87 Monitorable An error has occurred on the server.

when we browsed to this URL on OWA farm:

We were getting this error:

Server Error
We're sorry. An error has occurred.
We've logged the error for the server administrator.

We checked that 'OpenFromUrlEnabled' property on OWA farm was set to false.
Ran this command to set property to true.
Set-OfficeWebAppsFarm -OpenFromUrlEnabled:$true
Now If we browse to this URL: OfficeWebAppsServerFQDN/op/generate.aspx, It results page correctly.

But documents were still giving error when opening in browser.
So, we are able to view Office documents using the Office Web Apps 2013 viewer Hence didn't seem to be an Office web apps issue.
After further investigation we found that : 3rd party software: "Dell change auditor agent" was causing it to fail.
After we stopped "Dell change auditor agent" service on SharePoint server and restarted IIS, Office Web Apps started to work.
Dell is already aware of this issue.

Likewise, other 3rd Party softwares can cause this issue.

More Information


Comments (2)

  1. Marcin says:

    Just found this with another Customer. Unfortunately, Dell support link does not exist anymore. I assume they fixed it, but that needs to be verified.

    1. VivekMSFT says:

      Yep, support link doesn’t exist anymore. Looks like they heard us and fixed it 🙂

Skip to main content